CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

housekeeping

Run the recurring housekeeping pass — audit the agent files for rot, the glossary against the code, the decision index, the mutation measurement, the worktrees and the diary, then scan the codebase for Ousterhout's red flags and route each finding to the skill that owns it. It never fixes what it finds; findings leave as candidate tickets. Its one write of its own is stamping the diary's Last housekeeping row, and its one delegated action is the worktree pruning it hands to the cleanup skill. Use when the docs gate's housekeeping-due advisory fires, on the cadence the gate config names, or before cutting a release.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

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

An exemplary instruction-only skill body: dense and project-specific with zero filler, fully executable commands and templates, a checklist-plus-procedure structure with pre-flight states and explicit termination, and clean delegation of the checklist detail to CHECKLIST.md. Nothing scored below the top anchor on any dimension.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence throughout — it cites Ousterhout's red flags, ADR-0008, and shared invariants without explaining them, and every rationale line is kit-specific (e.g. "UTC, because the advisory that reads the row compares against UTC midnight") rather than general knowledge, so no token is spent on what Claude already knows.

5 / 5

Actionability

Guidance is copy-paste ready: `sh scripts/agents.lib.sh planner`, the full trace-emit command with its fallback `|| :`, the diary row template `| **Last housekeeping** | <today, ISO, UTC> — …`, and the report path format `<tmpdir>/housekeeping-<YYYYMMDDTHHMMSSZ>.md`, with concrete routing per finding class.

5 / 5

Workflow Clarity

The six-step procedure is clearly sequenced with explicit checkpoints: three pre-flight states (first pass, unstamped article, nothing to prune), per-item evidence requirements ("A pass that finds nothing says so, per item"), a defined stop condition, and an anti-patterns section covering failure modes; the pass is read-only, so no destructive-operation cap applies.

5 / 5

Progressive Disclosure

No bundle files were provided to verify, but scored on the body's structure: it is a well-organized overview that delegates the full checklist form to CHECKLIST.md with a clear signal ("The full form of each — what to look at, what counts as a finding, what to route it to — is in CHECKLIST.md"), a single well-signaled, one-level-deep reference.

5 / 5

Total

20

/

20

Passed

Description

92%Weight 40%Scale 1-5

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, highly specific description that states its full audit inventory, its non-fixing contract, and its two exceptions, with an explicit trigger clause. The only weakness is that triggers lean on the advisory and cadence mechanism rather than a broader spread of natural user phrasings.

DimensionReasoningScore

Specificity

The description enumerates every concrete audit action ("audit the agent files for rot, the glossary against the code, the decision index, the mutation measurement, the worktrees and the diary", "scan the codebase for Ousterhout's red flags and route each finding"), plus its single write and delegated action, in third person with no coverage gaps.

5 / 5

Completeness

It explicitly answers both questions: a detailed 'what' (the audit inventory, the never-fix rule, the diary stamp, the delegated pruning) and an explicit 'Use when…' clause naming the advisory, the cadence, and the pre-release trigger.

5 / 5

Trigger Term Quality

Triggers are mostly system-driven ("when the docs gate's housekeeping-due advisory fires, on the cadence the gate config names, or before cutting a release") with good natural terms ("housekeeping", "audit", "rot", "release"), but a few natural user phrasings and synonyms are missing, fitting the 'good coverage, a few natural terms missing' anchor rather than comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche ("the recurring housekeeping pass", the housekeeping-due advisory, the diary's Last housekeeping row) and names the adjacent skills it delegates to, so it is unlikely to fire for the wrong skill.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 3 possibly missing (scripts/agents.lib.sh, scripts/docs-conformance/config.mjs, scripts/trace.sh), 1 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

agranado2k/agentic-sdlc

Path

.agents/skills/housekeeping/SKILL.md

Reviewed

Table of Contents

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.