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.

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

82%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 tight, well-structured reference skill that assumes Claude's competence and provides concrete, scannable conventions plus a verification checklist. It would reach the top anchors by adding a representative code snippet and a one-level-deep reference file for the longer convention lists.

Suggestions

Add one short copy-pasteable code block (e.g. a minimal ContactInputs.tsx + index.tsx registration) to lift actionability to fully executable.

Split the per-resource file-structure and data-fetching conventions into a single references/ file linked from the body, giving genuine one-level-deep progressive disclosure.

Add an explicit error-recovery note to the Verification section (what to do when a checklist item fails) to strengthen the workflow feedback loop.

DimensionReasoningScore

Conciseness

Lean reference-style bullets with no padding or explanation of concepts Claude already knows; every line states a concrete convention, matching the 'every token earns its place' level-5 anchor.

5 / 5

Actionability

Highly concrete guidance with exact import paths, hook names, and file conventions plus grounding examples (e.g. 'dataProvider.getActivityLog() in ActivityLog.tsx'), but it lacks copy-paste code blocks, fitting level 4 rather than the executable-block level 5.

4 / 5

Workflow Clarity

Explicitly frames a read-section → write-code → verify-checklist workflow with a 6-item verification checklist, giving clear sequence and validation; it stops short of level 5's error-recovery feedback loops.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (When to Use, architecture, CRUD, forms, filters, responsive, Red Flags, Verification) with easy navigation; no bundle files exist to split, and cross-skill refs are cleanly signaled, but it is a single self-contained file rather than an overview pointing one level deep.

4 / 5

Total

17

/

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-scoped description that pairs a concrete trigger list with an explicit 'Use when' clause and is anchored to a specific app. The 'what' summary is slightly abstract, keeping completeness just below the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'React components, forms, list pages, detail views, filters, data fetching, or responsive layouts' — giving comprehensive coverage of the frontend surface, matching the level-5 anchor rather than the 'minor gaps' of level 4.

5 / 5

Completeness

Both 'what' ('Coding practices for frontend development in Atomic CRM') and 'when' ('Use when creating or modifying...') are present with explicit trigger phrases, but the 'what' is high-level compared to the concrete-action 'what' in the level-5 anchor, so level 4 fits best.

4 / 5

Trigger Term Quality

Natural frontend terms ('React components, forms, list pages, filters, responsive layouts') align with what a user would say, but a few common synonyms (e.g. 'CRUD pages', 'detail pages') are absent, fitting level 4 rather than the synonym-rich level 5.

4 / 5

Distinctiveness Conflict Risk

Scoped to 'frontend development in Atomic CRM' with specific React/ra-core triggers, carving a clear niche distinct from sibling skills (backend-dev, shadcn-customization) and minimizing conflict risk.

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
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.