CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

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

The canonical home for this skill is momentum-keeper in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

52%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-sequenced and surprisingly actionable for a soft-skills skill, with concrete thresholds, checklists, and templates. However, it is severely padded with productivity common sense Claude already knows, and its structure is a wall of text whose only external references are broken, so progressive disclosure fails outright.

Suggestions

Cut the body to a concise overview of the six operations (purpose, when-to-use, key thresholds) and move the detailed processes, examples, and reference tables into the actual reference guides the 'For More Information' section promises — references/stall-detection-guide.md, energy-management-guide.md, and completion-strategies-guide.md do not exist.

Remove or drastically compress the narrative example case studies (e.g., the 'Quick Win Session: Low Energy Day' story) and the general productivity wisdom Claude already knows (Pomodoro cycles, break frequency, celebrating wins); keep only the skill-specific thresholds, routing rules, and templates.

Replace subjective, unverifiable checklist items ("Psychological boost felt", "Energy level assessed honestly") with objective checkpoints, and add explicit recovery loops to the operations that currently end without one (e.g., Operations 3 and 4).

DimensionReasoningScore

Conciseness

The ~1040-line body extensively explains concepts Claude already knows (Pomodoro timing, "3-4 hours quality work/day > 10 hours mediocre work", celebrating wins, taking breaks) and pads operations with narrative example case studies like "Quick Win Session: Low Energy Day". It is above a 1 only because it also contains genuinely operational content such as concrete thresholds and checklists.

2 / 5

Actionability

For an instruction-only skill, the guidance is mostly concrete and executable: specific thresholds ("No completed tasks in 24-48 hours", "Task blocked >4 hours"), per-blocker-type resolution strategies, a session-end-notes template, and completion-rate formulas. Minor gaps include references to sibling skills (skill-researcher, todo-management) that are not verifiable.

4 / 5

Workflow Clarity

Each of the six operations has a numbered process and a validation checklist, and Operation 2 includes an explicit validate-or-escalate feedback loop ("If not, escalate or try different approach"). It falls short of 5 because several checkpoints are not objectively verifiable ("Psychological boost felt", "Energy level assessed honestly") and some operations lack an error-recovery loop.

4 / 5

Progressive Disclosure

The SKILL.md is a monolithic ~1040-line document whose per-operation detail clearly belongs in separate reference files, and the "For More Information" section points to references/stall-detection-guide.md, references/energy-management-guide.md, and references/completion-strategies-guide.md — none of which exist in the bundle, so navigation leads nowhere.

2 / 5

Total

12

/

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.

A strong description that clearly states capabilities and explicit trigger conditions in third-person voice. Its only weaknesses are mild redundancy between the second and third sentences and a few missing natural trigger synonyms.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities ("progress tracking, blocker resolution, quick wins identification, energy management, and continuation strategies"), matching the anchor for several specific actions with minor gaps. It is not a 5 because the second and third sentences partially restate the same actions with generic phrasing ("breaking through obstacles", "maintaining forward progress") rather than adding coverage.

4 / 5

Completeness

It explicitly answers both what ("Maintain development momentum and prevent project stalls through progress tracking, blocker resolution...") and when ("Use when progress stalling, facing blockers, losing energy, needing motivation...") with concrete trigger phrases, matching the top anchor. A 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

"Use when progress stalling, facing blockers, losing energy, needing motivation" provides good natural-phrase coverage a user would actually say. Not a 5 because common synonyms like "stuck", "burnout", "unmotivated", or "procrastinating" are missing.

4 / 5

Distinctiveness Conflict Risk

The momentum/stall-prevention niche ("prevent project stalls", "quick wins", "energy management") is mostly distinct with specific triggers. It is not a 5 because the domain overlaps with generic task- and todo-management skills, and no file types or artifacts further demarcate it.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

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

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