repo-standards

Files (15)

• SKILL.md
• AGENTS.md.example · assets/templates/
• operating-standards-v2.example.json · assets/templates/
• standards-certification.md.example · assets/templates/
• adoption-and-certification.md · references/
• source-resolution.md · references/
• standards-catalog.json · references/
• subscriptions.schema.json · references/
• pinned_definition.py · scripts/
• subscriptions.py · scripts/
• adoption-workflow.md · tests/behavior/
• authority-routing.md · tests/behavior/
• standard-selection.md · tests/behavior/
• test_pinned_definition.py · tests/scripts/
• test_subscriptions.py · tests/scripts/

SKILL.md (first lines)

# Repo Standards

Agent Operating Model (AOM) publishes selectable standards. Availability is not adoption. A repository owns its implementation and self-certification after adopting a standard.

For assessment or adoption, read [adoption and certification](references/adoption-and-certification.md), then inspect `.agents/contracts/operating-standards.json` and the certification it names. The current choices are listed in [the standards catalog](references/standards-catalog.json). A missing subscription means non-adoption unless the user asks to adopt. Do not infer adoption from installed skills, existing files, or an ambient catalog.

For an explicit adoption task, follow the [agent-led adoption sequence](references/adoption-and-certification.md#adoption-workflow). Editable [subscription](assets/templates/operating-standards-v2.example.json), [root router](assets/templates/AGENTS.md.example), and [certification](assets/templates/standards-certification.md.example) examples are available. Treat example values as placeholders and replace them with repository facts before deployment.

Honor the source and immutable commit recorded by the repository. A v1 record identifies historical deployed authority; retrieve the exact definition and resources from its immutable source commit. Do not use a current plugin snapshot as an upgrade. A v2 record identifies the source repository, full commit, definition path, and certification reference; retrieve that exact object, including when its standard is absent from today's catalog. The catalog presents current choices, not an update alarm. Upgrades are explicit reconciliation work.

After selecting the pinned authority, route to the smallest owner:

| Concern                                                  | Skill                      |
| -------------------------------------------------------- | -------------------------- |
| Subscription, certification, and broad routing           | `repo-standards`           |
| Runbook lifecycle stages and playbook concerns           | `repo-composition`         |
| Repository plugin dependencies and local authored skills | `repo-agent-assets`        |
| AGENTS.md routing                                        | `agents-routing`           |
| Git branch and release routing                           | `gitflow`                  |
| Product compatibility version and release identity      | `semver`                   |
| Agent doctrine and contracts                             | `agent-doctrine-contracts` |
| Tracked hook and hosted CI parity                        | `tracked-repo-hooks`       |
| Named command targets                                    | `command-bus`              |
| Focused checks and evidence                              | `repository-validation`    |

Use other focused standard skills named in the pinned definition or current catalog. Compose owners only when the requested change crosses their boundaries. Historical pins remain readable from their exact source commit; they do not add obligations to current v2 adopters.

From HarleyBartles/agent-asset-marketplace, MIT.

More from HarleyBartles/agent-asset-marketplace