momentum-keeper

Maintain development momentum and prevent project stalls through progress tracking, blocker resolution, quick wins identification, energy management, and continuation strategies. Task-based operations for detecting stalls, breaking through obstacles, maintaining forward progress, and ensuring completion. Use when progress stalling, facing blockers, losing energy, needing motivation, or ensuring project continuation to completion.

Quality

64%

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 ./skills/momentum-keeper/SKILL.md

Quality

Content

45%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 with clear sequenced workflows and checklists, but it is heavily verbose with generic productivity coaching and, critically, it is a monolith that references three non-existent guide files rather than actually splitting detail into them.

Suggestions

Move the per-operation deep dives (long examples, energy-management strategies, completion-tracking detail) into the three referenced reference files and create those files so the 'For More Information' links resolve.

Cut generic advice Claude already knows (Pomodoro definitions, 'marathon not sprint', 'celebrate wins') to shrink SKILL.md toward a lean overview with concrete thresholds, formulas, and checklists.

Tighten abstract coaching phrases ('ride the momentum wave', 'feel the momentum') into concrete, verifiable actions so the actionable density reaches anchor-4.

Dimension	Reasoning	Score
Conciseness	At ~1040 lines, the body is noticeably verbose and padded with generic productivity wisdom Claude already knows (Pomodoro explanation, "marathon not sprint", "celebrate wins", "accept good enough") plus long narrative ASCII examples, though it retains enough useful specifics (thresholds, formulas) to stay above the fully-padded anchor-1.	2 / 5
Actionability	Provides some concrete guidance (numeric thresholds like ">24-48h" and ">4h", completion-rate formulas, checkbox validation checklists, decision heuristics), but a large share is abstract coaching ("ride the momentum wave", "feel the momentum") with no executable code or commands, leaving it between anchors 3 and 4.	3 / 5
Workflow Clarity	Each of the 6 operations has a clearly numbered Process, a Validation Checklist, Outputs, and a Time Estimate, with cross-operation routing and feedback loops ("If not, escalate or try different approach"), but validation is self-reported checkbox style rather than objective verification and a few operations (4, 5) have softer checkpoints, so it is just below anchor-5.	4 / 5
Progressive Disclosure	SKILL.md is a monolithic ~1040 lines with detailed operation deep-dives inlined that clearly belong in separate files, and its "For More Information" section points to references/stall-detection-guide.md, energy-management-guide.md, and completion-strategies-guide.md — none of which exist, so the references are signaled but broken.	2 / 5
	Total	11 / 20 Passed

Description

83%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 answers both what the skill does and when to use it, with concrete trigger phrases and a mostly distinct niche. Its main weakness is that the named actions are somewhat abstract and a few natural trigger synonyms are missing.

Dimension	Reasoning	Score
Specificity	Lists several specific actions ("progress tracking, blocker resolution, quick wins identification, energy management, and continuation strategies"; "detecting stalls, breaking through obstacles"), but they sit at an abstract process level rather than the concrete tangible verbs of the anchor-5 example, so it is above 3 but not fully comprehensive/concrete.	4 / 5
Completeness	Explicitly states what it does ("Maintain development momentum and prevent project stalls through...") and gives an explicit "Use when..." clause with concrete trigger phrases, matching the anchor-5 example that answers both what and when.	5 / 5
Trigger Term Quality	Includes natural trigger phrases a user would say ("progress stalling, facing blockers, losing energy, needing motivation") with good coverage, but misses common synonyms like "stuck", "burnout", or "procrastinating", so it is not the comprehensive anchor-5.	4 / 5
Distinctiveness Conflict Risk	The momentum/stall-prevention niche and triggers (stalls, blockers) are mostly distinct, but the motivational/energy angle ("needing motivation", "losing energy") is somewhat broad and could overlap with general productivity or coaching skills, keeping it just below the minimal-conflict anchor-5.	4 / 5
	Total	17 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1044 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	13 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/momentum-keeper/SKILL.md
Commit: 93ed392

Reviewed: 2 days 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.