scroll-craft
An agent skill for building premium, immersive, scroll-driven websites. Works with Codex, Claude Code, and other coding agents. Also available as a Claude Code plugin.
Runssource: GitHubhomepageJavaScriptMITcommit 75d81f74e836
JavaScript, MIT licensed. The project labels itself: accessibility, agent skills, ai web design, anthropic, claude code, claude code plugin, creative coding and design system.
scroll-craft runs. An Argusic agent installed it in 11 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The scrollcraft engine loads and drives scroll-driven interaction cues across all 4 acts with no JavaScript errors; the encode.sh script produces valid scrubbing-optimized MP4 clips via ffmpeg
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- [email protected] requires Node >=20 but container has Node 18.19.1, causing EBADENGINE warnings1 minute
- Chrome not found on PATH or standard locations by doctor.mjs1 minute
- Install time
- 11 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- Node '/tmp/verify_scrollcraft.mjs' (Chrome via Playwright, headless, 1440x900@2x): engine ready (html.sc-ready), 4 acts detected [scrub,pin,flow,pin], page scrollable 6833px, cues transition correctly through scroll positions, 0 JS errors (only 404s for stubbed media assets)
- Model tokens used
- 266,484
- Exact commit tested
- 75d81f74e836
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
140
exec
/bin/sh -lc 'ls /work/repo/package.json 2>/dev/null && cat /work/repo/package.json | head -20' in /…
succeeded in 0ms:
/work/repo/package.json
{
"dependencies": {
"playwright-core": "^1.51.0"
}
}
tokens used
266,484Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 11 minutes, faster than the median of the 5 comparable projects Argusic has measured.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 6 accessibility projects Argusic has installed and timed, scroll-craft was the 3rd fastest to reach a running state, and 5 of 6 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
accessibilityagent-skillsai-web-designanthropicclaude-codeclaude-code-plugincreative-codingdesign-systemfrontendinteraction-designlanding-pagescroll-animationscrollytellingtypographyweb-design
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/scroll-craft)Questions
- Does scroll-craft run?
- Yes. scroll-craft runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test scroll-craft?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 75d81f74e836. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test scroll-craft?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does scroll-craft take to install?
- 11 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does scroll-craft need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing scroll-craft?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does scroll-craft compare with the alternatives?
- Of the 6 accessibility projects Argusic has installed and timed, scroll-craft was the 3rd fastest to reach a running state, and 5 of 6 reached one at all.
- Where is the evidence for scroll-craft?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.