appdeploy
Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl.
82
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/appdeploy/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that concisely covers what the skill does (deploy web apps with specific infrastructure components), when to use it (user asks to deploy/publish and wants a public URL), and how it works (HTTP API via curl). It uses third person voice correctly and includes natural trigger terms that users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: 'Deploy web apps with backend APIs, database, and file storage' and specifies the mechanism 'Uses HTTP API via curl'. This goes beyond naming a domain and provides concrete architectural components. | 3 / 3 |
Completeness | Clearly answers both what ('Deploy web apps with backend APIs, database, and file storage') and when ('Use when the user asks to deploy or publish a website or web app and wants a public URL'). The explicit 'Use when...' clause with trigger scenarios is present. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'deploy', 'publish', 'website', 'web app', 'public URL'. These cover the most common ways users would phrase deployment requests. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of deployment, public URL, backend APIs, database, and file storage creates a clear niche. The mention of 'curl' and 'HTTP API' further distinguishes it from general web development or hosting skills. Unlikely to conflict with code-writing or local development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides actionable, executable guidance with concrete curl commands and a clear deployment workflow, which is its main strength. However, it suffers from being a monolithic document with extensive auto-generated API parameter documentation that should be offloaded to a reference file. The workflow also lacks error recovery steps for deployment failures, which is important for a deployment-oriented skill.
Suggestions
Move detailed tool parameter documentation to a separate REFERENCE.md or API.md file, keeping only the core tools (deploy_app, get_deploy_instructions, get_app_status) with brief descriptions in SKILL.md
Add explicit error recovery steps to the workflow: what to do when get_app_status returns 'failed', how to diagnose with error logs, and how to retry deployment
Remove the boilerplate Limitations section at the bottom which adds generic guidance Claude already knows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes excessive parameter documentation that reads like auto-generated API reference. The full parameter lists for tools like src_grep and src_read could be offloaded to a separate reference file. Some tool descriptions repeat information Claude could infer. | 2 / 3 |
Actionability | Provides fully executable curl commands with exact endpoints, headers, and JSON payloads. The setup flow includes concrete API calls with example responses, and the workflow gives specific tool names to call in sequence. | 3 / 3 |
Workflow Clarity | The workflow lists a clear 5-step sequence for deployment, but lacks explicit validation/feedback loops. Step 4 mentions checking status but doesn't specify what to do if the build fails (retry? check logs? fix and redeploy?). For a destructive/deployment operation, the absence of error recovery guidance caps this at 2. | 2 / 3 |
Progressive Disclosure | All content is in a single monolithic file with no references to external files. The detailed parameter documentation for 11 tools creates a wall of text that should be split into a separate API reference file, with SKILL.md providing only the core workflow and most-used tools. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
1a9f5ac
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.