Content
71%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 well-organized, mostly executable API-deployment guide with a clear workflow and status-verification checkpoint. Its main weaknesses are an entirely monolithic structure with the tool reference inlined (and one dangling script reference) and a missing file-object example for deploy_app's core payload parameter.
Suggestions
Move the 'Available Tools' reference into a references/ file (e.g. references/tools.md), keeping a one-line purpose summary per tool in SKILL.md so the main file stays an overview with well-signaled one-level-deep references.
Document the file object shape for deploy_app's 'files' parameter (path/content/diff fields) with a small worked example, since that is the core payload and currently has no example.
Add an explicit error-recovery loop after the get_app_status step (e.g., 'if status is failed, read the error logs it returns, fix the files, and redeploy only the changed files as diffs'), and remove the duplicate trigger phrasing and the dangling 'Generated by scripts/generate-appdeploy-skill.ts' footer.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Terse parameter lists and proprietary API specifics earn their place, but the 'When to Use This Skill' section and deploy_app's description ('Use this when the user asks to deploy or publish a website or web app and wants a public URL') repeat the frontmatter triggers verbatim, and the trailing '*Generated by scripts/generate-appdeploy-skill.ts*' line references a script that does not exist in the bundle. | 4 / 5 |
Actionability | Concrete curl commands for API key registration, credential persistence, and a JSON-RPC call template, plus full parameter lists for every tool. The gap that keeps it below 5: the core 'files' parameter of deploy_app ('Files to write. NEW APPS: only custom files + diffs to template files') never documents the file object shape or gives a worked example. | 4 / 5 |
Workflow Clarity | The Workflow section gives a clear 5-step sequence (get_deploy_instructions → get_app_template → deploy_app → get_app_status → get_apps) with a status-verification checkpoint, satisfying the batch-operation validation requirement. It falls short of anchor 5 because there is no explicit failure-recovery loop after get_app_status (e.g., if status is 'failed', review error logs, fix, and redeploy). | 4 / 5 |
Progressive Disclosure | The ~110-line 'Available Tools' section is an inline API reference that clearly belongs in a separate references/ file; the skill has good section headers but no content split at all, and its only file pointer (scripts/generate-appdeploy-skill.ts) is dangling. This matches anchor 3 (structure present, content that should be separate is inline) rather than anchor 2, since navigation and organization are decent. | 3 / 5 |
Total | 15 / 20 Passed |