validate-loop
Check if growth loop requirements are actually implemented in the codebase. Use when the user says "validate", "check status", "skene status", "is it done", or "verify implementation".
pinned to #e2173a9updated yesterday
Ask your AI client: “install skills/validate-loop”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/validate-loopmetahub onboarded this repo on the author's behalf.
If you own github.com/SkeneTechnologies/skene on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
121
Last commit
yesterday
Latest release
published
- #ai-tools
- #anthropic
- #automation
- #cli
- #cli-tool
- #code-documentation
- #codebase-analysis
- #developer-tools
- #gemini
- #growth-hacking
- #llm
- #mcp
- #mcp-server
- #openai
- #plg
- #product-led-growth
- #pydantic
- #python
- #python3
- #tech-stack-detection
About this skill
Pulled from SKILL.md at publish time.
Check implementation status via the Skene CLI.
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.e2173a9· yesterday
Documentation
7 passed2 warningsHomepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
Documentation shows usagewarn
Documentation has no code examples.
Add at least one fenced example showing a real invocation.
Description quality
27 words · 184 chars — "Check if growth loop requirements are actually implemented in the codebase. Use …"
README is present and substantial
5,526 chars · 7 sections · 3 code blocks
Tags / topics declared
20 total — ai-tools, anthropic, automation, cli, cli-tool, code-documentation (+14)
README has usage / example sections
found: Quick Start · Installation
Homepage / docs URL declared
https://pypi.org/project/skene/
Description is substantive
Description is 27 words.
Documentation present and substantive
Documentation present (SKILL.md, 270 words).
Release history
1- releasecurrente2173a9warnyesterday
Contents
Check implementation status via the Skene CLI.
Agent behavior rules
- Autonomous. Run the CLI, present results, suggest next step. No mid-flow questions.
- CLI is the source of truth. If
uvx skene statusfails, report the error. Do NOT fabricate your own checklist. - User cannot type into agent terminals. Pipe safe defaults for routine prompts. Kill stuck terminals.
Steps
-
Discover CLI options Run
uvx skene status --helpto see available flags. Use only flags that appear in the output. -
Check for growth loops
ls .skene/active-loop.json 2>/dev/null || ls skene-context/growth-loops/ 2>/dev/null || ls skene/growth-loops/ 2>/dev/nullIf missing: "No growth loop found. Run/skene-planfirst." Stop. -
Run status check Run
uvx skene statuswith appropriate flags from --help output (e.g. path argument,--contextif needed). If it fails, report error. Do NOT build your own checklist. -
Present CLI output Present the engine status table from CLI output. For action features, Detail uses
Found in: <newest migration> (+N)when the same trigger exists in multiple SQL files (+N= additional files beyond the one shown). -
Suggest next step
- All done → "Growth loop implemented. Run
/skene-deployfor telemetry." - Gaps remain → "Remaining: [items]. Run
/skene-buildto continue."
- All done → "Growth loop implemented. Run
Error handling
- CLI failure: Report error, suggest fix.
- Permission errors: Give user the command for their terminal.
Output
Status summary (done/partial/missing), what's left, next step.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/validate-loop