magnus919/agent-skills

ai-governance

Design and operate AI governance: principles, decision rights, risk tiers, lifecycle gates, fairness, transparency, privacy, security, compliance mapping, maturity and board reporting across SaaS, API, self-hosted and agentic systems.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/magnus919/agent-skills --skill ai-governance

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

AI Governance

AI governance is the system an organization uses to decide, before a model is built and while it runs, who is accountable for an AI system, what risk it is allowed to carry, what evidence must gate each lifecycle stage, and how the organization reports and audits that posture. This skill teaches an agent to reason about and operate that system: it is a methodology skill, not a tool manual and not legal or security advice.

Scope: What This Skill Owns

You ownYou don't own
Governance principles and how they translate into policy and controlsDrafting or opining on legal interpretation of a regulation
The governance operating model: councils, stewards, decision rights, RACI, federated vs. centralizedData-platform mechanics, pipelines, and lineage tooling internals
Risk frameworks: NIST AI RMF, ISO/IEC 42001 & 23894, model-risk tiering, risk registersImplementing authentication, authorization, or vulnerability fixes
Lifecycle stage gates across ideation, build, evaluate, deploy, monitor, retireCI/CD pipeline and deployment-gate configuration
Cross-cutting 6L-G governance loop: strategy, impact, implementation, acceptance, operations, learningTreating an author-developed framework as a regulatory or standards requirement
Fairness, bias, transparency, explainability, and accountability controlsProduct portfolio/roadmap governance cadences
Privacy and data governance for training and operational dataCapital allocation, org structure, or M&A governance
GxP AI governance overlay: ALCOA+, data integrity, electronic records, risk-based assurance, QMS interfacesLegal applicability determinations, validation protocols, SOPs, or quality-system operation
LLM/agent safety: prompt injection, exposure ladders, tool authorization, memory, egress, red-teaming, supply chainHost-level or application-level security scanning
Regulatory landscape and compliance mapping (as guidance, not advice)Legal drafting, regulatory filings, or attorney-client work product
Third-party and model due diligence, board reporting, auditAny authoritative statement of "your system is compliant"

This is a prevention-and-operations methodology: it gives the agent frameworks, decision models, and controls to design and run governance, not a claim that a system is compliant or safe. For every engagement, record the operating model, the risk tier, the evidence that gated each stage, and the accountable owner of each accepted exception.

When To Use

Load this skill to answer "how should we govern this AI system?" — standing up or maturing a governance program, tiering use-case risk, designing the operating model and decision rights, reviewing an LLM/agent system for governance and safety gaps, mapping a regulation to a compliance/control plan, scoring governance maturity, or preparing board-level reporting.

Capability admission and authority decisions

For “may this capability enter or remain in our environment?”, read references/capability-admission-and-update.md and use templates/capability-admission-record.md. For “may this agent act?”, use the earned-autonomy path below. Admission approves a component at a recorded revision and configuration; it does not issue a runtime grant. Link the two records in one review when both decisions are needed. Reuse current evidence and existing authorized scope; request a new decision only for a material change or an unmet approval condition.

Earned autonomy

When setting agent promotion/demotion thresholds or reviewing earned autonomy, read references/earned-autonomy.md and use templates/earned-autonomy-decision.md. Support accountable humans making capability/environment/action-class decisions; the agent cannot grant itself authority. site-reliability-engineering supplies operational evidence and agent-production-operations implements the approved control plan. This five-level autonomy ladder is separate from the Six-Level Governance framework.

Agentic engineering decision rights

When deciding which software-factory decisions remain with humans and which an agent may execute, read references/agentic-engineering-governance.md and use templates/engineering-decision-rights.md. Reuse scoped grants; distinguish technical readiness, intent acceptance, residual-risk acceptance and production authority. Check whether reserved human review has enough evidence, capacity and ability to stop the action.

Protected control-plane decisions

When an agent could weaken its own supervision, load protected-control governance and use the protected-control registry. Monitoring, alert routes, audit sinks, authority ceilings, kill switches, evaluator oracles, and gate configuration are protected assets. The controlled agent cannot be sole approver or sole evidence source for changing them. Missing, degraded, redirected, or suppressed mandatory controls are control-integrity incidents, not ordinary task failures. Governance owns rights and bounded human exceptions; operations verifies live controls, security designs external enforcement, harnesses cover child workloads, and evals challenge the evidence.

