CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

build

Fully automate a coding task with make-plan, do, and babysit.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./plugin/skills/build/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 admirably lean and appropriately contained in a single short file, and the three-step sequence is unambiguous in ordering. However, it delegates everything to three named skills without stating how they are invoked, how the task argument flows between them, or how the autonomous run is verified or stopped, leaving actionability and workflow clarity mid-scale.

Suggestions

Show concretely how to invoke each step (e.g. the exact subagent prompt or Skill invocation for `make-plan`, `do`, and `babysit`) so the workflow is executable as written rather than delegated by name only.

Specify how $ARGUMENTS is passed into `make-plan` and what each step consumes from the previous one, so the chain is followable without guessing.

Add a validation or stop condition for the autonomous run (e.g. what `babysit` checks before completion, or what to do on failure), since fully automated coding sessions carry risk of unbounded or destructive changes.

DimensionReasoningScore

Conciseness

The body is six lines with no padding and no explanation of concepts Claude already knows; "Deploy a subagent to fully automate a coding session as if it were typing in it itself" is the only framing sentence and it earns its place.

5 / 5

Actionability

Concrete elements exist (exact skill names in order, the `$ARGUMENTS` task input), but there are no specifics on how to invoke each skill, how to deploy the subagent, or how the task flows between steps — key execution details are missing.

3 / 5

Workflow Clarity

A clear 1-2-3 sequence is present (make-plan, do, babysit), but each step is just a skill name with no description of what happens, no validation checkpoints, and no indication of how `$ARGUMENTS` propagates through the chain.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references; the single file is well-organized (heading, one-sentence purpose, ordered list, task placeholder), which scores 5 under the simple-skill guideline.

5 / 5

Total

16

/

20

Passed

Description

50%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 states a clear "what" and names its component skills, but omits any "when to use" guidance and lacks natural trigger terms. It sits at the middle of the scale: concrete enough to not be fluff, but generic enough to risk overlapping with other automation skills.

Suggestions

Add a "Use when..." clause naming the situations that call for this skill, e.g. "Use when the user asks to build, fully automate, or hands-off a coding task end-to-end."

Include the natural trigger word "build" (the skill's own name) and synonyms like "autonomous" or "delegate" so the description matches what users actually type.

Briefly state what the three sub-skills accomplish (plan the task, execute it, monitor it) so the "what" is comprehensive rather than a bare skill list.

DimensionReasoningScore

Specificity

"Fully automate a coding task" names the domain and one concrete action, plus three named sub-skills (make-plan, do, babysit), but coverage of what the skill actually does is not comprehensive.

3 / 5

Completeness

It answers "what" clearly (fully automate a coding task via three named skills) but contains no "Use when..." clause or any trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

"Automate" and "coding task" are somewhat natural user phrases, but common variations a user would actually say ("build", "delegate", "run autonomously", "hands-off") are missing.

3 / 5

Distinctiveness Conflict Risk

"Fully automate a coding task" is broad and could overlap with other agent/delegation skills; the named sub-skills add some distinctiveness within the claude-mem ecosystem.

3 / 5

Total

12

/

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

thedotmack/claude-mem

Path

plugin/skills/build/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.