Conciseness

The body is dense with project-specific facts Claude would not know (version-matched corpus package, template reuse policy, configure/compose/eject ladder) and avoids re-teaching generic concepts. A few long prose passages (e.g., the paragraph on the headless loop's tool exposure) could be tightened, keeping it below the lean-every-token-earns-its-place anchor.

Actionability

Commands are copy-paste ready and complete: `pnpm action framework-search --pattern "defineAction" --scope source --path "templates/*/actions/*.ts"`, the version-pinned corpus install via `node -p`, `rg` and `cp` fallbacks, plus mode guidance (substring/glob/sql-like/regex). These cover the common lookup cases end to end.

Workflow Clarity

A clear sequence is present: use `framework-search` first, narrow with scope, then use focused readers for the full page/file, with conditional branches for a missing corpus and an unavailable action runner. It is read-only lookup with no destructive or batch operations, so no cap applies, but there are no explicit checkpoints validating that a search actually answered the question.

Progressive Disclosure

This is a single-file skill with no bundle files; sections are well-organized with clear headers (Rule, Why, How, Reuse, Useful Slugs, Don't). At ~150 lines, the Useful Slugs table and the visual-docs authoring section are borderline content that could live in separate reference files, which keeps it just below the ideally-split anchor.

Specificity

Names the domain ("version-matched Agent-Native framework docs and source bundled in node_modules") and one concrete action ("find"), but stops short of listing several specific actions like a 4 or 5 would. Voice is third-person/neutral, so no voice penalty applies.

Completeness

The "what" is explicit ("find version-matched Agent-Native framework docs and source bundled in node_modules") and the "when" is explicit with concrete trigger phrases ("Use before implementing or answering questions about @agent-native/core APIs, generated apps, workspaces, templates, or advanced features"), matching the anchor that clearly answers both.

Trigger Term Quality

"@agent-native/core APIs, generated apps, workspaces, templates" are natural terms a user of this ecosystem would say, anchored by the concrete package name. A few natural variations are missing and "advanced features" is generic, so it falls just below the comprehensive-synonym coverage of a 5.

Distinctiveness Conflict Risk

The description carves out a clear niche — version-matched lookup of a specific framework's (@agent-native/core) docs and source — with triggers unlikely to fire for unrelated skills, matching the clear-niche/minimal-conflict anchor.