uinaf/agent-readiness
Audit and build the infrastructure a repo needs so agents can work autonomously — boot scripts, smoke tests, CI/CD gates, dev environment setup, observability, and isolation. Use when a repo can't boot, tests are broken or missing, there's no dev environment, agents can't verify their work, or agents need human help to get anything done. Do not use for reviewing an existing diff or for documentation-only cleanup.
99
100%
Does it follow best practices?
Impact
97%
1.15xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that clearly defines its scope (infrastructure for agent autonomy), lists specific concrete deliverables, provides multiple natural trigger scenarios via a 'Use when' clause, and even includes exclusion criteria via 'Do not use'. It uses proper third-person voice throughout and would be easily distinguishable from other skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: boot scripts, smoke tests, CI/CD gates, dev environment setup, observability, and isolation. These are clearly defined infrastructure components. | 3 / 3 |
Completeness | Clearly answers 'what' (audit and build infrastructure — boot scripts, smoke tests, CI/CD gates, etc.) and 'when' (explicit 'Use when' clause with multiple trigger scenarios). Also includes a 'Do not use' clause which further clarifies boundaries. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'repo can't boot', 'tests are broken or missing', 'no dev environment', 'agents can't verify their work', 'CI/CD', 'smoke tests'. These cover common pain points users would describe naturally. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around agent-readiness infrastructure for repos. The explicit 'Do not use' clause for diff review and documentation cleanup further reduces conflict risk with other skills. The focus on agent autonomy and repo bootstrapping is highly distinctive. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that efficiently communicates a complex multi-layered readiness framework. It balances conciseness with actionability — providing executable code where needed while keeping the overall structure navigable. The workflow is well-sequenced with validation checkpoints, clear handoff criteria, and appropriate progressive disclosure to reference files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude's competence throughout — no explanations of what CI/CD is, what curl does, or how bash works. Every section earns its place with concrete guidance, and the 7-layer stack is presented as a compact reference table rather than verbose prose. | 3 / 3 |
Actionability | Provides executable bash scripts for boot and enforce steps, concrete curl commands for smoke checks, a specific grading format with example output, and a structured output template. The workflow steps are concrete and copy-paste ready where code is needed. | 3 / 3 |
Workflow Clarity | The 4-step workflow (Audit → Setup → Improve → Hand Off) is clearly sequenced with explicit ordering within Setup (Boot → Smoke → Interact → E2e → Enforce → Observe → Isolate). The audit step includes validation criteria (pass/partial/fail), the boot script includes a health-check feedback loop with timeout and error handling, and there are clear handoff conditions (C+ grade threshold). | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to grading.md, setup-patterns.md, and industry-examples.md. Core patterns are inline while advanced/detailed patterns are appropriately delegated to reference files. The boundary section cleanly routes to other skills (review, verify, docs). | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents