ask

Gather the information needed to proceed with a task through structured, focused dialogue.

buiducnhat/agent-skillsUpdated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

43

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/buiducnhat/agent-skills --skill ask

0

installs

0

this week

43

stars

Installation Guide

How to use ask on Cursor

AI-first code editor with Composer

1

Prerequisites

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 ask
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/buiducnhat/agent-skills --skill ask

Fetches ask from buiducnhat/agent-skills 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/ask

Restart Cursor to activate ask. Access via /ask 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.

Documentation

Ask

Purpose

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.

Scope Gate (Required Before Starting)

Use this skill only when:

  1. The task is underspecified — key requirements, constraints, or decisions are missing
  2. User input is required — the task cannot proceed without answers from the user
  3. No assumptions are safe — guessing would risk wasted effort or wrong direction

If the task is clear enough to act on, use brainstorm, write-plan, or quick-implement instead.

Workflow

Step 1: Gather Project Context

Load project context per the shared Context Loading Protocol. Only gather what is relevant to the current task. Skip if no docs exist.

Step 2: Identify Information Gaps

Determine exactly what is missing before a task can proceed:

  • Objective and user value
  • Scope boundaries and non-goals
  • Constraints (technical, UX, performance, timeline)
  • Success criteria
  • Key decisions with multiple valid options

Step 3: Ask Questions (One at a Time)

Ask targeted questions sequentially to close each gap.

Rules:

  • Ask exactly one question per message
  • Prefer multiple-choice options when practical (2–4 choices)
  • Use open-ended questions only when no reasonable options exist
  • Do not ask questions already answered by project documentation
  • Do not ask about implementation details prematurely
  • Do not bundle multiple questions into one message

Step 4: Confirm and Hand Off

Once all gaps are closed:

  1. Summarize the collected answers concisely
  2. Confirm with the user that the summary is correct
  3. Recommend the appropriate next skill based on complexity:
    • Simple, clear task → quick-implement
    • Complex or risky task → write-plan
    • Ambiguous, high-risk, or exploratory → brainstorm

Rules

  • Do not write code or modify any files
  • Do not produce plans, designs, or implementation artifacts
  • Do not make assumptions; ask instead
  • Keep questions short and focused
  • Apply YAGNI: only ask what is strictly necessary to proceed
  • Feeds into: brainstorm, write-plan, quick-implement

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

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

Steps

  1. 1Install product management skill
  2. 2Start with user story generation for known feature
  3. 3Progress to competitive analysis: research 2-3 competitors
  4. 4Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5Draft stakeholder communications and refine based on feedback
  6. 6Build template library for recurring PM tasks
  7. 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

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Related Skills

Reviews

4.645 reviews
  • H
    Hana TaylorDec 28, 2024

    Useful defaults in ask — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • A
    Advait ChoiDec 16, 2024

    I recommend ask for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • A
    Aditi BansalDec 8, 2024

    Solid pick for teams standardizing on skills: ask is focused, and the summary matches what you get after install.

  • M
    Maya RaoDec 8, 2024

    ask is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • A
    Anaya JainNov 27, 2024

    Useful defaults in ask — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • A
    Aanya AbebeNov 19, 2024

    ask is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • A
    Anaya KapoorNov 7, 2024

    Keeps context tight: ask is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • K
    Kwame MartinezOct 26, 2024

    ask is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • K
    Kwame KimOct 18, 2024

    I recommend ask for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • C
    Carlos AbebeOct 10, 2024

    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

1 / 5

Discussion

Comments — not star reviews
  • No comments yet — start the thread.