CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dogfood

Walk this project's own personas through its real user-facing surface before a human does — a browser for a web app, the binary for a CLI, a client for an API or a tool server — and report the friction and breakage as candidate tickets. Use when a branch is functionally complete and somebody is about to say "ship it", or when the user asks to dogfood a branch, run an end-to-end pass, or test the changed flows as a user.

Quality

85%

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

The canonical home for this skill is dogfood in agranado2k/google-books-clojure

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 is a well-structured, trustworthy procedure: a clearly sequenced five-step workflow with explicit validation gates and stop conditions, concrete deliverables, and strong safety boundaries. It is efficient and actionable, falling just short of top marks only on token trim and the absence of a worked example or template.

Suggestions

Trim the opening narrative framing and the provenance footer; both are non-operational and would save tokens without losing guidance (conciseness).

Add one worked example of a matrix row and a short candidate-ticket template so steps 2 and 5 are copy-paste actionable rather than assembled from field lists (actionability).

DimensionReasoningScore

Conciseness

The body assumes Claude's competence — it explains no general concepts — and nearly every section carries operational content. Minor instances of trimmable material (the opening rhetorical framing and the provenance footer) keep it below "every token earns its place".

4 / 5

Actionability

Guidance is concrete for an instruction-only skill: "One row per (persona, journey, assertion) triple", a report location ("docs/dogfood-reports/"), enumerated ticket fields, and a concrete good/bad example of step wording ("upload a file, then share it with a colleague" — not "POST /files then PATCH /acl"). Minor gaps: no sample matrix row or report/ticket template to copy.

4 / 5

Workflow Clarity

A clear five-step sequence with explicit validation gates and stop conditions: "Refuse to run on trunk itself", "If the surface will not come up, that is the finding, and the run stops here", "wait for it to be genuinely ready rather than merely started", the red-suite stop, and a matrix "written before anything is launched". Startup-output capture provides an error-recovery path for later failures.

5 / 5

Progressive Disclosure

A single-file skill (no references/, scripts/, or assets/ exist) with well-organized sections — prerequisites, trust boundary, five-step procedure, boundaries, when to run — and nothing that clearly belongs in a separate file. At ~143 lines it is appropriately placed overall, with only minor organization headroom.

4 / 5

Total

17

/

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: it names concrete actions, enumerates the surfaces it drives, and gives an explicit, multi-trigger "Use when" clause. Its only weaknesses are slightly narrow action coverage and a few missing natural synonyms, plus minor overlap risk with general testing/driving skills.

DimensionReasoningScore

Specificity

Concrete actions are named — "Walk this project's own personas through its real user-facing surface", "report the friction and breakage as candidate tickets" — with a specific enumeration of surfaces ("a browser for a web app, the binary for a CLI, a client for an API or a tool server"). Minor gaps keep it below the comprehensive multi-action coverage of a 5.

4 / 5

Completeness

Explicitly answers both questions: the "what" is walking personas through the real surface and reporting friction/breakage as candidate tickets, and the "when" is a concrete "Use when" clause with multiple trigger phrases ("a branch is functionally complete", "dogfood a branch", "end-to-end pass", "test the changed flows as a user").

5 / 5

Trigger Term Quality

Includes natural phrases a user would actually say: "dogfood a branch", "run an end-to-end pass", "test the changed flows as a user". A few natural synonyms (e.g. "smoke test", "manual QA", "try the app") are missing, so it falls just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The pre-merge dogfooding niche and "dogfood" trigger are distinctive, but phrases like "test the changed flows as a user" carry minor overlap risk with app-driving or end-to-end testing skills in a similar kit.

4 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

agranado2k/tic-tac-toe-with-agentic-sdlc

Path

.claude/skills/dogfood/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.