skill-lookup

f/prompts.chat · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/f/prompts.chat --skill skill-lookup
0 commentsdiscussion
summary

Search, retrieve, and install reusable AI agent skills from the prompts.chat registry.

  • Provides two core MCP tools: search_skills for keyword-based discovery with category and tag filtering, and get_skill to retrieve complete skill packages including SKILL.md, documentation, and helper scripts
  • Supports installation workflow that creates .claude/skills/{slug}/ directories and verifies file integrity after saving
  • Enables skill browsing with result presentation showing title, descriptio
skill.md

Workflow

  1. Search for skills matching the user's request using search_skills
  2. Present results with title, description, author, and file list
  3. If the user picks a skill, retrieve it with get_skill to get all files
  4. Install by saving files to .claude/skills/{slug}/ and verify the SKILL.md exists
  5. Confirm installation and explain what the skill does and when it activates

Example

search_skills({"query": "code review", "limit": 5, "category": "coding"})
get_skill({"id": "abc123"})

Available Tools

Use these prompts.chat MCP tools:

  • search_skills - Search for skills by keyword
  • get_skill - Get a specific skill by ID with all its files

How to Search for Skills

Call search_skills with:

  • query: The search keywords from the user's request
  • limit: Number of results (default 10, max 50)
  • category: Filter by category slug (e.g., "coding", "automation")
  • tag: Filter by tag slug

Present results showing:

  • Title and description
  • Author name
  • File list (SKILL.md, reference docs, scripts)
  • Category and tags
  • Link to the skill

How to Get a Skill

Call get_skill with:

  • id: The skill ID

Returns the skill metadata and all file contents:

  • SKILL.md (main instructions)
  • Reference documentation
  • Helper scripts
  • Configuration files

How to Install a Skill

When the user asks to install a skill:

  1. Call get_skill to retrieve all files
  2. Create the directory .claude/skills/{slug}/
  3. Save each file to the appropriate location:
    • SKILL.md.claude/skills/{slug}/SKILL.md
    • Other files → .claude/skills/{slug}/{filename}
  4. Read back SKILL.md to verify the frontmatter is intact

Guidelines

  • Always search before suggesting the user create their own skill
  • Present search results in a readable format with file counts
  • When installing, confirm the skill was saved successfully
  • Explain what the skill does and when it activates
how to use skill-lookup

How to use skill-lookup 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 development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add skill-lookup
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/f/prompts.chat --skill skill-lookup

The skills CLI fetches skill-lookup from GitHub repository f/prompts.chat and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/skill-lookup

Reload or restart Cursor to activate skill-lookup. Access the skill through slash commands (e.g., /skill-lookup) or your agent's skill management interface.

Security & Verification 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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

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

Installation Steps

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

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.764 reviews
  • Pratham Ware· Dec 28, 2024

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

  • William Iyer· Dec 24, 2024

    We added skill-lookup from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Isabella Flores· Dec 20, 2024

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

  • Lucas Gonzalez· Dec 12, 2024

    Registry listing for skill-lookup matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Meera Jackson· Dec 8, 2024

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

  • Ren Sethi· Dec 8, 2024

    skill-lookup fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Yusuf Khanna· Dec 4, 2024

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

  • Aanya Johnson· Dec 4, 2024

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

  • Layla Khanna· Nov 27, 2024

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

  • Noah Harris· Nov 27, 2024

    Registry listing for skill-lookup matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 64

1 / 7