ce-dogfood

Hands-off, diff-scoped browser QA of the active branch: maps user flows, drives a real browser, autonomously fixes small breakages with regression tests and commits, judges experience against product personas, and writes a durable dogfood report. Manual invocation only.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ce-dogfood/SKILL.md

Quality

Content

85%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 orchestrator skill body: dense and actionable with a clearly sequenced, validation-gated workflow and clean progressive disclosure into one-level-deep reference files.

Dimension	Reasoning	Score
Conciseness	Lean and information-dense with no padding of concepts Claude already knows; every line carries operational guidance, though a few long compound sentences (e.g., the Outcome paragraph) could be tightened.	4 / 5
Actionability	Provides concrete executable guidance — 'command -v agent-browser', 'mktemp -d "${TMPDIR:-/tmp}/ce-dogfood-XXXXXX"', 'gh pr view <number> --json ...', specific report paths — but delegates the per-phase execution detail to references/phases.md.	4 / 5
Workflow Clarity	Explicit ordered sequence ('Scope -> analyze the diff -> map the flows -> derive the matrix -> serve -> execute -> fix loop -> report') with a stated invariant, validation gates ('a regression test fails before it and passes after'), a fix feedback loop, and a terminal-state/resumability checklist.	5 / 5
Progressive Disclosure	The body is an overview that clearly signals one-level-deep references to real bundle files — 'Read references/phases.md before Phase 0', 'Create the report from references/dogfood-report-template.md' — with content appropriately split across phases.md, the report template, and test-matrix-taxonomy.md.	5 / 5
	Total	18 / 20 Passed

Description

75%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 specific, well-scoped description that concretely enumerates the skill's actions and occupies a distinct niche, but it lacks an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger phrases (e.g., dogfooding a branch, end-to-end browser QA of a PR/branch, validating user flows before merge).

Include common synonym trigger terms users might say (e.g., 'smoke test', 'manual QA pass', 'end-to-end test') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'maps user flows, drives a real browser, autonomously fixes small breakages with regression tests and commits, judges experience against product personas, and writes a durable dogfood report' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	The 'what' is clearly and concretely stated, but there is no 'Use when...' trigger clause; 'Manual invocation only' is a constraint rather than explicit when-to-use guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('browser QA', 'dogfood', 'user flows', 'regression tests', 'personas') but missing common synonyms and an explicit trigger phrasing, so not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — 'diff-scoped browser QA of the active branch' producing a 'dogfood report' — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: EveryInc/compound-engineering-plugin
Path: skills/ce-dogfood/SKILL.md
Commit: 26bf5b1

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.