CtrlK
BlogDocsLog inGet started
Tessl Logo

team-frontend

Unified team skill for frontend development. Pure router — all roles read this file. Beat model is coordinator-only in monitor.md. Built-in ui-ux-pro-max design intelligence. Triggers on "team frontend".

42

Quality

42%

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 ./.codex/skills/team-frontend/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured orchestration skill with strong actionability and clear workflow definitions. The delegation lock, spawn templates, and GC loop provide concrete, executable guidance for the coordinator role. The main weakness is moderate verbosity — some sections could be tightened or externalized to reduce the token footprint, and without bundle files it's hard to fully validate the progressive disclosure structure.

Suggestions

Consider moving the 'v4 Agent Coordination' section (message semantics, fork_turns consideration, agent health check) into a separate coordination-guide.md to reduce SKILL.md size

The Model Selection Guide table shows '(default)' and 'high' for every role — either remove it or only document exceptions/overrides to save tokens

DimensionReasoningScore

Conciseness

The skill is moderately efficient — the architecture diagram, role registry table, and delegation lock table are well-structured and dense. However, there's some redundancy (e.g., the spawn template is shown twice with slight variations for fork_turns, model selection guide uses defaults for every role, and some sections like 'Named Agent Targeting' repeat information already implied by the spawn template). Some explanatory text could be trimmed.

2 / 3

Actionability

The skill provides concrete, copy-paste-ready spawn_agent templates with exact parameter structures, a precise delegation lock table with allowed/blocked verdicts, specific timeout values (1800000ms, 3 min), exact file paths, and clear command patterns. The worker spawn template and GC loop instructions are fully executable.

3 / 3

Workflow Clarity

The sequential pipeline (analyst → architect → developer → QA) is clearly defined with explicit validation via the GC loop (QA fix cycle with max 2 rounds and user escalation). The delegation lock provides a clear checkpoint before every tool call. Timeout handling has a 3-step escalation (STATUS_CHECK → FINALIZE → close). Agent health check reconciliation is specified for resume scenarios.

3 / 3

Progressive Disclosure

The skill correctly references role-specific files (roles/<name>/role.md) and specs (specs/pipelines.md), providing a clear one-level-deep structure. However, no bundle files were provided to verify these references exist, and the SKILL.md itself is quite long (~180 lines) with sections like 'v4 Agent Coordination' and 'fork_turns Consideration' that could potentially be split into separate reference files. The session directory structure and model selection guide add bulk that could be externalized.

2 / 3

Total

10

/

12

Passed

Description

7%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description reads like internal implementation notes rather than a functional skill description. It focuses on architecture ('pure router', 'beat model', 'coordinator-only') instead of describing what the skill actually does or when it should be used. The language is full of jargon and buzzwords ('ui-ux-pro-max design intelligence') that provide no actionable information for skill selection.

Suggestions

Replace internal jargon with concrete actions the skill performs, e.g., 'Creates React components, implements responsive layouts, styles pages with CSS, builds interactive UI elements'.

Add a proper 'Use when...' clause with natural trigger terms users would actually say, e.g., 'Use when the user asks about frontend development, React components, CSS styling, HTML markup, responsive design, or building web interfaces'.

Remove implementation details like 'pure router', 'beat model', 'coordinator-only in monitor.md' that describe internal architecture rather than user-facing capabilities.

DimensionReasoningScore

Specificity

The description uses vague, jargon-heavy language like 'pure router', 'beat model', 'built-in ui-ux-pro-max design intelligence' without listing any concrete actions the skill performs. No specific capabilities like 'create components', 'style pages', or 'build layouts' are mentioned.

1 / 3

Completeness

The 'what' is extremely vague — 'frontend development' and 'design intelligence' don't explain concrete capabilities. The 'when' is limited to 'triggers on team frontend' which is a narrow, unnatural trigger phrase rather than explicit guidance on when Claude should select this skill.

1 / 3

Trigger Term Quality

The only trigger term mentioned is 'team frontend', which is not a natural phrase a user would say. Terms like 'pure router', 'beat model', 'coordinator-only', and 'monitor.md' are internal jargon, not user-facing keywords. Missing natural terms like 'React', 'CSS', 'HTML', 'UI', 'component', 'web page', etc.

1 / 3

Distinctiveness Conflict Risk

The very specific trigger phrase 'team frontend' and references to internal architecture (monitor.md, coordinator-only) make it somewhat distinguishable from generic skills, but the broad 'frontend development' domain could overlap with other frontend or UI-related skills.

2 / 3

Total

5

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

10

/

11

Passed

Repository
catlog22/Claude-Code-Workflow
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.