Purpose: One command to pull the latest skills from the repo and install them globally across all agents.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionupdateExecute the skills CLI command in your project's root directory to begin installation:
Fetches update from boshu2/agentops 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 update. Access via /update 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
0
total installs
0
this week
260
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
260
stars
Purpose: One command to pull the latest skills from the repo and install them globally across all agents.
YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.
bash <(curl -fsSL https://raw.githubusercontent.com/boshu2/agentops/main/scripts/install.sh)
Run this command. Wait for it to complete.
Confirm the output shows all skills installed with no failures.
If any skills failed to install, report which ones failed and suggest re-running the installer. If the failure is isolated to one skill, tell the user to inspect the target agent's installed skill or plugin directory and restore just that skill from the latest repo copy.
# Retry the full installer:
bash <(curl -fsSL https://raw.githubusercontent.com/boshu2/agentops/main/scripts/install.sh)
Tell the user:
User says: /update
What happens:
Result: All AgentOps skills are updated to the latest version and available globally across all agent sessions.
User says: /update (after a previous run failed for some skills)
What happens:
Result: 48 skills installed successfully, with clear instructions to retry the installer and recover the 2 failed skills from the latest repo copy if needed.
| Problem | Cause | Solution |
|---|---|---|
curl: command not found |
curl is not installed | Install curl via your package manager |
| Download fails | Network or GitHub unreachable | Check connectivity; retry |
| Individual skills fail | Permissions issue in the agent's install or plugin directory | Fix permissions on the target agent's install home, then re-run /update |
| Skills not available after install | Agent session not restarted | Restart your agent session |
EACCES: permission denied |
Restrictive permissions on the install target | Fix permissions on the install target, then re-run /update |
Make 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
update has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in update — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
update reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for update matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: update is focused, and the summary matches what you get after install.
We added update from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
update is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: update is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: update is focused, and the summary matches what you get after install.
Registry listing for update matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 66