CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prior-work-retrieval

Only for explicit prior-work/reuse/history requests, not status checks. Finds and verifies existing work before new production when reuse is plausible. Use when the user explicitly references earlier work, existing code, history, or prior decisions, or says 以前做过, 已有代码, 别重复造轮子. Not for current tests, files, bug fixes, or mechanical verification. Produces a reuse/adapt/reject receipt; zero hits never prove absence.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./daymade-claude-code/prior-work-retrieval/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%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.

The body delivers an exceptionally rigorous, validated workflow: every step has an executable command, machine-checkable gates, and explicit error-recovery loops. Its main defect is token efficiency — a large fraction of the file is hook/classifier operational policy and maintenance procedure that should live in one-level-deep reference files like the existing source-manifest and visual-result-reuse docs, which would also sharpen progressive disclosure.

Suggestions

Move the Companion hooks section's classifier filter cases, opt-out phrasing table, and --reclassify-requirement maintenance procedure into a dedicated reference file (e.g., references/hook-policy.md), keeping in SKILL.md only the install commands and a summary of what each hook enforces.

Add one worked retrieve example with realistic --business-outcome/--outcome-term/--term values so the placeholder templates ('distinctive entity', 'old workflow name') become concrete, copy-paste-ready guidance.

Merge the zero-candidate and returned-results-uninspected passages into a single 'closing both directions' subsection to remove the repetition ("Pair this with the zero-candidate clause above") that currently re-explains the same rule twice.

DimensionReasoningScore

Conciseness

At ~465 lines the body is noticeably verbose: it does not explain basics Claude knows (good), but it inlines extensive policy edge-case prose — e.g., the hook classifier filter taxonomy ("Internal templates (`You are a/an …`)... never arm a requirement"), the reclassify-requirement maintenance mode, and the twice-explained zero-candidate vs returned-results dismissal rules ("Pair this with the zero-candidate clause above"). This matches anchor 2's "several unnecessary explanations or padded sections" relative to a skill body; it does not reach 3 because much of this material is not needed at point-of-use in SKILL.md at all.

2 / 5

Actionability

Commands are concrete and executable throughout: `uv run --no-project python scripts/prior_work.py --manifest <path> validate-manifest`, a fully worked verify_artifact.py invocation with real-looking values (`--candidate /tmp/agent-backup.zip --member skills/editor/SKILL.md`), the complete/check commands, and hook selftest/install invocations. It falls short of anchor 5 because the central retrieve command's arguments are placeholder templates ('the observable result the user actually needs', 'distinctive entity') with no worked example showing what good terms look like.

4 / 5

Workflow Clarity

A five-step numbered workflow (read context → validate manifest → retrieve → verify at authority → complete receipt) with an explicit five-condition completion contract, machine-enforced checkpoints (`scripts/prior_work.py check` must accept the receipt; "Only after this passes should substantial production begin"), exit-code semantics for verification (0/1/2), and a clear feedback loop ("If completion reports changed source evidence or scope, retrieve again... inspect the affected results and complete the new run"). This matches anchor 5's sequence + validation + feedback loops + checklist pattern.

5 / 5

Progressive Disclosure

The bundle structure is used well: both reference files exist and are clearly signaled at point of need ("The schema and carrier examples are in `references/source-manifest.md`", "[visual-result reuse](references/visual-result-reuse.md)", a deep-linked anchor `references/source-manifest.md#source-fields`), and referenced scripts all exist, one level deep. It falls short of anchor 5 because substantial content that belongs in a reference — the ~120-line Companion hooks section with classifier filter cases, opt-out phrase tables, and the reclassify-requirement maintenance procedure — is inlined in SKILL.md rather than split out.

4 / 5

Total

15

/

20

Passed

Description

87%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 description: it answers what, when, and when-not explicitly, uses natural trigger phrasings in both English and Chinese, and carves out a distinct niche with active disambiguation from neighboring request types. The only weakness is that a few common trigger synonyms are absent and the capability list, while concrete, could enumerate the workflow's outputs more fully.

DimensionReasoningScore

Specificity

The description names several concrete actions — "Finds and verifies existing work", "Produces a reuse/adapt/reject receipt" — plus a concrete output contract ("zero hits never prove absence"). It stops short of anchor 5's comprehensive coverage because the retrieval/verification mechanics (carriers, manifest, receipt gate) are only implied, and short of nothing below since the actions are specific rather than generic.

4 / 5

Completeness

Both what and when are answered explicitly: what — "Finds and verifies existing work... Produces a reuse/adapt/reject receipt"; when — "Use when the user explicitly references earlier work, existing code, history, or prior decisions, or says 以前做过, 已有代码, 别重复造轮子", reinforced by an explicit negative scope ("Not for current tests, files, bug fixes, or mechanical verification"). This matches the anchor-5 example pattern of concrete what plus explicit trigger phrases.

5 / 5

Trigger Term Quality

Good natural-language coverage in two languages: "prior-work", "reuse", "history", "earlier work", "existing code", "prior decisions", plus 以前做过, 已有代码, 别重复造轮子. It falls below anchor 5 because a few common natural phrasings are missing (e.g., "don't reinvent the wheel", "we already built/discussed this", "previous approach"), while clearly exceeding anchor 3's partial keyword coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche with distinct triggers: it opens with "Only for explicit prior-work/reuse/history requests, not status checks" and explicitly excludes current-file inspection, bug fixes, and mechanical verification. Conflict with adjacent skills (code search, status checks, summarization) is proactively warded off, meeting the anchor-5 criterion.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

daymade/claude-code-skills

Path

daymade-claude-code/prior-work-retrieval/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.