CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ce-skill-work

Applies this repository's skill-authoring standard as a procedure. Use for any change to, or judgment about, a file under skills/** — a SKILL.md, a reference, a persona prompt, a bundled script's instructions: creating a skill, editing one, reviewing a skill change, or acting on review feedback (human or bot) about one. Not for src/, tests/, or scripts/ code.

Quality

86%

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

78%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-engineered instruction-only skill body: it routes per-mode detail to real one-level-deep references, names exact validation commands and done conditions, and adds only non-derivable rules. Its main costs are sentence-level density — several rules fuse multiple clauses despite the skill's own plain-sentences standard — and a couple of spots (report example, validation failure loop) where concrete guidance could be fuller.

Suggestions

Split the longest multi-clause rules (the description rule and plain-sentences rule each fuse 3+ rules into one sentence) into one-idea-per-sentence form, matching the skill's own stated standard.

Add a short inline example of the completion report for one mode so the report spec is copy-paste concrete rather than purely descriptive.

State the validation failure loop explicitly (guards or eval fails → fix at the owning layer → re-run), making the workflow checkpoint a true feedback loop.

DimensionReasoningScore

Conciseness

The body assumes competence (no concept re-teaching) and nearly every rule states a falsifiable constraint or non-derivable fact, but several rules — notably the description rule and the plain-sentences rule — pack three or more clauses into single very long sentences that could be trimmed or split, matching 'efficient; minor instances that could be trimmed' rather than lean throughout.

4 / 5

Actionability

Concrete anchors are present: an exact validation command ('bun run test:skill-guards') with the named budget test ('tests/codex-skill-prompt-budget.test.ts'), per-mode reference paths, per-mode done conditions in the mode table, and a specified report shape. Minor gaps remain — e.g., the completion report is described but never exemplified — so it is mostly, not fully, executable guidance.

4 / 5

Workflow Clarity

The sequence is clear (pick mode → read the named guide sections → apply the rules → validate → report) with an explicit validation checkpoint and per-mode done bars in the table. It falls short of a 5 because the error-recovery loop when validation fails or an eval misfires is implied ('or an explicit skip reason in the report') rather than spelled out as a fix-and-revalidate step.

4 / 5

Progressive Disclosure

The body is a genuine overview: always-on rules stay inline, each mode routes to exactly one one-level-deep reference (references/new-skill.md, edit-skill.md, review-skill.md, respond-to-review.md), evaluation detail lives in references/evaluate.md, and the authority guide is externalized to docs/solutions/. All referenced bundle files verified present.

5 / 5

Total

17

/

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 names a distinctive mechanism, enumerates four concrete lifecycle actions as observable work-states, and closes with an explicit Not-for boundary that sharply limits mis-triggering. The only weakness is a mildly abstract opening clause and a few missing natural trigger variants.

DimensionReasoningScore

Specificity

The description enumerates several concrete actions — 'creating a skill, editing one, reviewing a skill change, or acting on review feedback' — covering the full skill-work lifecycle, but the opening clause 'Applies this repository's skill-authoring standard as a procedure' is somewhat abstract, placing it between the comprehensive (5) and several-specific-actions (4) anchors.

4 / 5

Completeness

Both what ('Applies this repository's skill-authoring standard as a procedure' plus the four concrete activities) and when ('Use for any change to, or judgment about, a file under skills/**' with enumerated triggers and an explicit 'Not for src/, tests/, or scripts/ code' exclusion) are clearly and explicitly stated with concrete trigger phrases.

5 / 5

Trigger Term Quality

It includes natural trigger phrases ('creating a skill', 'editing one', 'reviewing a skill change', 'acting on review feedback'), file terms (SKILL.md, skills/**), and synonyms ('a persona prompt, a bundled script's instructions'), but a few natural user variants (e.g., 'write a skill', 'update the reference') are absent, so it matches 'good keyword coverage; a few natural terms missing' rather than fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

The scope is tightly pinned to 'a file under skills/**' in this repository with an explicit negative boundary ('Not for src/, tests/, or scripts/ code'), giving it a clear niche with distinct triggers and minimal conflict risk with other 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

EveryInc/compound-engineering-plugin

Path

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