CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-expert

Especialista Senior en Frontend (Next.js, React, Tailwind, FSD) para la construcción de interfaces. Úsalo cuando el usuario pida "nueva funcionalidad", "modifica el front", "crea un componente", "actualiza el diseño" o "refactoriza la UI".

68

Quality

85%

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

86%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-organized, actionable skill body with executable commands, worked examples, and excellent progressive disclosure pointing to real reference files. The only meaningful gap is the absence of an explicit validation step in the scaffolding workflow.

Suggestions

Add an explicit verification checkpoint after scaffolding, e.g. 'After the scaffold command finishes, confirm the expected files exist under frontend/src/<layer>/<name>/ before writing component code.'

Include a final validation step in the SOP such as running the project's linter/typecheck (or noting how to verify the new component compiles) before considering the task complete.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence (no explanations of what React/Tailwind are), stating project-specific conventions and an action-oriented SOP. Not 5 because the heavy CAPS/bold emphasis ('NUNCA', 'OBLIGATORIO', 'DEBES') and role framing add minor padding that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready commands ('python scripts/scaffold_feature.py lead-profile --layer entities --path frontend/src/entities'), exact file paths, and two fully worked examples covering common cases (new entity component, generic reusable button).

5 / 5

Workflow Clarity

Clear sequenced SOP (Análisis → Scaffolding → Componentes → Integración) with an explicit completion checkpoint ('Espera a que el comando termine') and a troubleshooting table giving feedback loops. Not 5 because there is no explicit validation/verify step (e.g. confirm scaffold output, run lint/typecheck) after the batch scaffolding operation.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references; the 'Referencias (Progressive Disclosure)' section labels each file by purpose and all referenced paths (component-rules.md, api-standards.md, fsd-cheatsheet.md, frontend-patterns.md, assets/templates/component.tsx) resolve to real bundle files.

5 / 5

Total

18

/

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, well-structured description that explicitly covers both what the skill does and when to use it, with natural Spanish trigger phrases and a distinct frontend niche. The main weakness is a slightly thin 'what' action statement and a few missing trigger synonyms.

DimensionReasoningScore

Specificity

Names the domain ('Frontend (Next.js, React, Tailwind, FSD)') and lists several concrete action triggers ('crea un componente', 'actualiza el diseño', 'refactoriza la UI'), though the core 'what' ('construcción de interfaces') is somewhat thin. Not 5 because coverage is not comprehensive (no testing, state, performance actions); not 3 because the trigger verbs supply multiple concrete actions beyond a single one.

4 / 5

Completeness

Explicitly answers both what ('Especialista Senior en Frontend... para la construcción de interfaces') and when ('Úsalo cuando el usuario pida...') with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Includes natural phrases a Spanish-speaking user would actually say ('nueva funcionalidad', 'modifica el front', 'crea un componente', 'actualiza el diseño', 'refactoriza la UI') plus the tech stack. Not 5 because synonym variations (e.g. 'front-end', 'pantalla', 'vista', 'página') are missing.

4 / 5

Distinctiveness Conflict Risk

Clear frontend niche with distinct triggers ('modifica el front', 'actualiza el diseño'); minor overlap risk because 'nueva funcionalidad' is broad and could match a general/fullstack coding skill. Not 5 due to that residual overlap.

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 7 missing, 7 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
alpacapurpura/ap_sales_agent
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.