CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frontend-dev

Full-stack frontend development combining premium UI design, cinematic animations, AI-generated media assets, persuasive copywriting, and visual art. Builds complete, visually striking web pages with real media, advanced motion, and compelling copy. Use when: building landing pages, marketing sites, product pages, dashboards, generating media assets (image/video/audio/music), writing conversion copy, creating generative art, or implementing cinematic scroll animations.

Quality

84%

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.

A well-engineered, highly actionable skill body with a gated six-phase workflow, concrete configs and commands, and properly signaled one-level-deep references. The main defects are two bundle directories referenced but missing (templates/, canvas-fonts/), no inline example of script invocation, and some duplicated structure listings.

Suggestions

Add the missing `templates/viewer.html` and `templates/generator_template.js` (and `canvas-fonts/`) to the bundle, or remove those references — the Interactive art mode currently instructs Claude to read a file that does not exist.

Include one copy-paste-ready example invocation of an asset script (e.g. `python scripts/minimax_image.py --prompt "..." --ratio 16:9`) in section 3.1 so the core generation loop is executable without opening the CLI reference first.

Trim duplication: the per-framework directory trees largely repeat the asset/component-location table, and the references list appears in both the Skill Structure tree and section 3.4 — consolidate to one listing.

DimensionReasoningScore

Conciseness

The body is dense and directive — design dials, forbidden patterns, exact spring configs, install commands — and assumes Claude's competence (never explains what React/Tailwind/GSAP are). Minor redundancy could be trimmed: the asset-location table repeats information in the five per-framework directory trees, and the references list appears both in the Skill Structure tree and again in section 3.4. This fits anchor 4 (efficient, minor instances that could be trimmed) rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Highly concrete throughout: exact classes ("min-h-[100dvh]", "max-w-[1400px] mx-auto"), exact spring/easing values, install commands, asset naming patterns, preset specs, and a grep checklist for placeholder URLs. The gap keeping it from anchor 5: Phase 3's core action — "Execute via scripts" — never shows a single example invocation of the minimax scripts, deferring entirely to references/minimax-cli-reference.md.

4 / 5

Workflow Clarity

Six phases are clearly sequenced with explicit gates: user confirmation before asset generation ("MUST confirm before generating"), a hard gate ("do NOT proceed to Phase 5 until all assets are saved locally"), and a Quality Gates checklist including a validate-and-fix loop ("grep the output... If ANY found, STOP and replace with generated assets before delivering"). This matches anchor 5's explicit validation steps, feedback loops, and checklists for a complex process.

5 / 5

Progressive Disclosure

Good structure overall: the Skill Structure tree maps one-level-deep to real files (all 10 references/ and 4 scripts/ files exist) with per-file descriptions and "read as needed" signaling. The gap against the actual bundle: the body instructs "Read `templates/viewer.html` first" and "Sparse typography from `canvas-fonts/`", but neither `templates/` (viewer.html, generator_template.js) nor `canvas-fonts/` exists in the bundle — broken paths that would dead-end the Interactive art mode. This fits anchor 4 (good structure, minor organization gaps) rather than anchor 5's clean navigation.

4 / 5

Total

17

/

20

Passed

Description

83%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 strong description: it states a clear multi-capability "what" in third person and pairs it with an explicit, concrete "Use when" trigger list. Weaknesses are limited to mild buzzword padding and a few missing natural synonyms.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Builds complete... web pages", "generating media assets (image/video/audio/music)", "writing conversion copy", "creating generative art", "implementing cinematic scroll animations" — with minor gaps in coverage. Buzzword padding ("premium UI design", "visually striking", "cinematic") keeps it below the 5 anchor, which demands comprehensive concrete actions without fluff; it is well above anchor 3's 1-2 actions.

4 / 5

Completeness

Clearly answers both questions: the "what" ("Full-stack frontend development combining premium UI design, cinematic animations, AI-generated media assets, persuasive copywriting, and visual art") and an explicit "Use when:" clause with six concrete trigger phrases. This matches anchor 5 exactly; anchor 4's "'when' could be more explicit" does not apply since the when-clause is explicit and specific.

5 / 5

Trigger Term Quality

The "Use when" clause surfaces natural phrases users would actually say: "building landing pages, marketing sites, product pages, dashboards... writing conversion copy, creating generative art, or implementing cinematic scroll animations." Common variations are missing (e.g. "website", "web page", "hero section", file extensions), so it matches anchor 4 (good coverage, a few natural terms missing) rather than anchor 5's synonym-and-extension comprehensiveness.

4 / 5

Distinctiveness Conflict Risk

The combination (frontend page building + AI media generation + copy + art) forms a clear niche with distinct triggers. Minor overlap risk remains: standalone triggers like "dashboards" and "creating generative art" could fire for requests better served by dedicated dataviz or art skills, fitting anchor 4 (mostly distinct, minor overlap) rather than anchor 5's minimal conflict risk.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (571 lines); consider splitting into references/ and linking

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

MiniMax-AI/skills

Path

skills/frontend-dev/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.