Name: agent-readiness-audit
Rating: 74.4 (1 reviews)
Author: docker

agent-readiness-audit

Audit a documentation site for agent-friendliness: discovery, markdown delivery, crawlability, semantic structure, machine-readable surfaces, and content legibility. Use when asked to assess docs.docker.com or any docs site for AI/agent readiness, produce a scored report, compare with external scanners, or generate a remediation list. Triggers on: "audit docs for agent readiness", "how agent-friendly is docs.docker.com", "score our docs for AI agents", "review llms.txt / markdown / crawlability", "create an agent-readiness remediation plan".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, actionable audit workflow with executable commands, real bundled references, and clear sequencing with verification checkpoints. Its only meaningful weakness is mild redundancy across the markdown-delivery guidance and repeated 'Do not...' guardrails, which keeps conciseness just below the top anchor.

Suggestions

Consolidate the markdown-delivery guidance: sections 4, 5, and the Notes each restate markdown/parity concerns — fold the Notes restatements into the relevant sections to remove redundancy.

Tighten the repeated 'Do not...' guardrails (e.g. the homepage-scan and manifest warnings appear more than once) into a single concise guardrail per topic.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and action-oriented with no over-explanation of concepts Claude already knows, but it carries some redundancy — markdown deliverability is revisited across sections 4, 5, and Notes, and several 'Do not...' guardrails restate the same guidance, so it could be tightened. It sits above the verbose level-1 anchor but short of the fully lean level-3 anchor.	2 / 3
Actionability	Provides copy-paste-ready executable commands ('bash .agents/skills/agent-readiness-audit/scripts/baseline-probes.sh "$ARGUMENTS"' with a CHECK_TOOL_MANIFESTS=0 variant), exact resource paths to probe (/llms.txt, /robots.txt, /.well-known/ai-plugin.json), and specific per-page checks, matching the level-3 fully-executable anchor for an instruction skill.	3 / 3
Workflow Clarity	Presents a clear 9-step sequence (scope, sitewide signals, sampling, per-page checks, judging, scoring, comparison, remediation, report) with explicit verification checkpoints ('score only what you verified', 'trust the live fetch', 'report the mismatch explicitly') and confidence/normalization rules, matching the level-3 anchor.	3 / 3
Progressive Disclosure	The overview body signals one-level-deep references to verified bundle files ([references/rubric.md], [references/report-template.md], scripts/baseline-probes.sh), keeping the scoring rubric and report template externalized rather than inlined, matching the level-3 clear-overview-with-well-signaled-references anchor.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinctive: it states concrete capability areas and deliverables, gives an explicit 'Use when' clause with natural-language trigger phrases, and occupies a clear niche unlikely to conflict with other skills. No verbosity, buzzwords, or voice issues are present.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas ('discovery, markdown delivery, crawlability, semantic structure, machine-readable surfaces, and content legibility') plus concrete deliverables ('produce a scored report, compare with external scanners, or generate a remediation list'), matching the level-3 anchor of multiple specific actions.	3 / 3
Completeness	Explicitly answers both what ('Audit a documentation site for agent-friendliness...') and when ('Use when asked to assess docs.docker.com or any docs site for AI/agent readiness...') with an explicit 'Use when' trigger clause, matching the level-3 anchor.	3 / 3
Trigger Term Quality	Provides quoted natural-language triggers users would actually say ('audit docs for agent readiness', 'how agent-friendly is docs.docker.com', 'score our docs for AI agents', 'review llms.txt / markdown / crawlability', 'create an agent-readiness remediation plan'), giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (agent-readiness auditing of documentation sites) with distinct triggers unlikely to overlap with other skills, matching the level-3 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: docker/docs
Commit: 67d0999

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.