Reference Files (load on demand, one per task)

Progressive disclosure: load only the reference relevant to the current question.

Load whenReference
Framing what AI governance is and its principles; governance vs. compliance vs. riskreferences/foundations-and-principles.md
Designing the operating model, councils, stewards, decision rights, RACI, maturity, culturereferences/governance-operating-model.md
Applying NIST AI RMF, ISO/IEC 42001 & 23894, model-risk tiering, inherent vs. residual riskreferences/risk-management-and-frameworks.md
Placing stage gates across ideation, data, build, evaluate, deploy, monitor, retirereferences/ai-lifecycle-governance.md
Applying the Six-Level Governance framework, evidence loop, maturity, and posture overlayreferences/six-level-governance-framework.md
Fairness metrics and their limits, bias sources, trade-offs, algorithmic justicereferences/fairness-bias-accountability.md
Explainability (XAI) methods, when explanation is required, disclosure, auditabilityreferences/transparency-and-explainability.md
Training/operational data governance, ownership, lineage, quality, consent, PETs, agentic memory, and purpose-aware egressreferences/privacy-and-data-governance.md
AI used in GLP, GCP, GMP, GDP, or pharmacovigilance contexts; ALCOA+, data integrity, electronic records, audit trails, validation/assurance, and QMS interfacesreferences/gxp-and-data-integrity.md
Trust boundaries, prompt injection, exposure ladders, excessive agency, tool authorization, containment, supply chain, red-teamingreferences/llm-and-agent-security.md
Current law by jurisdiction, compliance mapping, enforcement, horizon scanningreferences/regulatory-landscape.md
Vendor/model due diligence, supply chain, board reporting, metrics, auditreferences/procurement-third-party-and-board-oversight.md
Admitting, updating, disabling or retiring Skills, MCP servers or A2A capabilitiesreferences/capability-admission-and-update.md
Granting, promoting, reducing, suspending or revoking scoped agent authorityreferences/earned-autonomy.md
Assigning software-factory decision rights, protected terms and meaningful human oversightreferences/agentic-engineering-governance.md
Tracing any idea to its informing books and research notes; bibliographyreferences/source-index.md

Templates (fillable)

Use these to turn the methodology into working artifacts.

Use whenTemplate
Recording capability admission, configuration changes, overlap and exittemplates/capability-admission-record.md
Recording scoped authority, evidence, counterevidence and independent approvaltemplates/earned-autonomy-decision.md
Recording engineering delegation, reserved human decisions and enforcement handoffstemplates/engineering-decision-rights.md
Standing up the governance council and its terms of referencetemplates/governance-charter.md
Registering a use case and classifying it at intaketemplates/use-case-intake-form.md
Running a NIST-aligned risk assessment and tiering worksheettemplates/model-risk-assessment.md
Documenting a released model: intended use, data, performance, fairness, limitationstemplates/model-card.md
Conducting vendor/model supply-chain due diligencetemplates/third-party-due-diligence.md
Preparing executive/board AI-governance reportingtemplates/board-ai-governance-report.md
Reviewing SaaS/API/self-hosted boundaries and agentic tools, actions, egress, memory, and evidencetemplates/agentic-governance-review.md

Scripts

Executable, flag-driven, stdlib-only Python CLIs with tests. Both accept a JSON input path and emit deterministic output; --json prints one JSON object on stdout; --dry-run previews without changing anything. Exit 0 on success; the maturity scorer also exits 1 on a critical posture, and both scripts exit 1 on input errors.

Use whenScript
Scoring an organization's governance maturity from dimension scores (1-5); emits maturity level + gapsscripts/governance-maturity.py
Classifying an AI use case into a risk tier and its required controlsscripts/use-case-risk-tier.py
Verifying the maturity scorer (unit + behavior tests)scripts/test_governance_maturity.py
Verifying the risk-tier classifier (unit + behavior tests)scripts/test_use_case_risk_tier.py

Evaluation and Configuration

