AGENT SKILL

agent-doctrine-contracts

Use when adopting or assessing agent-facing doctrine and contracts, their repository locations, quality, or routes.

License 许可
MIT
最近更新
2026-10-08
Stars
★ 0
Forks
0

01 前言 Front Matter

name
agent-doctrine-contracts
license
MIT
metadata
{ "owner": "Harley Bartles", "status": "active", "use_when": [ "the human asks to adopt or assess the agent-doctrine-contracts standard.", "the repository subscribes to the standard and agent-facing doctrine or contract stores are changing." ], "source-id": "agent-doctrine-contracts", "source-path": "skills/agent-doctrine-contracts/SKILL.md", "do_not_use_when": [ "the files describe product schemas or API contracts rather than agent operating guidance.", "the repository has no subscription and no explicit adoption or assessment request for this standard." ], "provenance-name": "Agent Doctrine and Contracts first-party skill", "source-category": "first_party" }
description
Use when adopting or assessing agent-facing doctrine and contracts, their repository locations, quality, or routes.

02 资源文件 5

03 SKILL.md 正文

Agent Doctrine and Contracts

Use the agent doctrine and contracts standard 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. 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.

04 同仓库更多 Skills