iam-consent-governance
Skill40 starsChanged 5 days agoApache-2.0View on GitHub
Use when changing IAM, consent scopes, actor model, verification policy, or marketplace access contracts inside the security-audit owner family.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Avoid overlap with security-audit and quality-contracts.
- Distinctive: line 58
Keep IAM docs, code, and validation checklists aligned in the same change.
- Very specific: line 59
Treat vault and PKM boundary questions as security-audit work when they become primary.
- Very specific: line 64
If the request is still broad or ambiguous, route it back to security-audit.
- Very specific: line 65
If the task becomes vault or PKM storage-boundary work, use security-audit.
- Very specific: line 66
If the task becomes general backend runtime work, route it to backend.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hussh IAM Consent Governance Skill
Purpose and Trigger
- Primary scope:
iam-consent-governance - Trigger on IAM, consent scopes, actor model, verification policy, or marketplace access contract changes.
- Avoid overlap with
security-auditandquality-contracts.
Coverage and Ownership
- Role:
spoke - Owner family:
security-audit
Owned repo surfaces:
docs/architecture/identityconsent-protocol/api/routes/iam.pyconsent-protocol/api/routes/consent.pyhushh-webapp/lib/consenthushh-webapp/components/consent
Non-owned surfaces:
security-auditbackenddocs-governance
Do Use
- Consent-scope, actor-model, and verification-gate changes.
- IAM runtime surface and marketplace access contract work.
- IAM docs and code alignment across frontend and backend.
- Opaque object-share references that must remain separate from
attr.*scopes.
Do Not Use
- Broad security intake where the correct spoke is still unclear.
- Vault and PKM storage or encryption-boundary work.
- Generic backend runtime or deploy work.
Read First
docs/architecture/identity/README.mddocs/architecture/identity/architecture.mddocs/architecture/identity/consent-scope-catalog.mddocs/architecture/identity/agent-delegation-boundary.mddocs/architecture/identity/validation-checklist.md.agents/skills/iam-consent-governance/references/anti-rationalization.md
Workflow
- Confirm whether the change is about actor model, scope catalog, verification gate, or runtime surface.
- Keep IAM docs, code, and validation checklists aligned in the same change.
- Treat vault and PKM boundary questions as
security-auditwork when they become primary. - Reject every Source Library
attr.*form; a local share row is mapping state, not access or revocation authority.
Handoff Rules
- If the request is still broad or ambiguous, route it back to
security-audit. - If the task becomes vault or PKM storage-boundary work, use
security-audit. - If the task becomes general backend runtime work, route it to
backend.
Required Checks
cd consent-protocol && python3 -m pytest tests/test_granular_scopes.py -q
cd consent-protocol && python3 -m pytest tests/test_ria_iam_routes.py -q
cd consent-protocol && python3 -m pytest tests/test_source_library_scope_policy.py -qDoes 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.