model design, use-case risk tiering, 6L-G and deployment-posture review, agentic security and privacy review, impact-assessment closure, LLM-app governance review, fairness/accountability review, regulatory compliance mapping, board governance reporting, and GxP/data-integrity governance) used to grade this skill.

  • Configuration: pytest.ini overrides the repository's root coverage settings so

the subprocess-based skill tests run cleanly; do not add a second override.

human-facing overview for people evaluating whether to install the skill.

When Not To Use

Do not load this skill for work that belongs to a neighbor methodology or to execution:

  • Regulatory/legal strategy. Interpreting what a law or regulation means, structuring

compliance legal risk, or preparing legal positions is legal-strategy work. This skill maps obligations to controls and records a defensible governance posture; it does not opine on the law. Prefer legal-strategy when the ask is legal interpretation, and return here to turn the resulting obligations into a control plan.

  • Product operations and governance. Recurring product decision cadences (intake, portfolio,

roadmap, experiment, launch, lifecycle reviews) with evidence standards belong to product-operations-and-governance, not to this skill. This skill governs the AI system's risk and accountability, not the product portfolio cadence.

  • Data-governance mechanics. Building data catalogs, lineage pipelines, or platform storage

internals is data-architect / data-engineering work. This skill consumes data governance as a control input but does not operate the data platform.

  • Implementation-time security. Writing authentication, authorization, input validation, or

dependency hardening for an application is secure-software-engineering work. This skill sets the AI governance and safety controls and the risk tier; it does not implement the security mechanisms.

  • Legal, financial, or security advice. Nothing in this skill is legal, financial, or security

advice. Regulatory and standards material must be re-verified against primary sources at the time of use.

  • Other one-off decisions. Use adr-authoring or product-methodology for general

architectural or product decisions. Individual AI capability admission and authority decisions remain in this skill.

Related Skills (routing)

When you need...Route to
Regulatory and board-legal strategy, legal interpretationlegal-strategy
Data-governance mechanics: catalogs, lineage, platform internalsdata-architect or data-engineering
Implementing application and system security controlssecure-software-engineering
Recurring product decision cadences and evidence standardsproduct-operations-and-governance
A single durable architectural decision recordadr-authoring
dallo stesso repository

Altri Skills

Tutti gli Skills
magnus919
Community

amazon-memo

Create, adapt, or revise Amazon-style narrative decision memos, six-pagers, PR/FAQs, and short decision briefs, including reading meetings and async review. Use for choosing the right memo form, evidence-led reasoning, and revising mechanical AI prose for human readers. Do not use for general copywriting, document rendering, or replacing incident reports and technical design records.

Installazioni / 1h
1
GitHub Stars
172
Aggiornato
8 nov
magnus919
Community

analog-occultism

Use this skill to create subject-neutral images and videos in an analog occultism / industrial CRT noir aesthetic: near-monochrome archival technical atmosphere, severe low-key lighting, tactile signal degradation, industrial geometry, and quiet unresolved tension. Use for portraits, products, environments, interfaces, diagrams, abstract forms, stills, and motion. Do not use for colorful cyberpunk, vaporwave, glossy advertising, conventional horror, or clean digital renders.

Installazioni / 1h
1
GitHub Stars
172
Aggiornato
8 nov
magnus919
Community

binary-analysis

Plan static inspection of unknown binary files with a deterministic CLI whose Ghidra operations are currently unimplemented and fail closed. Use when you need to inspect a PE, ELF, or Mach-O file — triage suspicious binaries, map imported APIs, decompile functions, trace call paths, or produce structured evidence reports. Do not use for runtime analysis (debugging, dynamic tracing, sandbox execution), for modifying or patching binaries, or for binaries you already know everything about. The skil

Installazioni / 1h
1
GitHub Stars
172
Aggiornato
8 nov
magnus919
Community

brand-designer

Create comprehensive brand identity documentation for any brand. Guides you through documenting strategy, visual identity (logo, color, typography, imagery), voice and tone, customer-centered messaging handoffs, application guidelines, governance, and asset inventory. Produces markdown specs, compiled brand books, and brand-compliant images via reference-image-aware generation. Use when you need to capture a brand's identity in structured, durable form — for vault storage, agency handoff, or pre

Installazioni / 1h
1
GitHub Stars
172
Aggiornato
8 nov