CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ds-intake-audit

Use when a quest does not start from a blank state and the agent must first audit, trust-rank, and reconcile existing baselines, results, drafts, or review materials before choosing the next anchor.

Quality

82%

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

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

A well-structured, actionable instruction-only skill with a clear six-step workflow, named tool calls, and a genuine one-level-deep template reference. It falls short of top marks due to elided parameters in artifact calls, the absence of an explicit validate/retry loop in the reconciliation step, and inline taxonomy/routing content that could be offloaded to references.

Suggestions

Replace elided parameters in artifact calls (e.g., 'artifact.attach_baseline(...)') with the required arguments or one minimal worked example so the guidance is copy-paste ready.

Add an explicit validation checkpoint in the trust-rank/reconcile step (e.g., what to do when verification of an existing baseline fails: re-verify, downgrade trust level, or route to 'baseline') to close the missing feedback loop.

Move the trust-level taxonomy and companion-skill routing tables into a reference file and link 'references/state-audit-template.md' markdown-style, trimming the main body's length.

DimensionReasoningScore

Conciseness

The body is directive-dense with no teaching of known concepts, and system-specific details (tool cadence, startup_contract fields) earn their tokens. A few emphasis/explanatory lines ('This skill exists because many quests do not start from a clean slate', 'The point is to reuse prior route knowledge...') could be trimmed. Not score 5 because of those minor instances; not score 3 because padding is rare and the document largely assumes Claude's competence.

4 / 5

Actionability

Concrete, specific guidance throughout: exact tool calls ('memory.list_recent(scope=\'quest\', limit=5)', 'artifact.record(payload={\'kind\': \'decision\', ...})'), named files to inspect ('brief.md', 'plan.md', 'artifacts/', 'baselines/'), and a real template at 'references/state-audit-template.md'. Not score 5 because most artifact calls use elided parameters ('artifact.attach_baseline(...)') rather than copy-paste-ready signatures; not score 3 because guidance is mostly executable with only minor gaps.

4 / 5

Workflow Clarity

A clear six-step numbered sequence (read startup intent, retrieve memory, inventory, trust-rank/reconcile, choose next anchor, report/hand off) with an explicit insufficiency guard ('If the evidence is insufficient for a durable backfill, record that insufficiency explicitly instead of inventing a cleaned-up history') and non-negotiable rules acting as checkpoints. Not score 5 because there is no explicit validate-then-retry loop when a trust check or reconciliation fails; not score 3 because the sequence is complete with most checkpoints present and no destructive batch operation lacking validation.

4 / 5

Progressive Disclosure

Good section structure with one real, one-level-deep bundle reference ('references/state-audit-template.md') that exists on disk and is clearly signaled at point of use. Not score 5 because the reference is not linked markdown-style and sizable inline material (trust-level taxonomy, companion-skill routing, primary truth sources) could live in reference files to slim the ~280-line body; not score 3 because structure is clear and the reference is not buried.

4 / 5

Total

16

/

20

Passed

Description

83%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: third-person voice, an explicit 'Use when' trigger clause, and several concrete actions over specific asset types. Trigger coverage is good though it misses common 'continue existing work' phrasings, and the review-materials mention carries slight overlap risk with a rebuttal skill.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('audit, trust-rank, and reconcile existing baselines, results, drafts, or review materials' plus 'choosing the next anchor') over named asset types, but coverage of the skill's full capability set (inventory classification, durable backfill, route decision) is incomplete. Not score 5 because the action list is not comprehensive; not score 3 because more than 1-2 distinct concrete actions are named.

4 / 5

Completeness

Both questions are explicitly answered: 'what' via 'audit, trust-rank, and reconcile existing baselines, results, drafts, or review materials' and 'when' via the concrete 'Use when a quest does not start from a blank state... before choosing the next anchor' trigger clause. Not score 4 because the 'when' is already explicit and tied to concrete trigger conditions, not merely implicit or generic.

5 / 5

Trigger Term Quality

Natural domain nouns users would actually say are present ('existing baselines, results, drafts, or review materials', 'does not start from a blank state'), giving good keyword coverage. Not score 5 because common natural variations like 'continue from where we left off', 'don't re-run', or 'pick up existing work' are missing; not score 3 because coverage goes beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

The 'does not start from a blank state... before choosing the next anchor' framing carves a clear intake-audit niche distinct from sibling research skills. Not score 5 because 'review materials' creates minor overlap risk with a rebuttal/revision skill; not score 3 because the non-blank-state trigger is specific and unlikely to fire for ordinary fresh starts.

4 / 5

Total

17

/

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

OpenLAIR/dr-claw

Path

skills/ds-intake-audit/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.