uinaf/docs
Update repo documentation and agent-facing guidance such as AGENTS.md, README.md, docs/, specs, plans, and runbooks. Use when code, skill, or infrastructure changes risk doc drift or when documentation needs cleanup or restructuring. Do not use for code review, runtime verification, or `agent-readiness` setup.
98
100%
Does it follow best practices?
Impact
94%
1.00xAverage 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, provides concrete file targets and actions, includes both positive and negative trigger conditions, and uses proper third-person voice throughout. The 'Do not use' clause is a particularly strong addition that reduces ambiguity and conflict with related skills. Minor improvement could include mentioning 'update docs' as a common shorthand trigger term.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Update repo documentation and agent-facing guidance' with explicit file targets (AGENTS.md, README.md, docs/, specs, plans, runbooks). Also specifies cleanup and restructuring as actions. | 3 / 3 |
Completeness | Clearly answers both 'what' (update repo documentation and agent-facing guidance for specific file types) and 'when' (when code/skill/infrastructure changes risk doc drift, or when docs need cleanup/restructuring). Also includes explicit 'Do not use' negative triggers, which further strengthens completeness. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'documentation', 'AGENTS.md', 'README.md', 'docs/', 'specs', 'plans', 'runbooks', 'doc drift', 'cleanup', 'restructuring'. These cover a wide range of terms a user might naturally use when needing documentation updates. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to documentation maintenance with explicit negative boundaries ('Do not use for code review, runtime verification, or agent-readiness setup'), making it highly distinguishable from code review skills, testing skills, or setup skills. The specific file targets (AGENTS.md, README.md, etc.) further reduce conflict risk. | 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 a well-crafted skill that efficiently covers documentation maintenance with clear workflows, concrete validation steps, and appropriate progressive disclosure. The handoff section cleanly delineates scope boundaries, the workflow steps are logically sequenced with validation, and the references are one level deep and well-signaled. The diff example and shell commands make the guidance immediately actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. No unnecessary explanations of what documentation is or why it matters beyond the brief principles. Every section earns its place with actionable guidance rather than filler. | 3 / 3 |
Actionability | Provides concrete file names to check, specific commands like `rg -n` and `test -e` for validation, a diff example for fixing stale paths, and clear checklists for what to audit and update. The guidance is specific and directly executable. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced from audit → update routing → update deep docs → clean drift → validate reality. Step 5 includes explicit validation commands and verification checks, providing a proper feedback loop to ensure docs match reality. | 3 / 3 |
Progressive Disclosure | The skill keeps its own content at the right level of abstraction, with clear references to `references/documentation.md` and `references/specifications.md` for deeper detail. Handoffs to other skills are clearly signaled at the top. No nested reference chains. | 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