CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-dev

Coding practices for frontend development in Atomic CRM. Use when creating or modifying React components, forms, list pages, detail views, filters, data fetching, or responsive layouts.

80

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A tight, well-structured reference skill that assumes Claude's competence and delivers codebase-specific conventions as concrete, actionable rules. It pairs a clear usage frame with a closing verification checklist and avoids both verbosity and concept over-explanation.

DimensionReasoningScore

Conciseness

Lean throughout — every line states a codebase-specific convention (import paths, hooks, file structure) with no explanation of concepts Claude already knows and no padding; each token earns its place.

3 / 3

Actionability

Gives concrete, copy-applicable guidance: exact import sources ('@/components/admin/'), named hooks ('useListContext', 'useGetOne'), and a standard resource file layout — fully actionable even without code blocks (an instruction/reference skill).

3 / 3

Workflow Clarity

Explicitly frames itself as a reference skill ('read the relevant section before writing code, then verify against the checklist at the end') and closes with a verification checklist plus a Red Flags section, providing a clear read-then-verify loop.

3 / 3

Progressive Disclosure

A single well-organized file with clear section headers and no nested references; no bundle files are needed for these conventions, and navigation is trivial via the labeled sections.

3 / 3

Total

12

/

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.

A concise, third-person description that states a clear niche (Atomic CRM frontend), enumerates concrete capability areas, and provides an explicit 'Use when' trigger. It is well above the rubric's vague-fluff examples and uses natural trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete action categories — 'creating or modifying React components, forms, list pages, detail views, filters, data fetching, or responsive layouts' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' ('Coding practices for frontend development in Atomic CRM') and 'when' ('Use when creating or modifying...'), matching the top anchor with an explicit trigger clause.

3 / 3

Trigger Term Quality

Uses natural terms a developer on this codebase would actually say — 'React components, forms, list pages, detail views, filters, data fetching, responsive layouts' — with good coverage and no jargon-only language.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to 'frontend development in Atomic CRM' with trigger terms unlikely to fire for unrelated skills; the body further separates it from backend-dev and theming 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
marmelab/atomic-crm
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.