SkillAgentSearch skills...

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.

Install / Use

npx skills add MengTo/Skills --skill scroll-progress-timeline

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Supported Platforms

Universal

Tags

Our assessment of scroll-progress-timeline

scroll-progress-timeline scores 90/100 on our quality scale, 26th of 60 Product Management skills we index (top 44%).

Its SKILL.md is 3.9 KB long, well organised into 8 sections with 2 code examples: a solid amount of guidance for an agent.

With 6,252 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so scroll-progress-timeline is actively maintained.
  • Our last check on 2026-10-30 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

scroll-progress-timeline compared with similar skills

All 4 of these similar skills score higher than scroll-progress-timeline; compare them before choosing.

SkillScoreStarsUpdatedFormat
scroll-progress-timeline (this skill)by MengTo906.3k54d agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install scroll-progress-timeline?
Run npx skills add MengTo/Skills --skill scroll-progress-timeline. The install tabs above show the steps for each supported agent.
Which AI agents does scroll-progress-timeline work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is scroll-progress-timeline safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is scroll-progress-timeline still maintained?
The repository was last updated about 2 months ago, so scroll-progress-timeline is actively maintained.

name: scroll-progress-timeline description: 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.

Scroll Progress Timeline

Use one progress line to connect ordered information. The sequence must remain complete, readable, and navigable before animation is added.

Model the steps

Keep the content data-driven:

const steps = [
  { id: "brief", number: "01", title: "Set the direction", body: "..." },
  { id: "build", number: "02", title: "Make the system", body: "..." },
  { id: "ship", number: "03", title: "Release and learn", body: "..." }
];

Render it as an ordered list with real headings. The line, dots, media, and active state enhance that structure; they do not replace it.

Build the line

  1. Render a quiet base line behind every point.
  2. Place one progress line on top with transform-origin: top for vertical or left for horizontal.
  3. Measure the first and last point centers, not arbitrary section edges.
  4. Normalize scroll position between those centers.
  5. Apply scaleY(progress) or scaleX(progress) so updates stay on the compositor.
  6. Mark a step active when the progress head crosses its center.
const progress = Math.min(1, Math.max(0,
  (viewportAnchor - lineStart) / (lineEnd - lineStart)
));
line.style.transform = `scaleY(${progress})`;

Schedule DOM writes in one animation frame. Recalculate geometry after font and image loading, resize, orientation changes, and content mutation.

Choose the layout

  • Use a centered alternating timeline only when both sides have enough width and similar content weight.
  • Use a left rail for long copy, compact steps, or mixed card heights.
  • Use a horizontal line for short sequences with concise labels and explicit keyboard-safe overflow.
  • Use pinned full-screen chapters only when each step carries a distinct visual state. Keep the pin finite and release before the next section.
  • Collapse to a simple left rail on small screens. Do not preserve alternation at the expense of reading order.

Animate step state

Use small opacity, translate, scale, blur, color, or media transitions. Keep every step readable while inactive. Expose active index with aria-current="step" only when that state is meaningful and current; do not announce every scroll update with a live region.

Use IntersectionObserver for simple active-state entry. Use a normalized scroll measurement or GSAP ScrollTrigger when the line must fill continuously or coordinate pinned media.

Handle navigation

  • Make step links real anchors when users can jump within the process.
  • Add scroll-margin for sticky headers.
  • Preserve focus and do not move it during passive scrolling.
  • Keep URLs and browser history stable unless the user explicitly selects a step.
  • If steps are interactive, use buttons or links with visible focus; never make a decorative dot the only control.

Reduce motion

Under prefers-reduced-motion: reduce, show the complete line or discrete reached states without scrubbed interpolation, blur, pinning, or large transforms. Keep ordinary document flow and all step content.

Verify

Test variable step counts, uneven card heights, missing media, long translations, 390/768/1024/1440 widths, 200% zoom, fast forward and reverse scrolling, direct anchor navigation, keyboard order, reduced motion, late font/image layout, route cleanup, and console errors. The active step and line head must agree at every boundary.

Use demo/index.html as the working reference and demo/PROMPT.md to recreate or remix it. Keep REFERENCES.md as the links-only implementation source list.

Related Skills

View on GitHub
GitHub Stars6.3k
CategoryProduct
Updated1mo ago
Forks741

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions