CtrlK
BlogDocsLog inGet started
Tessl Logo

scroll-progress-timeline

Turn any ordered process into a data-driven vertical or horizontal scroll story with a base line, progress fill, active step states, responsive collapse, semantic fallback, and reduced-motion behavior. Use for onboarding, checkout, roadmaps, recipes, case studies, service processes, histories, or narratives where progress through the sequence should become visible while scrolling.

68

Quality

83%

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

67%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-structured, lean, and actionable with real code and a verification checklist, but its progressive-disclosure promise is broken: every referenced bundle file is missing. Shipping the referenced demo/ and REFERENCES.md files would resolve the main weakness.

Suggestions

Add the referenced demo/index.html, demo/PROMPT.md, and REFERENCES.md files (and the demo/ directory) so the one-level-deep references resolve.

Move the bulk layout-selection guidance and the IntersectionObserver/GSAP detail into REFERENCES.md, keeping SKILL.md as a tighter overview that links out.

Add an explicit build/validate feedback loop (e.g., 'run the Verify checklist; if the active step and line head disagree at a boundary, re-measure lineStart/lineEnd and retry') to lift workflow clarity.

DimensionReasoningScore

Conciseness

Mostly lean and imperative ('Render a quiet base line behind every point') with executable code and no padding about basic CSS/DOM concepts; a few explanatory sentences could still be trimmed.

4 / 5

Actionability

Provides concrete executable JS for the steps array and the progress/scaleY calculation with specific transform-origin values, but some layout guidance remains high-level prose ('Use a centered alternating timeline only when...').

4 / 5

Workflow Clarity

Clear sequenced sections (model → build → layout → animate → navigate → reduce motion → verify) with an explicit 'Verify' testing checklist, though error-recovery feedback loops are implicit rather than spelled out.

4 / 5

Progressive Disclosure

References are clearly signaled one level deep ([demo/index.html], [demo/PROMPT.md], [REFERENCES.md]), but none of these files or the demo/, references/, scripts/, assets/ directories exist in the bundle, so navigation dead-ends in practice.

2 / 5

Total

14

/

20

Passed

Description

100%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 exemplary: third-person, concrete, and explicit about both capabilities and triggering contexts. It avoids fluff while comprehensively enumerating use cases. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'base line, progress fill, active step states, responsive collapse, semantic fallback, and reduced-motion behavior' — giving comprehensive coverage of what the skill produces.

5 / 5

Completeness

Explicitly answers both what ('Turn any ordered process into a data-driven ... scroll story ...') and when ('Use for onboarding, checkout, roadmaps ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural use-case terms a user would say are comprehensively listed: 'onboarding, checkout, roadmaps, recipes, case studies, service processes, histories, or narratives', alongside 'scroll story' and 'progress'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — scroll-linked progress timelines — with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
MengTo/Skills
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.