Skip to content
TrustedSkillsbeta
Back to all skills

Product Requirements

Checked
cexll·vlatest·productivity·AGPL-3.0

Generates clear product requirements documents quickly, streamlining development by outlining needs and features effectively.

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 stellarlinkco/myclaude --skill product-requirements -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

cexll

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 cexll/myclaude at f2e75c1263.

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

Commit
f2e75c1263
Manifest
skills/product-requirements/SKILL.md
Scanned
1 file, 353 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

The product-requirements skill helps users define, organize, and document clear requirements for a product or feature. It supports structured elicitation of user needs, functional specifications, and non-functional constraints to guide development efforts.

When to use it

  • When starting a new project and needing to gather initial requirements from stakeholders
  • When refining an existing product roadmap with detailed feature definitions
  • During planning phases to ensure alignment between teams on what needs to be built

Key capabilities

  • Structured requirement elicitation techniques
  • Documentation of functional and non-functional requirements
  • Organization of user stories, use cases, and acceptance criteria

Example prompts

  • "Help me gather product requirements for a mobile app that allows users to track their daily water intake."
  • "Create a list of functional and non-functional requirements for an e-commerce platform."
  • "Organize these user feedback points into clear product requirements."

Tips & gotchas

  • Ensure you have access to stakeholder input or existing documentation for accurate requirement gathering.
  • Use this skill early in the project lifecycle to avoid costly changes later on.