Skip to content
TrustedSkillsbeta
Back to all skills

Analyze Feature Requests

Checked
phuryn·vlatest·other·MIT

Quickly assesses feature requests, identifying impact, feasibility, and alignment with product strategy using detailed scoring.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add phuryn/pm-skills --skill analyze-feature-requests -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

phuryn

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned phuryn/pm-skills at c68487d721.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
c68487d721
Manifest
pm-product-discovery/skills/analyze-feature-requests/SKILL.md
Scanned
1 file, 50 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill analyzes feature requests to extract key information and identify potential issues. It can summarize requests, categorize them based on priority or impact, and highlight dependencies or conflicts between different features. The goal is to provide a structured overview of feature requests for product managers and development teams.

When to use it

  • Prioritization: Quickly assess a backlog of feature requests to determine which ones should be addressed first.
  • Dependency Mapping: Identify potential conflicts or dependencies between multiple feature requests.
  • Summarization: Condense lengthy feature request descriptions into concise summaries for stakeholders.
  • Categorization: Automatically categorize feature requests by type (e.g., bug fix, new feature, enhancement).

Key capabilities

  • Feature Request Summarization
  • Priority Assessment
  • Dependency Identification
  • Categorization

Example prompts

  • "Analyze this feature request: [paste feature request text]"
  • "Summarize these feature requests and categorize them by priority: [list of feature requests]"
  • "Identify any dependencies between these feature requests: [list of feature requests]"

Tips & gotchas

The quality of the analysis depends heavily on the clarity and detail provided in the original feature request. Ensure the input text is well-written and contains sufficient information for accurate assessment.