CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

94

1.08x
Quality

95%

Does it follow best practices?

Impact

90%

1.08x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

92%

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

A well-structured, actionable instruction skill with a clear sequenced workflow and concrete commands. Its one real defect is progressive disclosure: every referenced bundle file is a broken link because the references/ directory is absent.

Suggestions

Create the missing references/grading.md, references/setup-patterns.md, and references/industry-examples.md (or remove the inline links and the References section) so the signaled detailed material actually exists.

Keep the detailed .worktreeinclude and setup-pattern guidance in references/setup-patterns.md rather than expanding it further inline in SKILL.md.

After adding the bundle files, verify each inline link resolves before publishing so navigation matches the signaling.

DimensionReasoningScore

Conciseness

Lean, skill-specific content that assumes Claude's competence — it does not explain what boot/smoke/CI concepts are, and every section (7-layer stack, workflow, output) earns its place with actionable detail.

3 / 3

Actionability

Provides concrete, copy-paste-ready commands (pnpm dev, cargo run, docker compose up, curl .../health, make verify, just verify, ./scripts/verify.sh) plus a concrete audit-output example and a labeled output template.

3 / 3

Workflow Clarity

Clear four-phase sequence (Audit → Setup → Improve → Stop) with an explicit build order, a grading/validation loop (pass/partial/fail, lowest dimension sets grade), and an explicit stop criterion ("reaches C and can be judged honestly").

3 / 3

Progressive Disclosure

The overview is well-organized and references are clearly signaled one level deep (grading.md, setup-patterns.md, industry-examples.md), but the references/ directory does not exist, so all three links are broken and navigation fails the "easy navigation" bar.

2 / 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.

A strong, third-person description that pairs concrete capabilities with explicit natural-language triggers and an anti-trigger. It clearly communicates both what the skill does and when to invoke it, with low conflict risk.

DimensionReasoningScore

Specificity

Lists many concrete actions — "boot scripts, smoke tests, CI/CD gates, dev environment setup, observability, worktree isolation, and .worktreeinclude handling" — rather than vague language, matching the multi-action anchor.

3 / 3

Completeness

Explicitly answers both what (audit/build agent infrastructure) and when ("Use when...") plus an explicit anti-trigger ("Do not use for reviewing an existing diff or for documentation-only cleanup").

3 / 3

Trigger Term Quality

Natural trigger phrasing a user would actually say — "a repo can't boot, tests are broken or missing, there's no dev environment, agents can't verify their work, agents need human help" — with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Clear niche (agent-readiness infrastructure) with distinct triggers and an explicit exclusion clause that separates it from diff-review and documentation skills, making wrong-skill conflicts unlikely.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 missing

Warning

referenced_paths_exist

Referenced path issues: 10 missing

Warning

Total

14

/

16

Passed

Reviewed

Table of Contents