CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-native-reviewer

Reviews code to ensure agent-native parity -- any action a user can take, an agent can also take. Use after adding UI features, agent tools, or system prompts.

65

Quality

80%

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 well-built, highly actionable review skill: concrete search strategies per stack, a numbered process with triage and confidence gating, a clear exclusions list, and a full output template, all without teaching things Claude already knows. Remaining gaps are minor -- a re-verification loop over findings, and offloading the stack table or anti-pattern catalog to reference files if the skill grows.

DimensionReasoningScore

Conciseness

Every section carries skill-specific, non-obvious content (parity definitions, stack search table, anti-pattern catalog) with no padding of concepts Claude already knows; only minor prose (e.g., Core Principles restating later sections) could be trimmed.

4 / 5

Actionability

Copy-paste-ready grep patterns ("Grep for `onClick`, `onSubmit`, `onTap`, `Button`, `onPressed`"), exact per-stack API identifiers ("`tool()` in route handlers, `tools` param in `streamText`/`generateText`"), contrasting anti-pattern/correct code examples, and a complete output template cover the common cases.

5 / 5

Workflow Clarity

The 0-6 process is clearly sequenced with a real triage checkpoint (incremental vs. full audit, stack identification) and explicit confidence gating ("Low (below 0.60)... Suppress these"), but there is no feedback loop that re-verifies the capability map or noun-test findings.

4 / 5

Progressive Disclosure

No bundle files exist, and the single-file body is well-sectioned with each piece placed where the reviewer hits it; at ~184 lines, the stack-specific search strategies and anti-patterns table are plausible candidates for separate reference files, which keeps this below a 5.

4 / 5

Total

17

/

20

Passed

Description

78%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 third-person description that explicitly answers both what and when with a concrete trigger clause and a sharp definition of the parity criterion. Its only real weakness is specificity -- it names one action (reviewing code) rather than enumerating several capabilities -- and it misses a few natural synonyms (agent integration, frontend, MCP).

DimensionReasoningScore

Specificity

"Reviews code to ensure agent-native parity" names the domain and one concrete action, with the parity criterion spelled out, but it does not list several specific actions as the 4+ anchors require.

3 / 5

Completeness

Both parts are explicit: the what ("Reviews code to ensure agent-native parity -- any action a user can take, an agent can also take") and a concrete when clause ("Use after adding UI features, agent tools, or system prompts").

5 / 5

Trigger Term Quality

"Use after adding UI features, agent tools, or system prompts" gives good natural-term coverage, though common synonyms like "agent integration", "frontend", or "MCP" are missing.

4 / 5

Distinctiveness Conflict Risk

"agent-native parity" is a clear niche with distinct triggers, but "Reviews code... after adding UI features" carries minor overlap risk with general code-review skills.

4 / 5

Total

16

/

20

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.

Validation — 13 / 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
udecode/plate
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.