CtrlK
BlogDocsLog inGet started
Tessl Logo

senior-frontend

Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.

77

Quality

96%

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

92%

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 concise, highly actionable frontend reference with executable code and clear option tables, but it is monolithic — all reference material lives inline in a single file with no bundle files to offload the larger reference sections. Splitting the pattern catalogs and tables into signaled reference files would lift progressive disclosure.

Suggestions

Extract the bundle-analysis table and React/Next.js pattern catalogs into a references/ file (e.g., PATTERNS.md) and link to it from a concise overview section, so SKILL.md stays a lean entry point.

Move the accessibility checklist and Tailwind/TypeScript quick-reference into a separate CHEATSHEET.md referenced one level deep, keeping only the most essential snippets inline.

Add a short navigation block at the top pointing to any split-out reference files once created, so discovery is explicit rather than implied by section headings.

DimensionReasoningScore

Conciseness

The body is lean — tight code snippets, option tables, and minimal one-line section intros — with no padding that explains concepts Claude already knows (e.g., no 'what a hook is' prose). Not a 2, because nearly every line is directly actionable reference material that earns its place rather than carrying unnecessary explanation.

3 / 3

Actionability

Provides executable, copy-paste-ready code (useDebounce hook, next/image with sizes, cn utility, generic List component) and concrete option tables for scaffolding and component generation. Not a 2, because examples are complete and runnable rather than pseudocode with missing details.

3 / 3

Workflow Clarity

Scaffolding and component generation are single, unambiguous actions defined by clear option tables, which the rubric permits to score 3 for simple skills; no destructive/batch operations are present that would demand validation checkpoints. Not a 2, because the available actions are unambiguous and there is nothing fragile requiring a missing feedback loop.

3 / 3

Progressive Disclosure

The skill is a single ~190-line self-contained SKILL.md with no references/scripts/assets bundle files, and large reference blocks (React patterns, bundle-analysis tables, accessibility checklist) are all inline rather than split into clearly signaled one-level-deep files. Not a 3, because it exceeds the 'under 50 lines' simple-skill allowance and keeps content that could be separated inline; not a 1, because sections are well-organized with no nested/deep references.

2 / 3

Total

11

/

12

Passed

Description

100%

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 is strong: it states a clear frontend niche, lists six concrete actions in third person, and provides an explicit 'Use when' trigger clause. It is both specific and trigger-rich, minimizing conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality' — matching the anchor for listing several specific concrete actions. Not a 2, because the actions are comprehensive and varied rather than a domain plus a few actions; third-person voice is used throughout.

3 / 3

Completeness

Explicitly answers both 'what' (frontend development skill for React/Next.js/TypeScript/Tailwind) and 'when' via a 'Use when building... or reviewing...' trigger clause. Not a 2, because the when is explicit rather than implied; the 'Use when' clause satisfies the completeness cap rule.

3 / 3

Trigger Term Quality

Natural user-facing terms like 'React components', 'Next.js performance', 'bundle sizes', 'scaffolding frontend projects', and 'accessibility' match the phrasings a user would actually say. Not a 2, because it covers common variations rather than only a few relevant keywords; no generic jargon present.

3 / 3

Distinctiveness Conflict Risk

The React/Next.js/TypeScript/Tailwind frontend niche plus distinct task triggers make it unlikely to fire for unrelated skills. Not a 2, because the triggers are specific and clearly bounded rather than overlapping with similar general skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
composio-community/awesome-claude-plugins
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.