Content
81%Weight 40%Scale 1-5Reviews 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 instruction skill: concrete commands and config for every build path, explicit verification checkpoints with error-recovery loops, and real one-level-deep references. The main weakness is conciseness — a 483-line body that repeats its handoff-honesty rule several times and inlines content already owned by reference files.
Suggestions
State the handoff-honesty rule once (e.g., in 'Default behavior' or the Handoff section) and drop the repeats in 'Host execution boundary', step 1, and step 6 — the rule 'Do not claim the app exists / report unverified rather than ready' currently appears in four or more phrasings.
Under 'Spreadsheet sources', trim the six inline boundary bullets to the two or three highest-value ones (e.g., the Google Sheets access rule and the bounded-samples rule) and let references/spreadsheet-source.md own the rest, since the section already directs the reader there.
Tighten rationale sentences such as 'A host that asks per command will ask many times; one stated expectation up front is what keeps that from reading as something going wrong' into direct imperatives, and replace the bundle-external '/docs/agent-native-config' link with a relative reference or a short inline summary of the supported onboarding modes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 483-line body is mostly dense, non-obvious policy, but the honesty rule is repeated in at least four places ("Do not claim the app exists without an actual path and verification result" in Default behavior, "say what is missing rather than claiming the app is complete" in step 1, "that is the headline — not a caveat below one" in Handoff, "without claiming a live deployment" in step 6), and rationale sentences are padded ("A host that asks per command will ask many times; one stated expectation up front is what keeps that from reading as something going wrong"). This fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; not 2 because nearly all sections carry genuinely non-obvious host-boundary and failure-state guidance rather than filler or explanations of concepts Claude already knows. | 3 / 5 |
Actionability | Guidance is copy-paste ready and covers the common cases: scaffold commands for both layouts ("npx @agent-native/core@latest create <app-directory> --template chat", "pnpm exec agent-native add-app <slug> --template=chat"), dev/build/deploy ("pnpm dev", "npx @agent-native/core@latest build", "npx @agent-native/core@latest deploy --preset netlify"), complete agent-native.json and defineAgentNativeConfig config blocks, an exact API call shape ("sendToAgentChat({ message, context, submit: true, openSidebar: true })"), and a named set of brief headings to produce. | 5 / 5 |
Workflow Clarity | Steps 1-6 are numbered and clearly sequenced (Extract the workflow → Create a fresh app → Turn the workflow into buttons → Keep onboarding shared → Run it immediately → Verify, build, and deploy) with an explicit verification checklist ("Load the reported URL and confirm the main route renders... Click the primary workflow button and confirm the intended agent handoff") and named checks ("Run the checks the generated app's own AGENTS.md names — typecheck and agent-native doctor — and fix what they report before building"). An explicit error-recovery feedback loop exists for scaffold failure: "Retry once where a retry could plausibly help, then stop and report the blocker with the exact command, the failure, and what is already on disk", plus distinct evidence-state labels ("locally running, locally verified, build-ready, deployed, and live-verified"). | 5 / 5 |
Progressive Disclosure | All three referenced files exist and are one level deep (references/attachments.md, references/spreadsheet-source.md, references/fresh-project.md contain no second-level references), and each is clearly signaled with its purpose ("It defines the supported upload and public URL shapes, encoding rules, and handoff behavior"). Not 5: the body inlines content its own reference owns (the six boundary bullets under 'Spreadsheet sources' restate references/spreadsheet-source.md material), and the link to "the Agent-Native app configuration guide (/docs/agent-native-config)" points outside the bundle where the target cannot be verified. | 4 / 5 |
Total | 17 / 20 Passed |