CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

scroll-storytelling

Projeta narrativas interativas acionadas por rolagem. Trigger em: "scrollytelling", "scroll storytelling", "scroll animation site", "scroll-driven", "Apple-style landing page", "scroll experience", "rola como um filme", "video que roda com o scroll", "parece um template", "3D scroll world", "interactive landing page", "landing page cinematografica".

Quality

86%

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

81%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.

An unusually disciplined skill body: a sequenced 5-step pipeline with real validation loops, decision tables instead of prose, and dense detail correctly pushed to one-level-deep references. The two real defects are the missing engine/ runtime files — which the build step instructs the agent to copy and PROVENANCE claims were 'copiado byte a byte' — and light redundancy in the taste rhetoric.

Suggestions

Ship the missing `engine/scrollcraft.js` and `engine/scrollcraft.css` in the bundle (or inline a minimal fallback in SKILL.md), since Passo 4 and the Saidas Esperadas both depend on copying them and PROVENANCE.md claims they were copied byte a byte — an agent following the skill will currently fail at the build step.

Deduplicate the filmic one-shot rule (stated at the end of the grammars section and again in Regras Duras) and trim the editorial asides in 'O que isto NAO e' to reclaim tokens without losing the taste guidance.

Surface `references/verify.md` and `references/taste.md` from the body's own Checagem/Saidas sections (not only via PROVENANCE) so the verification procedure and taste floor are discoverable from the overview.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — no explanations of what scroll or libraries are, decision tables instead of prose, and detail explicitly deferred ('Conteudo denso... vive em `references/` — carregar sob demanda'), matching 'efficient; minor instances that could be trimmed'. Not 5: the filmic one-shot onus is stated twice (end of the grammars section and again as a Regras Duras row), and 'O que isto NAO e' carries some editorial rhetoric ('se reconhece de longe: mesmo diorama de argila...') that could be tightened without losing the taste guidance.

4 / 5

Actionability

Guidance is mostly executable for an instruction-only skill: the 8-grammar table, the 'Nunca | Em vez isso' hard-rules table, a measurable pre-build checklist (4+ device families, max two scrub acts, 8-14 viewport-heights), the `data-sc-*`/`--sc-p` contract with real HTML in references/devices.md, and a concrete token-theming CSS block in pipeline.md. Not 5: the central copy-paste artifact — 'engine/scrollcraft.js e engine/scrollcraft.css (do diretorio raiz desta skill)' — does not exist in the bundle, so the build step's key executable cannot actually be executed as written.

4 / 5

Workflow Clarity

The 5-passo pipeline is clearly sequenced (entrevista → brief/jornada → gramatica/gate/score → assets → construir/verificar) with a pre-build checklist and an explicit validation feedback loop at Passo 5 ('voltar ao Passo 2 pra reclassificar o beat — nao corrigir o HTML isolado'), plus an evidence-of-completion list — matching the anchor's 'clear sequence with explicit validation steps; feedback loops; checklists'. Not 4: validation checkpoints are explicit and the recovery path names where to go back to, not merely 'verify output'.

5 / 5

Progressive Disclosure

The ~200-line overview is well split across nine real, one-level-deep reference files, each signaled with what it holds and when to load it ('Detalhe completo... em `references/pipeline.md`', 'Ver references/worlds.md'), matching 'good structure; most content appropriately placed'. Not 5: scored against the actual bundle, the repeatedly referenced `engine/` directory is missing, `references/verify.md` and `references/taste.md` are surfaced only via PROVENANCE/pipeline.md rather than from the body's own verification sections, and GLOBAL.md/policies/ paths are unverifiable in this bundle.

4 / 5

Total

17

/

20

Passed

Description

86%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 compact description that answers what and when explicitly, with an unusually rich bilingual trigger list. Its main weakness is a thin 'what' — one action verb where two or three concrete capabilities would help — and a couple of over-broad triggers that could pull in generic landing-page requests.

Suggestions

Expand the 'what' clause with 2-3 concrete actions the skill performs, e.g. 'Projeta e constroi paginas scrollytelling (HTML + motor JS/CSS), do brief jornada ate a verificacao por screenshot' — this would lift specificity from naming one action to several.

Replace or qualify the 'parece um template' trigger with the phrasing a user would actually say (e.g. 'site que nao pareca um template') to reduce false triggers for generic template-based site requests.

Drop or narrow 'interactive landing page', which overlaps with general landing-page/UI-UX skills; the scroll-specific triggers already cover the niche.

DimensionReasoningScore

Specificity

The 'what' is a single clear action — 'Projeta narrativas interativas acionadas por rolagem' — which names the domain plus one concrete capability, matching the '1-2 concrete actions, not comprehensive' anchor. It does not reach 4 because the description never mentions the other concrete actions the skill performs (build the HTML page, scrub video, pin sections, verify via screenshots), and it is above 2 because the action is domain-specific rather than generic.

3 / 5

Completeness

Both questions are answered explicitly: what ('Projeta narrativas interativas acionadas por rolagem') and when ('Trigger em:' followed by concrete trigger phrases), mirroring the anchor-5 example structure. Not 4: the 'when' is fully explicit with literal trigger phrases rather than merely implied or generic, which is what the 4 anchor requires improving.

5 / 5

Trigger Term Quality

Twelve trigger phrases give comprehensive natural coverage with synonyms in both English and PT-BR ('scrollytelling', 'scroll storytelling', 'scroll-driven', 'Apple-style landing page', 'video que roda com o scroll', 'landing page cinematografica'), directly matching the 'comprehensive coverage of natural terms including synonyms' anchor. Not 4: no commonly used variant is obviously missing; the one ambiguous phrase ('parece um template') is a conflict-risk concern, not a coverage gap.

5 / 5

Distinctiveness Conflict Risk

The scrollytelling niche is clear and most triggers ('Apple-style landing page', '3D scroll world', 'video que roda com o scroll') would not fire for other skills, matching 'mostly distinct; minor overlap risk'. Not 5: 'interactive landing page' and 'parece um template' are broad enough to collide with a general UI/UX or landing-page design skill — a boundary the body has to police explicitly.

4 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/64-scroll-storytelling/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.