Before installing skills in Cursor, ensure your development environment meets these requirements:
›Cursor installed and configured on your machine
›Node.js 16+ with npm — verify with node --version
›Active project directory where you want to add status
2
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
$npx skills add https://github.com/boshu2/agentops --skill status
Fetches status from boshu2/agentops and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/status
Restart Cursor to activate status. Access via /status in your agent's command palette.
⚠
Security 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 environment. Always review source, verify the publisher, and test in isolation before production.
Purpose: Single-screen overview of your current state. What am I working on? What happened recently? What should I do next?
YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.
CLI dependencies: bd, ao, gt — all optional. Shows what's available, skips what isn't.
Quick Start
/status # Full dashboard/status --json# Machine-readable JSON output
Execution Steps
Step 1: Gather State (Parallel)
Run ALL of the following in parallel bash calls for speed:
Call 1 — RPI + Ratchet + Task State:
# Current ratchet phaseif[-f .agents/ao/chain.jsonl ];thentail-1 .agents/ao/chain.jsonl 2>/dev/null
elseecho"NO_CHAIN"fi# Ratchet status via CLIifcommand-v ao &>/dev/null;then ao ratchet status --json2>/dev/null ||echo"RATCHET_UNAVAILABLE" ao task-status --json2>/dev/null ||echo"TASK_STATUS_UNAVAILABLE"fi
Call 2 — Beads / Epic State:
ifcommand-v bd &>/dev/null;thenecho"=== EPIC ===" bd list --type epic --statusopen2>/dev/null |head-5echo"=== IN_PROGRESS ===" bd list --status in_progress 2>/dev/null |head-5echo"=== READY ===" bd ready 2>/dev/null |head-5echo"=== TOTAL ===" bd list 2>/dev/null |wc-lelseecho"BD_UNAVAILABLE"fi
Call 3 — Knowledge Flywheel:
# Learnings countecho"LEARNINGS=$(ls .agents/learnings/ 2>/dev/null |wc-l|tr-d' ')"echo"PATTERNS=$(ls .agents/patterns/ 2>/dev/null |wc-l|tr-d' ')"echo"PENDING=$(ls .agents/forge/ 2>/dev/null |wc-l|tr-d' ')"# Flywheel health + badgeifcommand-v ao &>/dev/null;then ao metrics flywheel status 2>/dev/null ||echo"FLYWHEEL_UNAVAILABLE" ao badge 2>/dev/null ||echo"BADGE_UNAVAILABLE"fi
Assemble gathered data into this format. Use Unicode indicators for visual clarity:
Pass/healthy: [PASS]
Warning/partial: [WARN]
Fail/missing: [FAIL]
Progress: [3/7] with bar ███░░░░
══════════════════════════════════════════════════
Workflow Dashboard
══════════════════════════════════════════════════
RPI PROGRESS
Phase: <current phase from chain.jsonl: research | plan | implement | validate | idle>
Gate: <last completed gate or "none">
─────────────────────────────────
research ── plan ── implement ── validate
<mark current position with arrow or highlight>
ACTIVE EPIC
<epic title and ID, or "No active epic">
Progress: <completed>/<total> issues <progress bar>
In Progress: <list in-progress issues, max 3>
READY TO WORK
<top 3 unblocked issues from bd ready>
<or "No ready issues — create work with /plan">
RECENT VALIDATIONS
<last 3 council reports with verdict>
<format: date verdict target>
<or "No recent validations">
KNOWLEDGE FLYWHEEL
Learnings: <count> Patterns: <count> Pending: <count>
Health: <flywheel status or "ao not installed">
Badge: <ao badge output or omit if unavailable>
TASK MATURITY
<ao task-status summary: active tasks with CASS maturity levels, or omit if unavailable>
RECENT SESSIONS
<last 3 session summaries with dates>
<or "No session history">
GIT STATE
Branch: <current branch>
Recent: <last 3 commits, one-line>
Changes: <uncommitted file count or "clean">
INBOX
<message count or "No messages" or "gt not installed">
SESSION QUALITY SIGNALS
<last 10 entries from .agents/signals/session-quality.jsonl as table>
| Timestamp | Signal | Detail | Session |
|-----------|--------|--------|---------|
<parsed from JSON lines: .timestamp, .signal, .detail, .session>
<or "No quality signals recorded." if file missing or empty>
──────────────────────────────────────────────────
SUGGESTED NEXT ACTION
<state-aware suggestion — see Step 3>
──────────────────────────────────────────────────
QUICK COMMANDS
/research Deep codebase exploration
/plan Decompose epic into issues
/pre-mortem Validate plan before coding
/implement Execute a single issue
/crank Autonomous epic execution
/validation Full close-out and learnings
/vibe Targeted code review
══════════════════════════════════════════════════
Step 3: Suggest Next Action (State-Aware)
Evaluate state top-to-bottom. Use the FIRST matching condition:
Priority
Condition
Suggestion
1
No ratchet chain exists
"Start with /quickstart or /research to begin a workflow"
2
Research done, no plan
"Run /plan to decompose research into actionable issues"
3
Plan done, no pre-mortem
"Run /pre-mortem to validate the plan before coding"
4
Issues in-progress
"Continue working: /implement <issue-id> or /crank for autonomous execution"
5
Ready issues available
"Pick up next issue: /implement <first-ready-id>"
6
Uncommitted changes
"Review recent work: /validation"
7
Implementation done, no vibe
"Run /validation for final close-out"
8
Recent WARN/FAIL verdict
"Address findings in <report-path>, then re-run /validation"
10
Vibe passed, no post-mortem
"Run /validation to complete closeout and extract learnings"
11
Pending knowledge items
"Promote learnings: ao pool list --status pending --json, then ao pool stage <id> and ao pool promote <id>"
12
Clean state, nothing pending
"All clear. Start with /research or /plan to find new work"
Step 4: JSON Output (--json flag)
If the user passed --json, output all dashboard data as structured JSON instead of the visual dashboard:
›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
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share 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
