prompt-governance
This skill should be used when the user asks to "audit prompts for safety", "check prompts for injection vulnerabilities", "manage a prompt catalog", "version control prompts", or "review prompt quality and compliance".
Install / Use
npx skills add borghei/Claude-Skills --skill prompt-governanceInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
LegalSupported Platforms
Our assessment of prompt-governance
prompt-governance scores 84/100 on our quality scale, 138th of 209 Legal skills we index.
Its SKILL.md is 3.3 KB long, well organised into 17 sections with 1 code example: a solid amount of guidance for an agent.
It has 817 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so prompt-governance is actively maintained.
- Our last check on 2026-11-06 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
prompt-governance compared with similar skills
All 4 of these similar skills score higher than prompt-governance; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| prompt-governance (this skill)by borghei | 84 | 817 | 57d ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 4d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install prompt-governance?
- Run
npx skills add borghei/Claude-Skills --skill prompt-governance. The install tabs above show the steps for each supported agent. - Which AI agents does prompt-governance work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is prompt-governance safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is prompt-governance still maintained?
- The repository was last updated about 2 months ago, so prompt-governance is actively maintained.
Skill content
View source on GitHubname: prompt-governance description: > This skill should be used when the user asks to "audit prompts for safety", "check prompts for injection vulnerabilities", "manage a prompt catalog", "version control prompts", or "review prompt quality and compliance". license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: engineering domain: ai-governance updated: 2026-04-02 tags: [prompt-governance, prompt-safety, prompt-audit, prompt-catalog, ai-compliance]
Prompt Governance
Category: Engineering Domain: AI Governance
Overview
The Prompt Governance skill provides tools for auditing prompts for security vulnerabilities, bias, and safety issues, plus managing a versioned catalog of approved prompts. Essential for organizations deploying LLM-based applications at scale.
Clarify First
Before auditing or cataloging, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- [ ] Target prompt(s) — the exact file/text to audit or the catalog dir to manage (the subject of every check)
- [ ] Task: audit vs catalog management — selects
prompt_auditor.pyvsprompt_catalog_manager.pyand the whole workflow - [ ] Check focus — injection / bias / safety (sets which auditor checks run and the pass/fail bar)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Quick Start
# Audit a prompt for security and safety issues
python scripts/prompt_auditor.py --file system_prompt.txt
# Audit with specific focus
python scripts/prompt_auditor.py --text "You are a helpful assistant..." --checks injection,bias,safety
# Initialize a prompt catalog
python scripts/prompt_catalog_manager.py --init --catalog-dir ./prompts
# Add a prompt to the catalog
python scripts/prompt_catalog_manager.py --add --name "customer-support-v1" --file prompt.txt --catalog-dir ./prompts
# List all prompts in catalog
python scripts/prompt_catalog_manager.py --list --catalog-dir ./prompts
Tools Overview
| Tool | Purpose | Key Flags |
|------|---------|-----------|
| prompt_auditor.py | Audit prompts for injection, bias, and safety | --file, --text, --checks, --format |
| prompt_catalog_manager.py | Manage versioned prompt catalog | --init, --add, --list, --diff, --catalog-dir |
Workflows
Prompt Review Process
- Author writes or modifies a prompt
- Run
prompt_auditor.pyfor automated checks - Review findings and address critical issues
- Add approved prompt to catalog with
prompt_catalog_manager.py - Deploy from catalog (never from ad-hoc sources)
Prompt Versioning
- Store all prompts in catalog with semantic versioning
- Use
--diffto compare versions before promotion - Maintain audit trail of all prompt changes
- Roll back to previous versions when issues detected
Reference Documentation
- Prompt Governance Framework - Policies, review processes, and compliance requirements
Common Patterns
Prompt Lifecycle
Draft -> Audit -> Review -> Approve -> Deploy -> Monitor -> Retire
Governance Checklist
- No injection vulnerabilities
- No harmful content generation potential
- Appropriate bias mitigation
- Clear scope boundaries
- Output format constraints
- Error handling instructions
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
