CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cs-frontend-review

Frontend engineering review — walks the 7 Matt Pocock forcing questions (device, LCP target, rendering, bundle budget, SEO vs auth, design system, WCAG), picks the framework + rendering profile, forks into specialists (a11y-audit, performance-profiler, epic-design). Invokes the cs-frontend-engineer agent with context fork.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/cs-frontend-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 lean, well-structured command body with a concrete executable decision-engine invocation, explicit kill-criteria checkpoints, specific output expectations, and useful anti-patterns. The main gaps are missing error-recovery/merge guidance in the workflow, specialist forks lacking an invocation mechanism, and core references that live outside the skill bundle and cannot be verified to exist.

Suggestions

Ship the referenced files inside the skill bundle (e.g. references/forcing_questions.md, scripts/frontend_decision_engine.py, profiles/*.json) or use bundle-relative paths so the core protocol is self-contained and verifiable.

Add error-recovery guidance to the routing protocol: what to do when the decision engine script fails or specialist findings conflict with the matched profile, and when/how the depth-first specialist fork terminates and merges results.

Make the specialist fork step concrete by specifying the invocation mechanism (e.g. the Agent/subagent call or command) and define the runner-up tradeoff threshold precisely (e.g. 'within 15% match-score of the top profile').

DimensionReasoningScore

Conciseness

The body is ~60 lines of dense lists, commands, and bullets with zero padding: it never explains what LCP, WCAG, or design systems are, and every section (forcing questions, routing protocol, output expectations, anti-patterns, customization) carries purely operational content. This matches the 5 anchor (lean, assumes Claude's competence, every token earns its place); there is no over-explanation to trim that would justify 4.

5 / 5

Actionability

Concrete, executable guidance dominates: a full bash invocation with enumerated flag choices ("--primary-device <mobile-4g|desktop-fiber|low-end-android|corporate-network>", "--lcp-target-ms <N>"), named fork conditions ("epic-design only for astro-or-static marketing surfaces"), and measurable outputs ("p75 on the primary device", "KB-gzip"). Not 5 because of minor gaps: the referenced script and canonical reference file do not exist in the skill's bundle, the specialist-fork step gives no concrete invocation mechanism, and "runner-up tradeoff (if within 15%)" does not define 15% of what; not 3 because the command block is directly executable with fully specified parameters.

4 / 5

Workflow Clarity

The routing protocol is a clearly numbered 5-step sequence with an explicit validation checkpoint ("Surface kill criteria — e.g., 'SEO-dependent + SPA-only' trips. STOP and resolve.") and a concrete final checklist ("Output expectations (≤ 200-word digest)"), matching the 4 anchor. Not 5 because there is no error-recovery feedback loop (e.g., what to do when the decision engine fails or specialist findings conflict) and the depth-first fork loop has no completion or merge criteria; not 3 because checkpoints are explicit and the sequence is unambiguous.

4 / 5

Progressive Disclosure

The body is well-organized into clear sections, keeps an appropriately brief inline 7-question summary while deferring detail to a clearly labeled canonical reference ("Canonical source: engineering-team/skills/senior-frontend/references/forcing_questions.md"), and signals every external resource with a full path and purpose. Not 5 because the referenced paths (forcing_questions.md, frontend_decision_engine.py, profiles/) point outside the skill bundle and do not resolve — no references/, scripts/, or assets/ directories ship with the skill — so the core protocol depends on unverifiable external files; not 3 because signaling is clear and nothing that should be separate is inlined.

4 / 5

Total

17

/

20

Passed

Description

71%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 highly specific, dense description that clearly communicates what the skill does with named protocols, specialists, and question domains. Its main weakness is the complete absence of any "when to use" trigger guidance, which caps completeness, and a few missing natural synonyms (accessibility, SSR/SPA, framework names) that would improve trigger matching.

Suggestions

Add an explicit 'Use when...' clause with concrete triggers, e.g. 'Use when reviewing a frontend architecture, choosing a rendering strategy (SSR/SPA/SSG), or setting performance/a11y targets for a web surface.'

Include natural synonyms users would actually say — 'accessibility', 'web performance', 'SSR/SPA', 'React/Next' — alongside the current jargon-heavy terms (LCP, WCAG, a11y) so the description matches how users phrase the need.

Name the distinguishing trigger vs. the parent command (e.g. 'frontend-only surface; use /cs-fullstack-review when backend is in scope') to reduce overlap risk with closely related review skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions, each with named sub-entities: "walks the 7 Matt Pocock forcing questions (device, LCP target, rendering, bundle budget, SEO vs auth, design system, WCAG)", "picks the framework + rendering profile", and "forks into specialists (a11y-audit, performance-profiler, epic-design)". This matches the 5 anchor (multiple specific concrete actions, comprehensive coverage) rather than 4, since the actions enumerate their own sub-topics rather than leaving coverage gaps.

5 / 5

Completeness

The "what" is clearly and specifically stated, but there is no "Use when..." clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Good natural keyword coverage — "Frontend engineering review", "LCP target", "rendering", "bundle budget", "SEO", "design system", "WCAG" — terms a frontend engineer would naturally say. Not 5 because common synonyms and variations are missing ("accessibility" as a plain word, "SSR/SPA", "web performance", framework names like React/Next); not 3 because coverage goes well beyond "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

The niche is clear ("Frontend engineering review" with a named forcing-question protocol and named specialists), but a generic "review" trigger and the closely related parent command (cs-fullstack-review, referenced in the body) create minor overlap risk, matching the 4 anchor. Not 5 because that overlap exists; not 3 because the rendering-profile/a11y/perf focus is far more distinct than broadly overlapping skills.

4 / 5

Total

16

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/cs-frontend-review/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.