governance-setup
Skill1 starsChanged 8 months agoMITView on GitHub
Configure PromptSpeak governance for a new project. Use when first setting up PromptSpeak or when the user wants to customize governance policies.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- pitimon/claude-governancetheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- pitimon/claude-governance★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- drift-reviewSkill
- hold-triageSkill
The file
Files
Governance Setup — PromptSpeak
You are helping the user configure PromptSpeak governance for their project.
Workflow
- Assess the project context — Ask the user:
- What kind of agents will be governed? (coding assistants, data pipelines, customer-facing bots)
- What's the risk tolerance? (strict/regulated vs permissive/experimental)
- Are there specific tools or operations that must always require human approval?
Map answers to a governance profile, then let the user override specifics:
Profile When to use Confidence Holds Drift Post-Audit Lockdown Regulated domains (legal, financial, healthcare), production with PII 0.95 All tool calls held for approval ON, halt at 0.3 ON Standard Production coding assistants, internal tools, CI pipelines 0.7 Destructive ops only (deletes, deployments, external API writes) ON, halt at 0.6 ON Exploratory Sandboxes, prototyping, hackathons, trusted single-user agents 0.3 None (log only) OFF OFF Present all three profiles with the table above. Recommend Standard unless the user's answers clearly indicate otherwise. After the user picks a profile, ask: "Any overrides? For example, specific tools that should always require approval, or a different drift threshold."
Apply overrides on top of the chosen profile before proceeding to step 3.
- Apply configuration using PromptSpeak tools:
- Set confidence thresholds with
ps_confidence_bulk_set - Configure hold behavior with
ps_hold_config - Set feature flags with
ps_feature_set - Register policy overlays with
ps_config_setandps_config_activate
- Set confidence thresholds with
- Verify — Run
ps_execute_dry_runwith a sample frame to confirm the pipeline behaves as expected. - Export — Call
ps_config_exportso the user can save their configuration.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.