Is prds-get safe to install?

SaferSkills independently audited prds-get (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.claude/skills/prds-get/SKILL.md · 1 file

.claude/skills/prds-get/SKILL.md2.3 KB · Markdown

name: prds-get

description: Fetch all open GitHub issues from this project that have the 'PRD' label

category: project-management

disable-model-invocation: true

Get All PRDs

Fetch all open GitHub issues from this project that have the 'PRD' label.

Note: If any gh command fails with "command not found", inform the user that GitHub CLI is required and provide the installation link: https://cli.github.com/

Process

Fetch Issues: Use GitHub CLI to get all open issues with PRD label

   gh issue list --label PRD --state open --json number,title,url,labels,assignees,createdAt,updatedAt

Format Results: Present the issues in a clear, organized format showing:

Issue number and title
Creation and last update dates
Current assignees (if any)
Direct link to the issue
PRD file link (if available in issue description)

Meaningful Categorization: Group PRDs by their actual purpose and impact, not generic labels:

Architecture & Infrastructure: Core system changes, API designs, major refactors
User Experience: Features that directly impact how users interact with the system
Developer Experience: Tools, workflows, testing, documentation that help developers
AI & Intelligence: Machine learning, AI-powered features, recommendation engines
Operations & Monitoring: Deployment, scaling, observability, performance
Integration & Extensibility: Third-party integrations, plugin systems, APIs

Each category should briefly explain what the PRDs in that group will accomplish for users or the system.

Priority Analysis: If multiple PRDs exist, help identify:

Which PRDs are most recently updated or have active discussion
Which PRDs have dependencies on other PRDs
Which PRDs are foundational vs. incremental improvements
Which PRDs might be blocked or need clarification

Next Steps Suggestion: Based on the PRD list, suggest logical next actions:

Which PRD to work on next based on dependencies and impact
PRDs that need attention, updates, or clarification
Opportunities for parallel work on independent PRDs

This provides a complete view of all active product requirements and helps with project planning and prioritization.

prds-get— agent skill

Is prds-get safe to install?

Get All PRDs

Process

Audit the pieces. Scan the whole. Decide.