Guide users through the capabilities of this workspace setup.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionhelpExecute the skills CLI command in your project's root directory to begin installation:
Fetches help from parcadei/continuous-claude-v3 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 help. Access via /help 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
3.7K
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
3.7K
stars
Guide users through the capabilities of this workspace setup.
/help # Interactive guided discovery
/help workflows # Workflow orchestration skills
/help agents # Specialist agents catalog
/help tools # CLI tools (tldr, prove, recall)
/help hooks # Active hooks and what they do
/help advanced # MCP, frontmatter, customization
/help <name> # Deep dive on specific skill/agent
Use AskUserQuestion to guide the user:
question: "What are you trying to do?"
header: "Goal"
options:
- label: "Explore/understand a codebase"
description: "Find patterns, architecture, conventions"
- label: "Fix a bug"
description: "Investigate, diagnose, implement fix"
- label: "Build a feature"
description: "Plan, implement, test new functionality"
- label: "Prove something mathematically"
description: "Formal verification with Lean 4"
Based on response, show relevant tools:
| Goal | Show |
|---|---|
| Explore codebase | scout agent, tldr CLI, /explore workflow |
| Fix a bug | /fix workflow, sleuth agent, debug-agent |
| Build feature | /build workflow, architect agent, kraken agent |
| Prove math | /prove skill, lean4 skill, Godel-Prover |
| Research docs | oracle agent, nia-docs, perplexity |
| Configure workspace | hooks, rules, settings, frontmatter |
Display workflow meta-skills:
## Workflow Skills
Orchestrate multi-agent pipelines for complex tasks.
| Workflow | Purpose | Agents Used |
|----------|---------|-------------|
| /fix | Bug investigation → diagnosis → implementation | sleuth → kraken → arbiter |
| /build | Feature planning → implementation → testing | architect → kraken → arbiter |
| /debug | Deep investigation of issues | debug-agent, sleuth |
| /tdd | Test-driven development cycle | arbiter → kraken → arbiter |
| /refactor | Code transformation with safety | phoenix → kraken → judge |
| /review | Code review and feedback | critic, judge |
| /security | Vulnerability analysis | aegis |
| /explore | Codebase discovery | scout |
| /test | Test execution and validation | arbiter, atlas |
| /release | Version bumps, changelog | herald |
| /migrate | Framework/infrastructure changes | pioneer, phoenix |
**Usage**: Just describe your goal. Claude routes to the right workflow.
Display agent catalog:
## Specialist Agents
Spawn via Task tool with subagent_type.
### Exploration & Research
| Agent | Purpose | Model |
|-------|---------|-------|
| scout | Codebase exploration, pattern finding | sonnet |
| oracle | External research (web, docs, APIs) | sonnet |
| pathfinder | External repository analysis | sonnet |
### Planning & Architecture
| Agent | Purpose | Model |
|-------|---------|-------|
| architect | Feature planning, design docs | sonnet |
| plan-agent | Create implementation plans | sonnet |
| phoenix | Refactoring & migration planning | sonnet |
### Implementation
| Agent | Purpose | Model |
|-------|---------|-------|
| kraken | TDD implementation, refactoring | sonnet |
| spark | Quick fixes, lightweight changes | haiku |
### Review & Validation
| Agent | Purpose | Model |
|-------|---------|-------|
| arbiter | Test execution, validation | sonnet |
| critic | Code review | sonnet |
| judge | Refactoring review | sonnet |
### Investigation
| Agent | Purpose | Model |
|-------|---------|-------|
| sleuth | Bug investigation, root cause | sonnet |
| debug-agent | Issue investigation with logs | sonnet |
| profiler | Performance, race conditions | sonnet |
### Documentation & Handoff
| Agent | Purpose | Model |
|-------|---------|-------|
| scribe | Documentation, session summaries | sonnet |
| chronicler | Session analysis, learning extraction | sonnet |
Display CLI tools and capabilities:
## Built-in Tools
### TLDR Code Analysis
Token-efficient code exploration (95% savings vs reading raw files).
```bash
tldr tree src/ # File tree
tldr structure srcMake 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.
parcadei/continuous-claude-v3
mattpocock/skills
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
help has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend help for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in help — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
help fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: help is the kind of skill you can hand to a new teammate without a long onboarding doc.
help fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend help for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
help reduced setup friction for our internal harness; good balance of opinion and flexibility.
help is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: help is focused, and the summary matches what you get after install.
showing 1-10 of 69