CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agent-goal

Draft a `/goal` line that gives long-running Codex or Claude Code work an objective, validation evidence, and a stop condition. Use when the user explicitly asks for `/goal`, an agent goal, or a completion condition.

Quality

92%

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

92%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 tight, well-structured instruction skill: a copy-paste template, ordered questions, crisp rules, and a closing verification checklist, all with zero padding. The single improvement opportunity is including one fully worked /goal example to make the output format unambiguous.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a one-line template, four compressed questions, a bulleted inclusion list, seven terse rules ("after three failed attempts on the same check, report the root cause and next decision"), and a short checklist — every token earns its place with no padding or explanation of known concepts. Not 4 because there is no section that could be trimmed without losing actionable guidance; even the Platform Note states a portable rule ("the goal should not rely on hidden state") rather than background explanation.

5 / 5

Actionability

Concrete, executable guidance throughout: a copy-paste template line ("/goal <single objective> in <lane> until <observable evidence proves completion>"), four questions to answer in order, and a concrete evidence example ("`bun test packages/account` exits 0" beats "tests pass"), matching 'mostly executable guidance; concrete code or commands with minor gaps'. Not 5 because there is no fully worked example of a completed /goal line, which is the one gap preventing copy-paste-ready coverage of the common case; not 3 because the guidance is concrete and complete in structure, not pseudocode.

4 / 5

Workflow Clarity

The process is clearly sequenced — fill the template by answering the four questions "in order, then compress them into one line" — and ends with an explicit verification checklist ("Before handing back a goal, verify: It has one main objective... It tells the agent when to stop"), plus a failure-bounding loop ("after three failed attempts on the same check, report the root cause"). This matches the top anchor: clear sequence with explicit validation steps and a checklist. Not 4 because the Check section leaves no validation implicit.

5 / 5

Progressive Disclosure

This is a simple, single-purpose skill (~57 body lines) with no external files (references/, scripts/, assets/ are absent) and no content that belongs in a separate file; the well-organized sections (Shape, Rules, Platform Note, Check) provide easy navigation, so the simple-skill exception applies. Not 4 because there are no organization gaps and nothing is inlined that should be split out; the skill needs no references, so their absence is not a defect.

5 / 5

Total

19

/

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: third-person, concise, with an explicit and concrete 'Use when' trigger clause and a well-defined niche. The only soft spot is trigger coverage, which misses a few natural synonyms (stop condition, success criteria) users might say when they need this skill.

DimensionReasoningScore

Specificity

"Draft a `/goal` line that gives long-running Codex or Claude Code work an objective, validation evidence, and a stop condition" names one concrete action plus three specific output components, matching the 'several specific actions; minor gaps in coverage' anchor. Not 5 because there is effectively a single action (drafting the goal line) rather than multiple distinct concrete actions; not 3 because the components enumerated (objective, validation evidence, stop condition) go beyond 1-2 generic actions.

4 / 5

Completeness

It explicitly answers both: what ("Draft a `/goal` line that gives ... an objective, validation evidence, and a stop condition") and when ("Use when the user explicitly asks for `/goal`, an agent goal, or a completion condition") with concrete trigger phrases, matching the top anchor exactly. Not 4 because the when-clause is already explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

The trigger clause "Use when the user explicitly asks for `/goal`, an agent goal, or a completion condition" covers the natural phrases well, matching the 'good keyword coverage; a few natural terms missing' anchor. Not 5 because common variations users might say — "stop condition", "success criteria", "define when the agent is done" — are absent from the when-clause; not 3 because the terms present are natural user phrasings, not jargon.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — the slash-goal artifact for long-running coding-agent work — and the body-reinforced boundary ("This skill owns the slash-goal artifact") plus distinct triggers (/goal, agent goal, completion condition) give minimal conflict risk. Not 4 because it does not overlap with generic prompt-drafting or delegation skills; the trigger terms are specific to this artifact.

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

EpicenterHQ/epicenter

Path

.agents/skills/agent-goal/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.