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

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

73%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-crafted process skill: the workflow is clearly sequenced with explicit stop conditions and evidence requirements, and the guidance is concrete about artifacts and gates. The main drag is conciseness — the essayistic opening and provenance footer spend tokens on motivation rather than instruction.

Suggestions

Cut the motivational opening paragraphs ("Every other check in this chain reads the product... fail the only test that counts") down to one or two lines stating the skill's purpose; the reader is Claude, which does not need persuading.

Drop or compress the provenance footnote at the end — licensing/lineage detail does not help execute the skill and belongs in the referenced LICENSE file itself.

Trim the italicized aside ("This is the same split the rest of the kit uses...") and similar kit-commentary asides; they add context about the framework rather than instructions for the run.

DimensionReasoningScore

Conciseness

The bulk of the body is dense, non-padded instruction that assumes Claude's competence, but the motivational opening ("Every other check in this chain reads the product. This one uses it... That gap is where the embarrassing defects live") and the closing provenance footnote are unnecessary for execution and could be trimmed. Mostly efficient with some clearly cuttable material.

3 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: a matrix of (persona, journey, assertion) triples written before launch, a specific report location ("docs/dogfood-reports/, named for the branch and the date"), enumerated ticket fields, and named prerequisites. The actual driving mechanics are delegated to the project's product article, which is a deliberate design choice but leaves minor gaps.

4 / 5

Workflow Clarity

A clear five-step numbered sequence with explicit validation gates throughout: refuse to run on trunk, stop if the suite is red, "wait for it to be genuinely ready rather than merely started", and "If the surface will not come up, that is the finding, and the run stops here". The pre-written matrix acts as a checklist and every failed row requires evidence. The skill performs no destructive or batch operations (it explicitly fixes nothing), so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

A single, well-organized file with clear section headers and a logical flow, and no bundle files exist to reference. All content legitimately belongs inline for a process skill of this size, but at ~145 lines with no overview-to-detail split and only pointed-at project files (constitution/local-product.md, /to-tickets), it falls short of the fully-signaled reference structure of the top anchor.

4 / 5

Total

16

/

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 states what the skill does in concrete terms, enumerates the surfaces it drives, and gives an explicit, multi-trigger "Use when" clause. Trigger coverage is good though a few common synonyms are absent, and the action list is compact rather than exhaustive.

DimensionReasoningScore

Specificity

Concrete actions are named — "Walk this project's own personas through its real user-facing surface" and "report the friction and breakage as candidate tickets" — with the surface types enumerated (browser, binary, client). It sits between the 4 and 5 anchors: specific and near-comprehensive, but built on only two core verbs rather than a list of several distinct actions.

4 / 5

Completeness

Both halves are explicit: the "what" ("Walk this project's own personas through its real user-facing surface... report the friction and breakage as candidate tickets") and a concrete "Use when" clause with multiple trigger phrases (branch functionally complete, about to say "ship it", dogfood a branch, end-to-end pass, test changed flows).

5 / 5

Trigger Term Quality

Natural phrases a user would actually say are present — "dogfood a branch", "run an end-to-end pass", "test the changed flows as a user", "ship it" — but common synonyms like "smoke test", "QA pass", or "acceptance pass" are missing, which keeps it at good-but-not-comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — pre-merge dogfooding of the real user-facing surface — with distinctive triggers ("dogfood", "end-to-end pass") that are unlikely to collide with code-review, run, or test-execution skills.

5 / 5

Total

18

/

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-haskell

Path

.agents/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.