Is pretext-frontend-motion safe to install?

SaferSkills independently audited pretext-frontend-motion (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

SKILL.md · 1 file

SKILL.md2.0 KB · Markdown

name: pretext-frontend-motion

description: Build bold text-driven frontend demos across Accordion, Bubbles, Dynamic Layout, Variable Typographic ASCII, Editorial Engine, Justification Comparison, Rich Text, and Masonry. Use when the request needs strong frontend style, intentional typography, routed text layout, width-tight multiline UI, or kinetic typography driven by real Pretext measurement instead of DOM text reads.

Pretext Frontend Motion

Overview

Use this skill when the request clearly maps to an official Pretext demo family.

Do not treat Pretext as a decorative dependency. Keep it in the actual layout path.

Typical trigger patterns:

measure text height without DOM reflow
auto-fit text to a fixed number of lines
tight multilingual bubbles
routed text around an obstacle
algorithmic typography or glyph-field motion
line-breaking or justification comparison

Required Workflow

Pick the official demo family.
Pick the matching style profile before writing code.
Use the matching bundled example or blueprint.
Stay in the correct API lane:

prepare + layout for Accordion, Bubbles, Masonry
prepareWithSegments + layoutNextLine for Dynamic Layout and Editorial Engine
prepareWithSegments + layoutWithLines for Variable Typographic ASCII
walkLineRanges for width probing and layout comparison flows

Keep the design intentional.
Validate resize, mobile, and hot-path measurement rules.

Bundled Resources

core/bundle/references/official-notes.md
core/bundle/references/demo-family-map.md
core/bundle/references/prompt-recipes.md
core/bundle/references/integration-gotchas.md
core/bundle/examples/
core/bundle/integrations/
core/bundle/blueprints/

Validation Checklist

Official demo family is explicit.
Pretext is used for real measurement and layout.
No DOM text measurement in the relayout hot path.
prepare() is not rerun on every resize.
The result still looks intentional on mobile widths.

pretext-frontend-motion— agent skill

Is pretext-frontend-motion safe to install?

Pretext Frontend Motion

Overview

Required Workflow

Bundled Resources

Validation Checklist

Audit the pieces. Scan the whole. Decide.