agentleFS
hushh-labshushh-labs/hushh-research/.agents/skills/iam-consent-governance/SKILL.md

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.

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
  1. Very specific:

    Avoid overlap with security-audit and quality-contracts.

    line 12
  2. Distinctive:

    Keep IAM docs, code, and validation checklists aligned in the same change.

    line 58
  3. Very specific:

    Treat vault and PKM boundary questions as security-audit work when they become primary.

    line 59
  4. Very specific:

    If the request is still broad or ambiguous, route it back to security-audit.

    line 64
  5. Very specific:

    If the task becomes vault or PKM storage-boundary work, use security-audit.

    line 65
  6. Very specific:

    If the task becomes general backend runtime work, route it to backend.

    line 66

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-audit and quality-contracts.

Coverage and Ownership

  • Role: spoke
  • Owner family: security-audit

Owned repo surfaces:

  1. docs/architecture/identity
  2. consent-protocol/api/routes/iam.py
  3. consent-protocol/api/routes/consent.py
  4. hushh-webapp/lib/consent
  5. hushh-webapp/components/consent

Non-owned surfaces:

  1. security-audit
  2. backend
  3. docs-governance

Do Use

  1. Consent-scope, actor-model, and verification-gate changes.
  2. IAM runtime surface and marketplace access contract work.
  3. IAM docs and code alignment across frontend and backend.
  4. Opaque object-share references that must remain separate from attr.* scopes.

Do Not Use

  1. Broad security intake where the correct spoke is still unclear.
  2. Vault and PKM storage or encryption-boundary work.
  3. Generic backend runtime or deploy work.

Read First

  1. docs/architecture/identity/README.md
  2. docs/architecture/identity/architecture.md
  3. docs/architecture/identity/consent-scope-catalog.md
  4. docs/architecture/identity/agent-delegation-boundary.md
  5. docs/architecture/identity/validation-checklist.md
  6. .agents/skills/iam-consent-governance/references/anti-rationalization.md

Workflow

  1. Confirm whether the change is about actor model, scope catalog, verification gate, or runtime surface.
  2. Keep IAM docs, code, and validation checklists aligned in the same change.
  3. Treat vault and PKM boundary questions as security-audit work when they become primary.
  4. Reject every Source Library attr.* form; a local share row is mapping state, not access or revocation authority.

Handoff Rules

  1. If the request is still broad or ambiguous, route it back to security-audit.
  2. If the task becomes vault or PKM storage-boundary work, use security-audit.
  3. 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 -q

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.