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

76%

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 ./.agents/skills/dogfood/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 procedural core is excellent — a well-sequenced five-step workflow with validation gates and genuinely executable shell code — but it is buried in a trust-boundary section that is roughly twice as long as it needs to be, and the skill keeps ~200 lines of protocol inline that belong in bundle files that do not exist here. Tightening the pre-screen prose and moving the shell functions into a real scripts/ directory would lift both weak dimensions.

Suggestions

State each trust-boundary rule once: the checker-discovery logic and the two-line return shape are each explained two to three times (shell comments, prose, and code); keep the code plus one prose statement and cut the repeats.

Move the inline shell library (vocab_checker, span_ok, prescreen_ok, checked_prescreen, checked_outcome) into a scripts/ or references/ file in the bundle and reference it from the body, rather than inlining ~100 lines of shell in SKILL.md.

Resolve or clearly signal the external references (scripts/agents.lib.sh, scripts/vocab.config.sh, scripts/vocab.sh, constitution/local-product.md.template) — none are in this bundle, so a reader cannot tell which are kit-provided versus expected to be missing.

DimensionReasoningScore

Conciseness

Roughly half the body (the Trust boundary section, ~190 lines) is noticeably verbose: the checker-discovery rule is stated twice (as shell comments at lines 129-132 and again as prose at 207-215), the two-line return shape is described at least three times (106-111, 198-206, and via prescreen_ok), and "fails closed" is restated repeatedly. The information is accurate and novel, but the rubric penalizes verbosity even when accurate, and the same fences could be stated once each.

2 / 5

Actionability

Concrete, executable guidance throughout: complete shell functions (vocab_checker, span_ok, prescreen_ok, checked_prescreen, checked_outcome), a runnable scratch-directory lifecycle snippet (mktemp, redirect, checked_prescreen, rm -rf), and a specific report location (docs/dogfood-reports/). Minor gaps: the referenced helpers (scripts/agents.lib.sh, scripts/vocab.sh, scripts/vocab.config.sh) are not part of this bundle, and the reader-subagent spawn is left partially adapter-dependent.

4 / 5

Workflow Clarity

The five-step procedure is clearly sequenced with explicit validation checkpoints and feedback loops: refuse to run on trunk, stop if the surface will not come up, stop on a red suite, pre-screen output before reading it, checked_outcome gates every row's decision line before the report, and a refused outcome triggers a re-read and re-stamp. Error paths are named and handled throughout.

5 / 5

Progressive Disclosure

Section headers give the body reasonable structure, but no bundle files exist while the body references external ones (scripts/vocab.sh, scripts/agents.lib.sh, scripts/vocab.config.sh, constitution/local-product.md.template) that are neither present nor clearly signaled as separate materials. The ~190-line pre-screen protocol with inline shell libraries is content that clearly belongs in a separate scripts/ or references/ file, which anchors this at 'some structure but could be better organized'.

3 / 5

Total

14

/

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, concrete about what it does, and with an explicit and well-phrased 'Use when' clause covering natural trigger synonyms. The only weaknesses are minor — slightly incomplete action coverage and small overlap with generic testing vocabulary.

DimensionReasoningScore

Specificity

"Walk this project's own personas through its real user-facing surface" and "report the friction and breakage as candidate tickets" name several concrete actions, with four surface types enumerated (browser, binary, client, tool server). It falls short of 5 only because it omits other capabilities the body delivers (matrix building, evidence capture, high-risk flagging).

4 / 5

Completeness

It explicitly answers both questions: the what ("Walk this project's own personas through its real user-facing surface… and report the friction and breakage as candidate tickets") and the when ("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") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"dogfood a branch", "run an end-to-end pass", and "test the changed flows as a user" are natural phrases a user would say, giving good synonym coverage. A few plausible variants (e.g. "QA the branch", "smoke test", "try it before release") are missing, keeping it below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Dogfooding as a user before merge is a clear niche with distinct triggers ("dogfood", "end-to-end pass"). Minor overlap risk remains with general testing/QA skills via the phrase "test the changed flows as a user", so it is mostly distinct rather than minimal-conflict.

4 / 5

Total

17

/

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/vocab.config.sh, scripts/vocab.sh)

Warning

Total

13

/

16

Passed

Repository

agranado2k/agentic-sdlc

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.