CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-workflow

Coordinates frontend and UI implementation, refactoring, and review using the project's color system, React performance, shadcn/ui, interface-polish, and animation-vocabulary skills. Use when the user explicitly requests /frontend-workflow for a frontend task.

68

Quality

83%

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

78%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 an efficient, well-organized orchestrator that delegates to specialist skills via concrete paths and a clear sequenced workflow with validation. It is strong across all dimensions, with only minor tightening possible in conciseness and workflow feedback loops.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence without restating known concepts, with only minor phrasing that could be tightened in the specialist-skills list.

4 / 5

Actionability

Concrete file paths (e.g. "read ../vercel-react-best-practices/SKILL.md, then load only the applicable files from its rules/ directory") and explicit conditions give mostly executable guidance with minor gaps.

4 / 5

Workflow Clarity

A clear five-step sequence (Understand, Select, Implement, Validate, Report) includes validation checkpoints and a resolve-blocking-findings loop, but the feedback loops are mild rather than fully explicit.

4 / 5

Progressive Disclosure

It is a well-structured overview that points to one-level-deep sibling SKILL.md files with clearly signaled paths and no nested reference chains.

5 / 5

Total

17

/

20

Passed

Description

87%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 is third-person, concise, and answers both what and when with a concrete, well-gated trigger. It is strong overall, with only slight room to broaden natural trigger synonyms.

DimensionReasoningScore

Specificity

"Coordinates frontend and UI implementation, refactoring, and review" names the domain plus three concrete actions, with minor coverage gaps rather than comprehensive enumeration.

4 / 5

Completeness

It clearly states what (coordinates implementation, refactoring, review via named specialist skills) and when (explicit /frontend-workflow request) with a concrete trigger phrase.

5 / 5

Trigger Term Quality

"Use when the user explicitly requests /frontend-workflow for a frontend task" supplies natural terms like "frontend" and "UI", but a few common synonyms (React, component, styling) are absent.

4 / 5

Distinctiveness Conflict Risk

The trigger is gated on an explicit /frontend-workflow request, giving it a clear niche and minimal conflict risk despite overlapping with the specialist skills it orchestrates.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MODSetter/SurfSense
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.