Skip to content
TrustedSkillsbeta
Back to all skills

Create Prd

Checked
fradser·vlatest·productivity·MIT

Automatically generates product requirement documents from meeting notes and existing data, saving time and ensuring clarity.

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 fradser/dotclaude --skill create-prd -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

fradser

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 fradser/dotclaude at 9815c4f485.

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

Commit
9815c4f485
Manifest
office/skills/create-prd/SKILL.md
Scanned
8 files, 1,881 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 fradser-create-prd skill generates production readiness documentation from existing code and comments. It can automatically extract key information like API endpoints, data models, and deployment instructions. This helps streamline the process of creating comprehensive documentation for deployed applications, reducing manual effort and ensuring consistency.

When to use it

  • You have a newly developed application that needs thorough production-ready documentation.
  • Existing code lacks sufficient comments or documentation to understand its functionality.
  • You want to automate the creation of API reference guides from your codebase.
  • Your team struggles with maintaining up-to-date deployment instructions.

Key capabilities

  • Generates documentation from code and comments.
  • Extracts API endpoint details.
  • Identifies data model structures.
  • Creates deployment instruction outlines.

Example prompts

  • "Generate production readiness documentation for the user_authentication module."
  • "Create an API reference guide based on the /api/v1 endpoints."
  • "Outline the steps required to deploy the order_processing service."

Tips & gotchas

The quality of generated documentation depends heavily on the clarity and completeness of existing code comments. Ensure your codebase has sufficient commenting for optimal results.