Gather the information needed to proceed with a task through structured, focused dialogue.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionaskExecute the skills CLI command in your project's root directory to begin installation:
Fetches ask from buiducnhat/agent-skills 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 ask. Access via /ask 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
43
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
43
stars
Gather the information needed to proceed with a task through structured, focused dialogue.
This skill is for asking only. Do not plan, implement, or produce any artifacts.
Use this skill only when:
If the task is clear enough to act on, use brainstorm, write-plan, or quick-implement instead.
Load project context per the shared Context Loading Protocol. Only gather what is relevant to the current task. Skip if no docs exist.
Determine exactly what is missing before a task can proceed:
Ask targeted questions sequentially to close each gap.
Rules:
Once all gaps are closed:
quick-implementwrite-planbrainstormbrainstorm, write-plan, quick-implementMake 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
Useful defaults in ask — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend ask for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: ask is focused, and the summary matches what you get after install.
ask is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in ask — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
ask is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: ask is the kind of skill you can hand to a new teammate without a long onboarding doc.
ask is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend ask for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: ask is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 45