Ripperdoc is a tooling/knowledge-base repository that packages reusable skills and agent definitions alongside Python validation scripts. It is designed to provide structured guidance (skills/agents) and runnable checks (scripts) for audits, testing, and project validation workflows.
Key folders in the repository:
/agents/ -> Agent definitions (roles, capabilities, orchestration rules)
/skills/ -> Skill packages (SKILL.md + optional scripts/resources)
/scripts/ -> Python entry scripts (checklist, full verification)
Examples:
agents/orchestrator.md— orchestration rules and agent rolesskills/**/SKILL.md— skill metadata and instructionsscripts/verify_all.py— full verification suitescripts/checklist.py— master checklist runner
- Python 3.x (required to run scripts)
- No package manager config found (no
package.json,pyproject.toml, orrequirements.txtat repo root)
Note: Some skills reference optional tools (e.g., Playwright) within their own documentation; install as needed for those tasks.
Runs core validation checks in priority order.
python scripts/checklist.py .Runs complete validation, including performance and E2E checks.
python scripts/verify_all.py . --url <URL>- Skills live under
skills/and provide structured domain instructions plus optional scripts. - Agents live under
agents/and define role-specific behavior, boundaries, and orchestration rules.
Common patterns:
skills/<skill-name>/SKILL.md— metadata + instructionsskills/<skill-name>/scripts/— optional automation scriptsagents/<agent-name>.md— agent definition
See skills/doc.md for a detailed overview of how skills are structured and used.
- Add new skills under
skills/<your-skill>/SKILL.mdwith optionalscripts/,references/, andassets/. - Keep instructions concise and actionable.
- Ensure any scripts are runnable and documented in the skill.
If adding new validation scripts, place them in scripts/ and document usage in the README or relevant skill.
License: Unknown — add the correct license file or update this section when known.