CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

goal-writer

Use when writing individual performance goals for a review cycle, when the user needs to create yearly goals, or when preparing for a goal-setting talk with their manager

Quality

75%

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 ./goal-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured and actionable, with a concrete goal template, clear when/when-not guidance, and an explicit iterate-then-write workflow. Its main costs are the redundant dot-graph workflow duplicating the Implementation steps and the hard dependency on an external, non-bundled agent file with no fallback.

Suggestions

Remove the dot digraph (or the numbered Implementation list) — they duplicate each other and cost ~14 lines of context.

Bundle or inline the key instructions from ~/.claude/agents/goal-writer.md, or add a fallback (e.g., a sample agent-launch prompt) for when that file is absent.

Tighten the Overview, which restates the frontmatter description without adding new information.

DimensionReasoningScore

Conciseness

The body is generally lean with no over-explanation of known concepts, but the 14-line dot digraph ('User requests goals' -> 'Launch goal-writer agent' -> ... -> 'Write final file') fully duplicates the numbered Implementation steps and iterate loop, and the Overview restates the description — a substantial section that could be cut.

3 / 5

Actionability

Concrete, executable guidance: 'Use the Agent tool (general-purpose) with a prompt that instructs it to follow ~/.claude/agents/goal-writer.md', a default output path ('~/Desktop/goals-{year}.md'), and a copy-ready goal markdown template. Minor gaps: no sample agent-launch prompt text and total dependence on an unbundled external agent file.

4 / 5

Workflow Clarity

The Implementation section gives a clear 5-step sequence with an explicit user-approval/iterate checkpoint ('If changes needed, relaunch agent with feedback'; the graph's 'approved' -> 'Write final file'). It falls short of 5 because there is no explicit validation of the agent file's existence or of output quality before writing the final file.

4 / 5

Progressive Disclosure

Sections are well-organized (When to Use / When NOT to Use / Implementation / Goal Structure / Critical Rules) and the single reference to the agent file is clearly signaled and one level deep. It does not reach 5 because the body is ~76 lines with an external dependency (~/.claude/agents/goal-writer.md) that is not bundled with the skill, so navigation depends on a file outside the skill.

4 / 5

Total

15

/

20

Passed

Description

70%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 solid description with an explicit, well-phrased trigger clause and natural user terminology. Its main weakness is a thin 'what' — it says when to use the skill but not what the skill concretely does (draft structured goals with success indicators aligned to org strategy).

Suggestions

Add a 'what' clause enumerating concrete capabilities, e.g. 'Drafts structured individual performance goals with success indicators aligned to organizational strategy.'

Include additional natural trigger variations such as 'performance review' or 'annual goals' that users would commonly say.

Consider noting the OKR exclusion in the description to reduce conflict with OKR-writing skills.

DimensionReasoningScore

Specificity

Names the domain ('individual performance goals for a review cycle') and 1-2 concrete actions ('writing individual performance goals', 'create yearly goals'), but never states what the skill produces — no mention of drafting structured goals, success indicators, or strategy alignment — so it is not comprehensive.

3 / 5

Completeness

Both 'what' ('writing individual performance goals', 'create yearly goals') and an explicit 'when' ('Use when... for a review cycle... preparing for a goal-setting talk') are present, but the 'what' is thin and could be more concrete about the skill's outputs. It is above anchor 3 because 'when' is explicit and detailed, not merely implied.

4 / 5

Trigger Term Quality

Natural user phrases like 'review cycle', 'yearly goals', and 'goal-setting talk with their manager' are present, but common variations such as 'performance review', 'annual goals', or 'goal setting' are missing, keeping it short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche (individual performance goals for review cycles) is mostly distinct with natural triggers, but there is minor overlap risk with closely related skills like OKR creation or strategy-writing, and the explicit OKR exclusion lives only in the body, not the description.

4 / 5

Total

15

/

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

fernandezbaptiste/claude-playground-explorer

Path

goal-writer/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.