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

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

An exemplary dense skill body: purely repo-specific knowledge, clear step sequencing with verification, and well-signaled external references. The only gaps are undefined test/route helper utilities that leave the templates slightly short of copy-paste ready.

Suggestions

Define or point to the imported helpers (lazyNamed, seedAuthedSession, installShellMocks, mockJsonResponse, paged, SAMPLE) — e.g., one line naming the module they come from — so the templates are executable without guessing.

Split the admin/dashboard variations into two short labeled sub-sections per step (or reference files) instead of inline parentheticals like '(dashboard: inline type PagedResponse<T> ...)' so each app's path reads as a coherent whole.

Dimension	Reasoning	Score
Conciseness	Every line carries repo-specific, non-obvious information (the admin/dashboard divergence table, shared conventions, race-safe mutate pattern); there is no explanation of concepts Claude already knows and no padding.	5 / 5
Actionability	The step templates and verify command ('cd clients/{app} && npm run lint && npm run test:e2e') are concrete, but templates rely on placeholders ({Resource}, {Module}) and helpers (lazyNamed, seedAuthedSession, mockJsonResponse, paged, SAMPLE) that are referenced but not defined here — mostly executable with minor gaps.	4 / 5
Workflow Clarity	Steps 1–7 are clearly sequenced with an explicit validation checkpoint (Step 7: lint + test:e2e) and a closing checklist that doubles as a verification loop; the workflow is not destructive/batch, so no cap applies.	5 / 5
Progressive Disclosure	No bundle files exist, and the body is cleanly sectioned with clearly signaled one-level-deep pointers to .agents/rules/frontend/ app files; the divergence table and templates are appropriately inline, though overall organization could split the two apps' variations more explicitly.	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 description: it states concrete deliverables, an explicit 'Use when' trigger, and a tightly scoped niche with app-specific detail. The only weakness is keyword coverage that favors internal jargon over the natural synonyms a user might say.

Dimension	Reasoning	Score
Specificity	The description enumerates the concrete deliverables — 'API module, page, lazy route, (admin) permission gate, Playwright test' — giving comprehensive, specific coverage of what the skill produces, matching the top anchor exactly.	5 / 5
Completeness	It explicitly answers both what ('Add a list+create page to a React app ... API module, page, lazy route, (admin) permission gate, Playwright test') and when ('Use when adding any frontend screen') with concrete trigger phrasing, matching the top anchor.	5 / 5
Trigger Term Quality	'React app', 'frontend screen', and 'list+create page' are natural user phrasings, but the keyword mix leans on internal jargon ('lazy route', 'permission gate') and misses common variations like 'new page', 'view', or 'screen'. Good coverage with a few natural terms missing — between anchors 4 and 5.	4 / 5
Distinctiveness Conflict Risk	The niche is sharply scoped to two named apps ('clients/admin or clients/dashboard') with app-specific mechanics, making it clearly distinguishable from generic React/frontend skills; conflict risk is minimal.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: fullstackhero/dotnet-starter-kit
Path: .agents/skills/add-react-page/SKILL.md
Commit: 0bd98e3

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.