Skip to content
skillsafebeta
← Report library
Purpose / Documents

Prd Skill Security Audit

What the author says it does (original text)

Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

Independent security check

No obvious risks found in this check

Files checked
1
Risks found
0
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.No risks found
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.No risks found
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.No risks found
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.No risks found
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.No risks found
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.No risks found

Inside this skill

7 instruction sections

The Skill instructs the agent to interview the user, analyze scope, and then draft a product requirements document using a fixed structure. The supplied material contains no executable scripts, installation steps, or network-operation instructions.

View source
SKILL.md:25In the instructionsOpen original file
## Operational Workflow### Phase 1: Discovery (The Interview)Before writing a single line of the PRD, you **MUST** interrogate the user to fill knowledge gaps. Do not assume context.
SKILL.md:37In the instructionsOpen original file
### Phase 2: Analysis & ScopingSynthesize the user's input. Identify dependencies and hidden complexities.- Map out the **User Flow**.- Define **Non-Goals** to protect the timeline.### Phase 3: Technical DraftingGenerate the document using the **Strict PRD Schema** below.

The interview asks for the core problem, success metrics, and constraints such as budget, technology stack, or deadline. These inputs support requirements analysis; the visible instructions do not request credentials, local-file scanning, or disclosure to a third party.

View source
SKILL.md:31In the instructionsOpen original file
**Ask about:**- **The Core Problem**: Why are we building this now?- **Success Metrics**: How do we know it worked?- **Constraints**: Budget, tech stack, or deadline?

The required output structure asks the PRD to discuss tools/APIs, architecture, integrations, authentication, security, and privacy. These are documentation requirements, not authorization to connect services, change permissions, or deploy a system.

View source
SKILL.md:86In the instructionsOpen original file
### 3. AI System Requirements (If Applicable)- **Tool Requirements**: What tools and APIs are needed?- **Evaluation Strategy**: How to measure output quality and accuracy.### 4. Technical Specifications- **Architecture Overview**: Data flow and component interaction.- **Integration Points**: APIs, DBs, and Auth.- **Security & Privacy**: Data handling and compliance.

The `codesearch`, `grep`, and `webfetch` names appear specifically in the architecture section of the “Intelligent Search System” example. They describe tools for the example product, rather than operational steps that this Skill itself must execute.

View source
SKILL.md:118In the instructionsOpen original file
## Example: Intelligent Search System### 1. Executive Summary**Problem**: Users struggle to find specific documentation snippets in massive repositories.**Solution**: An intelligent search system that provides direct answers with source citations.**Success**:
SKILL.md:136In the instructionsOpen original file
### 3. AI System Architecture- **Tools Required**: `codesearch`, `grep`, `webfetch`.
Start here · InstructionsSKILL.md
prd
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source.
Files and check records1 files

Coverage and gaps

Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions
Lines read
144
File checksum (to compare versions)
d2a11dde3f5f077992b07de04271abe2e881f9376d3f22ca823a638dda5bc6dc