CtrlK
BlogDocsLog inGet started
Tessl Logo

add-react-page

Add a list+create page to a React app (clients/admin or clients/dashboard) — API module, page, lazy route, (admin) permission gate, Playwright test. Use when adding any frontend screen. See .agents/rules/frontend/.

72

Quality

90%

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

88%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 tightly written, highly actionable procedural skill with a clear sequenced workflow and verification step. The only real weakness is template placeholders in code examples that prevent literal copy-paste execution.

Suggestions

Add a brief note (one line) clarifying that {Resource}/{resources}/{area} are substitution placeholders and how to derive them from the argument-hint, so the code examples are unambiguously actionable.

Consider extracting the admin-vs-dashboard divergence table into a reference file and linking it, keeping SKILL.md as a leaner overview that signals the one-level-deep reference.

Add a short error-recovery hint in Step 7 (e.g. 'if lint/test fail, re-check param casing per app and permission mirroring') to make the verify step a fuller feedback loop.

DimensionReasoningScore

Conciseness

Lean and dense — a divergence comparison table plus tight code snippets with no padding or explanation of concepts Claude already knows (React, TanStack Query, etc.); every line carries specifics.

5 / 5

Actionability

Provides concrete, near-executable code for each step (imports, signatures, route entries, test scaffolding), but uses template placeholders like {Resource}/{resources}/{area} throughout so it is not literally copy-paste ready — a minor gap.

4 / 5

Workflow Clarity

Seven clearly sequenced steps with an explicit 'Step 7 — Verify' checkpoint ('npm run lint && npm run test:e2e') and a closing checklist that reinforces validation; the operation is additive (not destructive/batch) so the present verification suffices.

5 / 5

Progressive Disclosure

Well-organized into a comparison table, seven labeled steps, and a checklist, with external rules clearly signaled at the top ('Read .agents/rules/frontend/shared.md plus the app file'); no bundle files are provided, so content is appropriately self-contained with minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

92%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, specific description that names concrete deliverables and an explicit trigger. It is well-scoped to its niche and answers both what and when clearly.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'API module, page, lazy route, (admin) permission gate, Playwright test' plus 'list+create page' — giving comprehensive coverage of the skill's components.

5 / 5

Completeness

Explicitly answers both 'what' (add a list+create page with API module, page, lazy route, permission gate, Playwright test) and 'when' ('Use when adding any frontend screen') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Includes a natural trigger clause ('Use when adding any frontend screen') plus domain terms ('React app', 'list+create page'), but lacks common synonyms like 'new page' or 'add a screen' that a user might naturally say.

4 / 5

Distinctiveness Conflict Risk

Scoped to React apps in two named clients (admin/dashboard) with a specific list+create pattern, giving it a clear niche and minimal conflict risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
fullstackhero/dotnet-starter-kit
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.