CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

80%

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.

The content is well-structured, actionable, and appropriately concise for a simple drafting skill, with a clear template and a verification checklist. It could be strengthened by adding one fully worked example and trimming the redundancy between the template, questions, and component bullets.

Suggestions

Add one complete worked `/goal` example line to push actionability toward anchor 5.

Consolidate the Shape template, the four questions, and the component bullets to remove restated slots and improve conciseness.

Make the Check list an explicit ordered pass/fail gate (e.g., "if any item fails, revise before returning") to strengthen the validation checkpoint.

DimensionReasoningScore

Conciseness

The body is lean with no over-explanation of concepts Claude already knows, but the Shape template, the four questions, and the component bullets restate the same slots, a minor redundancy that keeps it at anchor 4 rather than 5.

4 / 5

Actionability

Provides a copy-paste template, concrete slot definitions, and specific rule examples ("`bun test packages/auth` exits 0"), but lacks a single fully worked example goal line, fitting anchor 4 rather than 5.

4 / 5

Workflow Clarity

The sequence (answer questions in order, compress to one line, run the Check list) is clear with an explicit validation checklist and an error-recovery loop (Rule 6), but the drafting workflow is not a risky multi-step operation, so it sits at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

No bundle files are needed for this single-purpose skill, and the body is organized into clear, well-signaled sections (Shape, Rules, Check), meeting the simple-skill exception for anchor 5.

5 / 5

Total

17

/

20

Passed

Description

82%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 strong: it states a concrete purpose, gives explicit trigger guidance, and carves out a distinct niche. Its only weakness is moderate specificity, since it names a single drafting action rather than enumerating several capabilities.

Suggestions

Broaden the action list slightly (e.g., "Draft, refine, and validate a `/goal` line") to lift specificity toward anchor 5.

Add one or two synonym trigger terms (e.g., "stop condition" or "done condition") to round out trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("Draft a `/goal` line") with three specific deliverables (objective, validation evidence, stop condition), but does not list several distinct actions, matching the anchor for 3 rather than 4.

3 / 5

Completeness

Explicitly answers both what (draft a goal line with objective, validation evidence, stop condition) and when ("Use when the user explicitly asks for `/goal`, an agent goal, or a completion condition") with concrete trigger phrases, matching anchor 5.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ("`/goal`", "agent goal", "completion condition") with good coverage, but misses common synonyms like "stop condition" or "done condition", fitting anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (the slash-goal artifact) with distinct triggers and minimal overlap risk with other skills, matching anchor 5.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
EpicenterHQ/epicenter
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.