This skill defines automatic trigger relationships between skills. When a skill completes its workflow, it should automatically trigger the next skill in the chain.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionauto-triggerExecute the skills CLI command in your project's root directory to begin installation:
Fetches auto-trigger from charon-fan/agent-playbook and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate auto-trigger. Access via /auto-trigger in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
27
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
27
stars
This skill defines automatic trigger relationships between skills. When a skill completes its workflow, it should automatically trigger the next skill in the chain.
prd_complete:
triggers:
- skill: self-improving-agent
mode: background
condition: PRD file exists and is complete
- skill: session-logger
mode: auto
context: "PRD created for {feature_name}"
prd_implemented:
triggers:
- skill: session-logger
mode: auto
context: "Implemented PRD: {feature_name}"
implementation_complete:
triggers:
- skill: code-reviewer
mode: ask_first
message: "Implementation complete. Run code review?"
- skill: create-pr
mode: auto
condition: changes_staged
session_start:
auto_triggers:
- skill: session-logger
action: create_session_file
session_end:
auto_triggers:
- skill: session-logger
action: update_session_file
To add auto-trigger capability to a skill, add to its front matter:
---
name: my-skill
description: Skill description
allowed-tools: Read, Write, Edit
hooks:
before_start:
- trigger: session-logger
mode: auto
context: "Start {skill_name}"
after_complete:
- trigger: self-improving-agent
mode: background
- trigger: session-logger
mode: auto
on_error:
- trigger: self-improving-agent
mode: background
---
When a skill completes its workflow:
hooks in its own front matter (before_start, after_complete, on_error, on_progress)mode: auto, trigger immediatelymode: background, trigger without waitingmode: ask_first, ask user before triggeringcondition: exists, check it first---
name: prd-planner
description: Creates PRDs using persistent file-based planning...
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, AskUserQuestion, WebSearch
hooks:
after_complete:
- trigger: self-improving-agent
mode: background
context: "PRD created at {prd_file}"
- trigger: session-logger
mode: auto
context: "PRD creation complete"
---
---
name: self-improving-agent
description: Universal self-improvement that learns from all skill experiences...
allowed-tools: Read, Write,Edit, Bash, Grep, Glob, WebSearch
hooks:
after_complete:
- trigger: create-pr
mode: ask_first
condition: skills_modified
- trigger: session-logger
mode: auto
context: "Self-improvement cycle complete"
on_error:
- trigger: self-improving-agent
mode: background
---
---
name: create-pr
description: Creates pull requests with bilingual documentation updates...
allowed-tools: Read, Write, Edit, Bash, Grep, AskUserQuestion
hooks:
after_complete:
- trigger: session-logger
mode: auto
context: "PR created: {pr_title}"
---
┌──────────────┐
│ prd-planner │
└──────┬───────┘
│ after_complete
├──→ self-improving-agent (background)
│ └──→ create-pr (ask_first)
│ └──→ session-logger (auto)
└──→ session-logger (auto)
on_error:
triggers:
- skill: self-improving-agent
mode: background
context: "Error occurred in {skill_name}"
- skill: session-logger
mode: auto
context: "Error captured for {skill_name}"
mode: ask_first for PRs, deploymentsmode: background for non-blocking tasksMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
auto-trigger is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: auto-trigger is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added auto-trigger from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added auto-trigger from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: auto-trigger is the kind of skill you can hand to a new teammate without a long onboarding doc.
auto-trigger fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
auto-trigger fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
auto-trigger is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added auto-trigger from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: auto-trigger is focused, and the summary matches what you get after install.
showing 1-10 of 56