CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-native-toolkit

Inventory and ownership rules for shared Agent Native workspace UI. Use before building app chrome, settings, navigation, sharing, collaboration, setup, history, comments, chat rails, agent UX, or repeated workspace behavior.

71

Quality

88%

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

100%

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

The body is a lean, well-structured ownership and discovery guide with concrete commands, a sequenced checklist, and an explicit conformance validation step. It avoids padding and appropriately delegates detail to related skills.

DimensionReasoningScore

Conciseness

The body is dense and sectioned with no padding or explanations of concepts Claude already knows; every list item earns its place (e.g., the design-system boundary and reusable kits catalogs are tight).

3 / 3

Actionability

Concrete commands and APIs are given ("agent-native eject --list", "docs-search", "source-search", "defineDesignSystem", conformance kit), plus a 9-step checklist with named files and components — actionable guidance rather than vague direction.

3 / 3

Workflow Clarity

"Discover Before Building" and the "Implementation Checklist" are explicit numbered sequences with a validation checkpoint (step 9 verifies the default and a non-Tailwind adapter via the conformance kit, including focus and portal stacking).

3 / 3

Progressive Disclosure

Content is split into clearly labeled overview sections that point one level deep to related skills ("agent-page", "customizing-agent-native"); no nested/broken references and no monolithic wall of text, though no bundle files are present to verify further.

3 / 3

Total

12

/

12

Passed

Description

77%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly communicates purpose and trigger conditions with a strong surface enumeration. It is slightly hampered by framework jargon in trigger terms and overlap with related sibling skills.

Suggestions

Replace framework-internal terms like "app chrome" and "chat rails" with language users naturally say (e.g., "app UI chrome / top bars", "recent-conversation lists").

Tighten the trigger surface list so it does not duplicate the domains owned by related skills (sharing, real-time-collab, frontend-design), reducing conflict risk.

DimensionReasoningScore

Specificity

Names the domain ("ownership rules for shared Agent Native workspace UI") and enumerates many concrete surfaces ("app chrome, settings, navigation, sharing, collaboration, setup, history, comments, chat rails, agent UX"), matching the multiple-specific-actions anchor.

3 / 3

Completeness

It states what the skill provides ("Inventory and ownership rules") and gives an explicit "Use before building..." trigger clause answering when to use it, satisfying both halves.

3 / 3

Trigger Term Quality

Coverage of surface names a user would reference is decent, but several terms ("app chrome", "chat rails") are framework-internal jargon rather than the natural language users say, so it is not full natural-term coverage.

2 / 3

Distinctiveness Conflict Risk

The Agent Native ownership niche is distinct, but the broad trigger surface list (sharing, collaboration, navigation) overlaps the sibling skills this very file points to, so it could still trigger for a neighboring skill.

2 / 3

Total

10

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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