Content
82%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, highly actionable body: every section delivers executable Neon-specific commands or code, and delegation to the parent skill and official docs keeps it navigable. The remaining gains are trimming redundancy (duplicated region list, description echo in When to Use), making the setup sequence explicit with a post-deploy verification step, and moving the full client-section details into reference files.
Suggestions
State the supported regions once (under Availability) and reference it from the intro, and trim the "When to Use" bullets that restate trigger phrases already in the description.
Make the deployment sequence explicit as numbered steps (declare in neon.ts → `neon config plan` → `neon deploy` → `neon env pull`) with a post-deploy verification checkpoint such as `neon bucket list` or a test upload.
Move the full Files SDK and AWS S3 client walkthroughs into a `references/` file (e.g. `references/clients.md`) and keep a one-line pointer to each in SKILL.md, keeping the overview lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and almost entirely Neon-specific novel information (injected AWS env vars, the `forcePathStyle: true` requirement, the Files SDK neon adapter, `neon config plan/apply`, branch-scoped logs) with no explanation of concepts Claude already knows. It falls short of anchor 5 on small redundancies: the supported-region list is stated twice ("Currently available in aws-us-east-2..." in the intro and again under Availability) and the "When to Use" bullets restate trigger material already in the description. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready guidance throughout: a complete `neon.ts` buckets declaration, `neon deploy` / `neon config status|plan|apply`, `neon env pull` and `neon-env run`, an env-var table, and complete working code for both the Files SDK (`upload`, `download`, `url`) and the raw AWS S3 client including presigned GETs. The common cases (set up a bucket, upload, download, share via presigned URL) are all covered with specific code. | 5 / 5 |
Workflow Clarity | The sections follow a coherent real-world sequence — region precondition check ("Check this precondition before setting anything up"), declare buckets in `neon.ts`, `neon config plan` dry-run, `neon deploy`, pull env vars, then client usage — and `neon config status/plan` provide checkpoints. It sits at anchor 4 rather than 5 because the sequence is implicit in section ordering rather than explicitly stepped, and there is no post-deploy verification step (e.g., confirming the bucket exists or a test upload succeeds). | 4 / 5 |
Progressive Disclosure | The body is well-organized with clear headers and appropriately delegates bulk material to one-level-deep targets: the parent `neon` skill (overview, neon.ts full reference, Observability/logs) and official Neon doc URLs. No bundle files exist, and no references are nested or buried. Anchor 4 rather than 5 because the two full client guides (Files SDK and AWS S3 client) plus the CDN/architecture prose sit inline in SKILL.md where a references/ split would keep the overview leaner. | 4 / 5 |
Total | 17 / 20 Passed |