adding-a-feature

The four-area checklist every new feature must complete. Use when adding any feature, integration, or capability to ensure the agent and UI stay in parity.

Quality

83%

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

77%

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

A highly actionable, well-sequenced checklist with concrete framework APIs and a verification checklist. Its main weakness is verbosity and inline detail that overlaps the related skills it points to, rather than being split out into those references.

Suggestions

Tighten the dense paragraphs in the Action area (provider-backed integrations, credentials, attachments, deep-link/mcpApp metadata) into checklist bullets, deferring full explanations to the already-referenced external-agents, real-time-sync, and sharing skills.

Move the 'Adding a new route' and 'One more area — sharing' sections into their related skills (client-side routing / sharing) and keep only a one-line pointer here, reducing the body length.

Consider extracting the per-area detailed rules into a reference file so SKILL.md reads as a concise four-area overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	Most content is project-specific guidance Claude would not already know, so it avoids explaining basic concepts, but the ~180-line body is verbose with long prose paragraphs that could be tightened or pushed to referenced skills.	2 / 3
Actionability	It gives concrete, executable guidance throughout: named APIs (defineAction, useActionQuery, useChangeVersions(["dashboards","action"]), ownableColumns()), a complete tsx code block, and specific commands like 'pnpm action view-screen'.	3 / 3
Workflow Clarity	The four areas are explicitly sequenced 'in order' (UI, Action, Skills, App-state) and close with a six-item Verification checklist that serves as explicit validation checkpoints for the completed feature.	3 / 3
Progressive Disclosure	References to related skills are well signaled and one level deep ('See the real-time-sync skill', a Related Skills list), but there are no bundle files and substantial inline detail (provider-API patterns, deep-link/mcpApp metadata, routing rules, the sharing TL;DR) duplicates content that dedicated related skills already cover.	2 / 3
	Total	10 / 12 Passed

Description

90%

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 with an explicit 'Use when' trigger and a distinct agent/UI parity niche. It is held back from full marks only because it describes the checklist abstractly without naming the four areas it covers.

Dimension	Reasoning	Score
Specificity	It names the domain ('feature, integration, or capability') and the 'four-area checklist' concept, but does not enumerate the concrete four areas, so it lists some actions rather than multiple specific concrete ones.	2 / 3
Completeness	It explicitly answers what ('The four-area checklist every new feature must complete') and when ('Use when adding any feature, integration, or capability') with an explicit trigger clause.	3 / 3
Trigger Term Quality	'Use when adding any feature, integration, or capability' uses natural phrasings a user would actually say when reaching for this skill, with good coverage of the domain's main variants.	3 / 3
Distinctiveness Conflict Risk	The 'ensure the agent and UI stay in parity' purpose carves a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: BuilderIO/agent-native
Path: .agents/skills/adding-a-feature/SKILL.md
Commit: c1ee18b

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.