system-card

Regenerate SYSTEM-CARD.md with measured counts and verified evidence.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill system-card
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-card
Source: https://github.com/brucebanner010198-commits/DevSecOps-Agency/tree/main/skills/system-card
Command: npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill system-card

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerate SYSTEM-CARD.md at every minor version bump (v0.X.0) or after any material capability or limit change. The skill collects actual measured capabilities from the current repo state (councils, skills, hooks, founding docs), verifies claims against evidence, and produces the updated card. Trigger phrases include "regenerate system card", "update SYSTEM-CARD", "refresh system card", or any /devsecops-agency:system-card invocation.

Core Features & Use Cases

  • Verifies current governance state against the SYSTEM-CARD.md.
  • Reconciles claims with evidence from CONSTITUTION.md, AGENTS.md, root docs, and runtime state.
  • Produces a versioned, audit-ready SYSTEM-CARD.md to inform risk and governance.

Quick Start

Trigger the system-card skill to regenerate SYSTEM-CARD.md during every minor version bump.

Frequently Asked Questions about system-card

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I regenerate a system card for governance and compliance auditing?

Regenerating a system card involves collecting actual measured capabilities from repo sources, verifying claims against evidence, and outputting an updated, versioned card for governance and compliance auditing.

What is a system card used for in repo governance and versioning?

A system card serves as an audit-ready record of governance and capability states, ensuring material changes across versions are reconciled with evidence from founding docs and runtime state.

When do I need to update my system card during the development lifecycle?

You need to update your system card during every minor version bump or whenever a material capability or limit claim changes across the repo's councils, skills, hooks, and founding documents.

How to verify governance claims against evidence in a repository?

Verifying governance claims involves reconciling the current state with sources like CONSTITUTION.md, AGENTS.md, and runtime state to measure actual counts and produce an audit-ready system card.

Can I use a system card to track capability limits across councils and hooks?

Yes, you can use a system card to track capability limits by measuring actual counts from councils, skills, and hooks, then verifying those limit claims against repository evidence.

What are the limitations of manual system card updates for compliance?

Manual system card updates risk unverified claims and inaccurate versioning, failing to reconcile actual measured capabilities with evidence from founding docs and runtime state during audits.