CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frontend-engineer

Pro frontend engineering discipline. Enforces build-test-verify workflow for every web project. Never declare done until the site is built, tested, responsive, accessible, and visually verified in a real browser. Pairs with a deployment skill such as vercel-cli, where one is installed.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./container/skills/frontend-engineer/SKILL.md
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.

The body is a strong, disciplined workflow document: a clearly sequenced six-step process with hard validation gates, concrete executable commands, checklists, and an explicit error-recovery iteration loop. Its only weaknesses are minor over-explanation of basics Claude already knows and a few placeholder stubs in the deploy commands.

DimensionReasoningScore

Conciseness

Largely lean, prescriptive bullets where every line directs behavior, but it restates concepts a senior frontend engineer already knows (semantic tag lists, 'Every <img> gets an alt attribute', one <h1> per page, WCAG 4.5:1 contrast), fitting 'efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

Provides mostly executable, copy-paste-ready commands ('pnpm run build 2>&1', the agent-browser open/screenshot/eval sequence, 'const Heavy = dynamic(() => import(...))') plus concrete checklists; minor gaps (the 'vercel deploy --token placeholder' and '<deployed-url>' stubs) keep it below the fully-executable anchor at 5.

4 / 5

Workflow Clarity

Six explicitly numbered steps in a coherent sequence with mandatory validation gates (build must pass before deploy, console-error check, checklist of always/when-relevant verifications), a production verification step, and an explicit iteration feedback loop with a bounded escape hatch after 3 failed iterations — matching the 'clear sequence with explicit validation steps, feedback loops, and checklists' anchor.

5 / 5

Progressive Disclosure

A single-file skill with no bundle files present and a well-organized section hierarchy (workflow steps, anti-patterns, reporting) that is easy to navigate; at ~150 lines, the React/Next.js and CSS rule catalogs are borderline candidates for a references file, matching 'good structure; minor organization gaps' rather than the fully split overview at 5.

4 / 5

Total

17

/

20

Passed

Description

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

The description communicates a clear what — a build-test-verify discipline with mandatory visual verification — with several concrete actions and a deployment pairing. Its main weaknesses are the absence of any explicit 'use when' trigger clause, incomplete natural-keyword coverage, and a buzzword-leading opener that dilutes specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building or modifying websites, web apps, or UI components, or when the user asks for frontend work, visual polish, or deployment.'

Replace the buzzword opener 'Pro frontend engineering discipline' with concrete capability phrasing and include natural trigger terms users actually say (website, web app, React/Next.js, landing page, UI).

Sharpen distinctiveness by stating what this skill governs versus sibling skills (e.g., it owns the build/verify/deploy workflow, not design-system or backend concerns) to reduce overlap with other web skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Enforces build-test-verify workflow for every web project", "built, tested, responsive, accessible, and visually verified in a real browser", "Pairs with a deployment skill" — but opens with buzzwordy "Pro frontend engineering discipline" and stops short of comprehensive capability coverage, so it fits the 'several specific actions; minor gaps' anchor rather than the 5.

4 / 5

Completeness

The 'what' is clear (enforces a build-test-verify discipline with visual verification), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the pairing note about vercel-cli describes integration, not when to invoke the skill — which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Contains relevant keywords ("web project", "browser", "responsive", "accessible", "vercel") but misses common natural variations users would say ("website", "web app", "React", "landing page", "component"), matching the 'some relevant keywords but missing common variations' anchor rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

Scoped to frontend web engineering, but "for every web project" is broad enough to overlap with general web-dev, component-library, and design skills; it is 'somewhat specific but could still overlap with similar skills' rather than 'mostly distinct' (4).

3 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

nanocoai/nanoclaw

Path

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