CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

goal-tracker

Record a session goal as a dated file with items plus evidence, keep its status current, then answer "what's left" in under 100 words: achieved, parked, still open. Use when the user states a session goal, asks what's left, what's outstanding, what's still open, whether the goal is met, are we done, where the session got to. Also use to park an item, to promote an overgrown goal into a plan, to close a goal out.

Quality

94%

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.

An exemplarily structured skill body: concrete commands that match the shipped script, a clearly sequenced workflow with an explicit validation gate and verification checklist, and one-level-deep references with per-file load triggers. The only notable improvement is mild redundancy between the Mindset principles and the Anti-Patterns' WHY clauses.

Suggestions

Trim or merge the Mindset section into Core Rules/Anti-Patterns: its unevidenced-status and asymmetric-trust principles are restated almost verbatim as Anti-Patterns' WHY clauses (e.g., 'NEVER close an outside-reach item on your own observation').

In the description, scope the generic completion phrases ("are we done", "close a goal out") to the session-goal context, e.g. "are we done with the session goal", to reduce overlap with plan/todo-tracking skills.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — no concept explanations, just rules, commands, and pointers — but the Mindset section ("An unevidenced status is worse than no status... Keep trust asymmetric") partially restates the rationale already carried by the Anti-Patterns' WHY clauses, so a small amount could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with argument shapes cover the common cases: "./scripts/goal.sh new \"Rotate the exposed token and unblock Phase 1\"", "./scripts/goal.sh park 3 \"Andy is on leave until Monday\"", "./scripts/goal.sh check --session <id>", plus a verbatim status output example and a concrete BAD/GOOD row comparison — all matching the actual goal.sh interface.

5 / 5

Workflow Clarity

The sequence is explicit (clarity test → draft → user confirmation → in-progress with same-turn evidence → park → status → promote → close) with an explicit validation gate ("Close out only when the check exits zero"), a five-item verification checklist, and a signaled recovery path (references/file-shape.md "load when diagnosing a failing check").

5 / 5

Progressive Disclosure

SKILL.md is a concise overview with five one-level-deep bundle references, each existing on disk and carrying an explicit load condition ("load when a new goal lacks a checkable end state", "load when closing any item", etc.), plus a schema asset and the goal.sh script — well-signaled, easy navigation.

5 / 5

Total

19

/

20

Passed

Description

96%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: it states concrete capabilities in third person, gives an explicit 'Use when' clause rich with natural trigger synonyms, and carves out a recognizable session-goal-tracking niche. The only weakness is a few generic completion phrases that slightly overlap with plan/todo-tracking skills.

DimensionReasoningScore

Specificity

The description enumerates the skill's full operation set concretely: "Record a session goal as a dated file with items plus evidence, keep its status current", "answer 'what's left' in under 100 words: achieved, parked, still open", plus "park an item", "promote an overgrown goal into a plan", and "close a goal out" — comprehensive, not just 1-2 actions.

5 / 5

Completeness

Both what ("Record a session goal as a dated file with items plus evidence... answer 'what's left' in under 100 words") and when ("Use when the user states a session goal, asks what's left...") are explicit, with concrete trigger phrases — the level-5 pattern.

5 / 5

Trigger Term Quality

Natural user phrasings are covered with abundant synonyms: "what's left", "what's outstanding", "what's still open", "whether the goal is met", "are we done", "where the session got to". This matches the comprehensive synonym coverage of the level-5 anchor rather than the 'a few natural terms missing' level-4 anchor.

5 / 5

Distinctiveness Conflict Risk

The session-goal niche is clear and most triggers are goal-specific, but generic completion phrases like "are we done" and "close a goal out" could also fire for closely related plan- or todo-tracking skills — minor overlap risk rather than minimal.

4 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

pantheon-org/tekhne

Path

skills/project-mgmt/goal-tracker/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.