CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

85%

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

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 an exemplary orchestrator-style skill: lean and prescriptive, with an explicit phase order, hard validation gates (regression test fails-before/passes-after, suite result recorded), well-defined escalation and blocked states, and a clean split between the overview and `references/phases.md`. The residual gaps are minor — a few sentences that restate constraints, and a two-level reference chain instead of one level.

DimensionReasoningScore

Conciseness

The body is dense, rule-per-sentence prose that assumes competence — it never explains what a browser, git, or a dev server is — with concrete templates like `mktemp -d "${TMPDIR:-/tmp}/ce-dogfood-XXXXXX"`. A few passages could be trimmed (the host-specific invocation-rendering rules, and restatements like "The task list is session-scoped, but the report on disk is what a later run or a teammate resumes from"), so it sits at efficient-with-minor-trimmings rather than every-token-earns-its-place.

4 / 5

Actionability

Guidance is largely executable: exact paths (`.compound-engineering/config.yaml`, `<root>/dogfood-reports/<YYYY-MM-DD>-<branch-slug>-dogfood.md`), a copy-paste temp-dir command, an explicit status vocabulary (`Pass`, `Fixed`, `Skipped`, `Blocked (needs human verify)`), and named delegation targets (`ce-worktree`, `ce-debug`, `ce-commit`, `ce-compound`). It stops short of score 5 because the actual execution steps for the common cases are deferred to `references/phases.md` rather than covered in the body itself.

4 / 5

Workflow Clarity

The sequence is explicit and invariant ("Scope -> analyze the diff -> map the flows -> derive the matrix -> serve -> execute -> fix loop -> report. The order is the invariant"), with explicit validation ("A fix is not done until a regression test fails before it and passes after"), a checkpoint rule ("Create the report ... as soon as the matrix exists ... update it after each scenario"), the automated suite run recorded, and defined error-recovery paths (escalation to "Decisions for a human", terminal Blocked states). This matches the anchor with explicit validation steps and feedback loops.

5 / 5

Progressive Disclosure

The 60-line body is a genuine overview that clearly signals its references ("Read `references/phases.md` before Phase 0 ... the run cannot be executed correctly from the phase list below") and the report template, and every referenced path resolves to a real bundle file. It misses score 5 because the bundle is two levels deep — SKILL.md -> phases.md -> agent-browser-driver.md / test-matrix-taxonomy.md / packs-resolve.py — rather than the ideal one-level-deep structure.

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.

The description is a strong, dense statement of capability: it enumerates the full workflow concretely, stakes out a distinct niche, and explicitly declares manual-only invocation. Its only real weakness is the absence of concrete trigger phrases, which leaves completeness and trigger-term quality just below the top anchors.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the entire workflow: "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". This matches the comprehensive-coverage anchor rather than the score-4 anchor, which allows minor gaps.

5 / 5

Completeness

The "what" is explicit and comprehensive, and the "when" is explicitly stated via "Manual invocation only" — explicit invocation guidance rather than a weakly implied trigger. It does not reach score 5 because there are no concrete trigger phrases (e.g., "Use when the user asks to dogfood a branch"), and it stays above score 3 because the when-clause is not missing.

4 / 5

Trigger Term Quality

Natural terms a user would say are present — "browser QA", "dogfood", "user flows", "regression tests", "active branch" — giving good keyword coverage. It falls short of the score-5 anchor because common variations and synonyms (e.g., "test the branch", "e2e", "smoke test") are missing, but it exceeds score 3 since several genuinely natural phrases appear.

4 / 5

Distinctiveness Conflict Risk

"Hands-off, diff-scoped browser QA of the active branch" plus "dogfood report" and "product personas" carves a clear niche with distinct triggers, unlikely to fire for a generic testing or code-review skill. This matches the clear-niche/minimal-conflict anchor rather than the minor-overlap anchor at score 4.

5 / 5

Total

18

/

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

EveryInc/compound-engineering-plugin

Path

skills/ce-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.