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

75%

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

Quality

Content

62%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 excels at workflow clarity — each of the six operations is a numbered process with an explicit validation checklist and error-recovery loops — and offers genuinely actionable thresholds and templates. However, it is severely padded through four-fold repetition of the same content across Operations, Best Practices, Common Mistakes, and Quick Reference sections, and it points to reference files that are absent from the bundle while inlining the very content those files should hold.

Suggestions

Cut the redundancy: the Best Practices, Common Mistakes, and Quick Reference sections largely restate the six Operations — collapse them into one summary table and move detailed mistake narratives into a reference file.

Create the three referenced guides (references/stall-detection-guide.md, energy-management-guide.md, completion-strategies-guide.md) or remove the 'For More Information' pointers, since the files do not exist in the bundle.

Trim the long narrative examples and motivational filler ('Celebrate', 'Psychological boost felt' checklist items) to roughly halve the body length while keeping the thresholds, templates, and checklists that carry the value.

DimensionReasoningScore

Conciseness

The ~1040-line body repeats the same material four times (Operations, Best Practices, Common Mistakes, and Quick Reference tables) and pads with motivational filler ('Celebrate... Feel the momentum', 'Psychological boost felt' checkboxes) and long narrative vignettes. Not 1 because genuine actionable signal and structure remain beneath the padding.

2 / 5

Actionability

Concrete thresholds (24-48h stall detection, 4-hour blocker rule, 15-60 min quick wins), ready-to-use templates (session-end breadcrumbs, Definition of Done), and decision aids make the guidance mostly executable. Not 5 because some steps remain abstract ('Assess subjective state', 'Feel the win') and referenced companion files are missing.

4 / 5

Workflow Clarity

Every operation has a numbered process, an explicit validation checklist, and feedback loops ('If not, escalate or try different approach') plus cross-operation routing from stall detection to the right intervention. This matches the top anchor: clear sequences, explicit validation steps, and checklists for complex processes.

5 / 5

Progressive Disclosure

Good sectioning and a clearly signaled 'For More Information' block, but the three referenced files (references/stall-detection-guide.md, energy-management-guide.md, completion-strategies-guide.md) do not exist, and the 1040-line body inlines long examples and mistake write-ups that belong in those separate files. Structure exists but organization is undermined by broken references and heavy inlining.

3 / 5

Total

14

/

20

Passed

Description

80%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 is well-constructed: it states multiple concrete capabilities and includes an explicit, trigger-rich 'Use when...' clause that clearly answers both what and when. Its weaknesses are missing common trigger synonyms and broad motivational phrasing that risks overlap with adjacent productivity/task-management skills.

Suggestions

Add natural trigger synonyms users would actually say, e.g. 'stuck', 'blocked', 'burnout', 'procrastinating', or 'losing interest', to strengthen trigger_term_quality.

Sharpen distinctiveness by scoping the 'when' clause to momentum-specific situations (e.g. 'no meaningful progress in 24-48 hours', 'resuming after an interruption') rather than generic phrases like 'needing motivation'.

Make capabilities slightly more concrete (e.g. 'run stall-detection checks with time thresholds, maintain a quick-wins reserve, leave session-resume breadcrumbs') to reach artifact-level specificity.

DimensionReasoningScore

Specificity

Lists several specific actions ('progress tracking, blocker resolution, quick wins identification, energy management, and continuation strategies', 'detecting stalls, breaking through obstacles... ensuring completion') with minor gaps in coverage. Not 5 because the actions are capability-level rather than concrete artifact-level operations like 'fill forms, merge documents'.

4 / 5

Completeness

Explicitly answers 'what' across three sentences (momentum maintenance via tracking, blocker resolution, quick wins, energy management, continuation strategies) and 'when' with a concrete 'Use when...' clause listing trigger conditions. Matches the top anchor of both what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Use when progress stalling, facing blockers, losing energy, needing motivation' provides good natural keyword coverage, but common variations users would say ('stuck', 'blocked', 'burnout', 'procrastinating') are missing. Clears anchor 4 but not comprehensive enough for 5.

4 / 5

Distinctiveness Conflict Risk

The momentum/stall-management niche is somewhat specific, but broad triggers like 'needing motivation' and 'facing blockers' overlap with general task-management, planning, and todo skills (the body itself references todo-management, task-development, planning-architect). Could still overlap with similar skills, fitting anchor 3 rather than 4.

3 / 5

Total

16

/

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

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.