agent-doctrine-contracts

Files (6)

• SKILL.md
• openai.yaml · agents/
• check_agent_docs.py · assets/
• standard.md · references/
• checker-starter.md · tests/behavior/
• test_check_agent_docs.py · tests/scripts/

SKILL.md (first lines)

# Agent Doctrine and Contracts

Use the [agent doctrine and contracts standard](references/standard.md) when a repository explicitly adopts or asks to assess `agent-doctrine-contracts`. It governs agent-facing operating knowledge, not product schemas merely named contracts.

AOM offers an editable [checker starter](assets/check_agent_docs.py). Copy and adapt it into a repository-owned location; the plugin copy is not the repository's implementation. It checks that `.agents/doctrine/` and `.agents/contracts/` exist, parses JSON syntax without imposing a schema, and checks inline and reference-style local Markdown links and images in those stores and in explicitly selected `--route-root` sources; inline and block code examples do not count as links. Other Markdown files can contribute inbound-link evidence for advisory candidate reporting, but their unrelated broken links do not fail this check. It reports any recognized agent document without a static Markdown inbound link as an advisory candidate, including JSON, YAML, and TOML documents. Use `--exclude` for repository-specific boundaries. The starter cannot identify agent documents misplaced elsewhere, establish semantic reachability, or see harness scope, skill metadata, plugin/tool registries, and other non-Markdown routes. Adapt it and add the semantic review your repository needs. A repository adopting this standard must maintain its own checker and run it in CI when CI exists; it owns any hook integration and continuing certification.

From HarleyBartles/agent-asset-marketplace, MIT.

More from HarleyBartles/agent-asset-marketplace