CtrlK
BlogDocsLog inGet started
Tessl Logo

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

62

Quality

72%

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

75%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 concise for an instruction-only skill, with a clear sequenced workflow and feedback loop. The main gaps are a redundant dual representation of the workflow, an un-templated agent prompt, and no explicit validation of the final goal output.

Suggestions

Collapse the dot workflow graph and the numbered Implementation steps into a single representation to remove redundancy.

Provide a copy-pasteable agent prompt template (with slots for strategy/achievements/plans) so step 1 is fully executable.

Add an explicit validation/review checkpoint for the final goal document (e.g. check each goal has success indicators at levels 2, 3, and 4 and an org-strategy alignment) before writing the file.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no concept over-explanation; the only redundancy is that the dot workflow graph and the numbered Implementation steps describe the same flow twice.

4 / 5

Actionability

Concrete guidance is given (Agent tool via general-purpose, read ~/.claude/agents/goal-writer.md first, default output ~/Desktop/goals-{year}.md, templated Goal Structure), but the exact prompt to pass to the agent is not templated.

4 / 5

Workflow Clarity

A clear sequence is present with checkpoints ('Agent confirms understanding', user 'Iterate?' gate) and a feedback loop for iteration, but there is no explicit validation of final goal quality.

4 / 5

Progressive Disclosure

Well-organized sections in a single file with a one-level reference to the agent file by path; over 50 lines with content reasonably inline, but no progressive split of the goal template or examples into separate files.

4 / 5

Total

16

/

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.

The description clearly states what the skill does and gives three concrete, natural trigger scenarios, with a distinct niche and low conflict risk. It is slightly limited by a narrow single-action 'what' statement and could include a few more natural trigger synonyms.

Suggestions

Expand the 'what' to name the deliverable, e.g. 'Drafts structured individual performance goal documents with success indicators aligned to org strategy.'

Add a couple more natural trigger terms such as 'development goals' or 'career goals' to broaden trigger coverage.

Keep the explicit 'Use when...' clause but pair it with a short third-person capability statement so the 'what' leads the description.

DimensionReasoningScore

Specificity

Names the domain ('individual performance goals') with 1-2 concrete actions ('writing goals', 'create yearly goals', 'preparing for a goal-setting talk'), but the actions are narrow variations of one task rather than comprehensive coverage.

3 / 5

Completeness

Both 'what' (write individual performance goals) and 'when' (three explicit trigger scenarios) are present and clear, but the 'what' is a single action without naming the structured deliverable, keeping it just below the comprehensive anchor 5.

4 / 5

Trigger Term Quality

Strong natural phrases users would say ('performance goals', 'review cycle', 'yearly goals', 'goal-setting talk', 'manager') with synonyms, but a few natural variations like 'development goals' or 'career goals' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (individual performance goals in a review cycle) with distinct triggers; only minor overlap risk with adjacent development-planning or OKR-style skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fernandezbaptiste/claude-playground-explorer
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.