Content
75%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 high-quality integration guide: nearly all content is project-specific and actionable, with correct sequencing of billing-critical operations and good internal navigation. The main improvement levers are de-duplicating section content vs. the gotchas list, replacing placeholder code comments with real error responses, and splitting bulk reference material into bundle files.
Suggestions
Remove the duplicated long-form explanations in 'Common Gotchas' (items 3, 5, 8 repeat the Naming Conventions, Plan Structure, and Proportional Billing sections) — keep gotchas as one-line pointers to those sections.
Replace placeholder comments like `// Return 402 with balance info` with the actual error-response code so the credit-check and middleware snippets are copy-paste ready.
Move the SDK/CLI reference detail and plan-item variant specs into references/ files (e.g., references/sdk.md, references/plans.md) linked from short summary sections, keeping SKILL.md as a lean overview.
Add an explicit post-push validation step (e.g., re-run `bun x atmn preview` or verify plans in the dashboard after `atmn push --prod`) to close the feedback loop on config changes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with non-inferable, project-specific knowledge (plan-item variant rules, interval exclusivity, fail-closed policy, secret-key rotation), but several topics are explained twice at length — proportional billing, naming conventions, and interval exclusivity each reappear in 'Common Gotchas' — which is trimmable duplication. Fits 'minor instances of over-explanation'; not 5 because of this repeated content. | 4 / 5 |
Actionability | Concrete, near-executable TypeScript and `bun x atmn ...` commands with real project paths cover the common cases, but a few snippets are templates rather than copy-paste ready — e.g. `if (!allowed) { // Return 402 with balance info }` is a comment placeholder and snippets reference undefined locals (`error`, `data.model`). Fits 'concrete code with minor gaps'; not 5 due to those placeholders. | 4 / 5 |
Workflow Clarity | Sequencing and most checkpoints are explicit (blocking `getOrCreate` before `check()`, fail-closed credit gating before expensive provider calls, `atmn preview` dry-run before push, authGuard → customer-ensuring middleware → credit gate). Not 5 because there is no validate-after-push feedback loop or error-recovery steps for config pushes, leaving 'minor validation gaps'. | 4 / 5 |
Progressive Disclosure | With no bundle files, the single 345-line body is well organized — clear headers, tables, `---` separators, and a project-file map make navigation easy — matching 'good structure; most content appropriately placed'. Not 5 because bulk reference material (full SDK/CLI reference, plan-variant details) is inlined in SKILL.md where one-level-deep reference files would keep the overview leaner. | 4 / 5 |
Total | 16 / 20 Passed |