goal-tracking

Track progress toward 3-year, yearly, monthly, and weekly goals. Calculate completion percentages, surface stalled goals, connect daily tasks to objectives. Use for goal reviews and progress tracking.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./vault-template/.claude/skills/goal-tracking/SKILL.md

Quality

Content

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable content with concrete formulas, paths, and tool calls, organized into clear sections. Its weaknesses are missing verification checkpoints on goal-editing workflows and a monolithic inline structure (large templates) that could be split into reference files.

Suggestions

Add a verification step to 'Update Goal Status' (e.g. re-read the goal file to confirm the checkbox/percentage changed as intended) to satisfy the validation-checkpoint expectation for batch/destructive edits.

Move the full Progress Report Format template and the complete TaskCreate block list into reference files (e.g. references/report-template.md, references/report-tasks.md) and link to them from SKILL.md to improve progressive disclosure and conciseness.

Tighten the report-format example to a minimal skeleton with field descriptions rather than a fully populated sample table.

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational reference with no concept-padding, but the full progress-report template and complete TaskCreate blocks are heavier inline than necessary and could be tightened or externalized.	2 / 3
Actionability	Provides concrete formulas, real file paths (e.g. 'Goals/0. Three Year Goals.md'), explicit TaskCreate calls with subjects/activeForms, and copy-paste report tables — fully executable guidance.	3 / 3
Workflow Clarity	Operations are clearly numbered and task dependencies are explicit via addBlockedBy, but file-editing workflows (Update Goal Status) lack validation/verification checkpoints, capping clarity at 2 per the batch/destructive guideline.	2 / 3
Progressive Disclosure	No bundle files exist and sections are well-organized, but at ~200 lines with large inline report/task templates that could live in separate reference files, it leans monolithic rather than overview-with-references.	2 / 3
	Total	9 / 12 Passed

Description

84%

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 specific, well-triggered description that cleanly covers both what and when with a clear niche. Trigger-term coverage is the only soft spot — it names the use case once rather than enumerating the natural phrasings a user might say.

Suggestions

Broaden trigger terms to match user phrasings, e.g. 'Use for goal reviews, progress tracking, weekly reviews, or when asking if you're on track to meet a goal.'

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Calculate completion percentages', 'surface stalled goals', 'connect daily tasks to objectives' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (track/calculate/surface/connect actions) and when via the 'Use for goal reviews and progress tracking' trigger clause.	3 / 3
Trigger Term Quality	'goal reviews and progress tracking' gives some natural keywords, but coverage is thin and missing common variations users would say (e.g. 'am I on track', 'check my goals', 'weekly review').	2 / 3
Distinctiveness Conflict Risk	The cascading 3-year→weekly goal niche with 'surface stalled goals' is a distinct, specific trigger set unlikely to collide with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: ballred/obsidian-claude-pkm
Path: vault-template/.claude/skills/goal-tracking/SKILL.md
Commit: ef1e4da

Reviewed: about 2 hours ago

Table of Contents

Discovery Implementation Validation

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.