Skill
analyze-codebase
Run comprehensive PLG analysis on a codebase to detect tech stack, existing growth features, and revenue opportunities. Use when…
@skenetechnologiesInstall SkillProduct
Skill
/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".
Install
$ npx -y skills add skenetechnologies/skene --skill validate-loop --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/validate-loop
Context preview
The summary Claude sees to decide when to auto-load this skill.
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".
SKILL.md
validate-loop.SKILL.mdname: validate-loop
description: 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".
Validate Loop Implementation
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 status` fails, 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
1. **Discover CLI options** Run `uvx skene status --help` to see available flags. Use only flags that appear in the output.
2. **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/null` If missing: "No growth loop found. Run `/skene-plan` first." Stop.
3. **Run status check** Run `uvx skene status` with appropriate flags from --help output (e.g. path argument, `--context` if needed). If it fails, report error. Do NOT build your own checklist.
4. **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).
5. **Suggest next step**
- All done → "Growth loop implemented. Run `/skene-deploy` for telemetry."
- Gaps remain → "Remaining: [items]. Run `/skene-build` to continue."
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.
Read more
name: validate-loop description: 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".
Validate Loop Implementation
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 status` fails, 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
1. **Discover CLI options** Run `uvx skene status --help` to see available flags. Use only flags that appear in the output.
2. **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/null` If missing: "No growth loop found. Run `/skene-plan` first." Stop.
3. **Run status check** Run `uvx skene status` with appropriate flags from --help output (e.g. path argument, `--context` if needed). If it fails, report error. Do NOT build your own checklist.
4. **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).
5. **Suggest next step**
- All done → "Growth loop implemented. Run `/skene-deploy` for telemetry."
- Gaps remain → "Remaining: [items]. Run `/skene-build` to continue."
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.
Ships withskene
Product-Led Growth (PLG) analysis toolkit that detects tech stacks, plans growth loops and builds the loop iteratively.
Get the whole plugin
Other skills on skene.
@skenetechnologiesInstall SkillSkill
build-implementation
Generate context-aware implementation prompts for a selected growth loop. Use when the user says "build", "implement", "generate…
@skenetechnologiesInstall SkillSkill
deploy-telemetry
Set up analytics and tracking infrastructure for growth loops. Use when the user says "deploy telemetry", "set up analytics",…
@skenetechnologiesInstall SkillSkill
initialize-config
Set up Skene configuration for a project. Use when starting a new PLG analysis, when .skene.config is missing, or when the user…
@skenetechnologiesInstall SkillSkill
plan-growth-loop
Generate prioritized growth loops with implementation roadmaps based on codebase analysis. Use when the user says "plan", "growth…
@skenetechnologiesInstall Skill