auto-trigger▌
charon-fan/agent-playbook · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
This skill defines automatic trigger relationships between skills. When a skill completes its workflow, it should automatically trigger the next skill in the chain.
Auto-Trigger Hooks
This skill defines automatic trigger relationships between skills. When a skill completes its workflow, it should automatically trigger the next skill in the chain.
Hook Definitions
PRD Creation 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 Chain
implementation_complete:
triggers:
- skill: code-reviewer
mode: ask_first
message: "Implementation complete. Run code review?"
- skill: create-pr
mode: auto
condition: changes_staged
Session Management
session_start:
auto_triggers:
- skill: session-logger
action: create_session_file
session_end:
auto_triggers:
- skill: session-logger
action: update_session_file
Hook Format in Skills
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
---
Implementation Guide
When a skill completes its workflow:
- Check
hooksin its own front matter (before_start,after_complete,on_error,on_progress) - For each hook:
- If
mode: auto, trigger immediately - If
mode: background, trigger without waiting - If
mode: ask_first, ask user before triggering - If
condition:exists, check it first
- If
- Pass context to the triggered skill
Example Integration
prd-planner should add:
---
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"
---
self-improving-agent already has:
---
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
---
create-pr should add:
---
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}"
---
Chain Visualization
┌──────────────┐
│ prd-planner │
└──────┬───────┘
│ after_complete
├──→ self-improving-agent (background)
│ └──→ create-pr (ask_first)
│ └──→ session-logger (auto)
└──→ session-logger (auto)
Error Correction Chain
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}"
Important Rules
- Don't create infinite loops - Ensure chains terminate
- Ask before major actions - Use
mode: ask_firstfor PRs, deployments - Background tasks - Use
mode: backgroundfor non-blocking tasks - Pass context - Always include relevant context to triggered skills
How to use auto-trigger on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add auto-trigger
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches auto-trigger from GitHub repository charon-fan/agent-playbook and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate auto-trigger. Access the skill through slash commands (e.g., /auto-trigger) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★56 reviews- ★★★★★Lucas Choi· Dec 24, 2024
auto-trigger is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Xiao Sethi· Dec 8, 2024
Keeps context tight: auto-trigger is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Omar Martin· Dec 4, 2024
We added auto-trigger from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Min Gill· Nov 27, 2024
We added auto-trigger from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Liam Iyer· Nov 23, 2024
Keeps context tight: auto-trigger is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Lucas Thomas· Nov 15, 2024
auto-trigger fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Xiao Liu· Oct 18, 2024
auto-trigger fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Olivia Kapoor· Oct 14, 2024
auto-trigger is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Kwame Sharma· Oct 6, 2024
We added auto-trigger from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Isabella Flores· Sep 25, 2024
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