CtrlK
BlogDocsLog inGet started
Tessl Logo

deploying-to-cloud

Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews 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 body with strong validation and feedback loops for destructive operations. Its main weakness is progressive disclosure: most detail lives inline and the one referenced file is missing.

Suggestions

Create the referenced `reference/checklists.md` (or fix the link to the correct path) so the multi-step-operations reference resolves instead of pointing at a nonexistent file.

Move the long Billing/Usage and Config detail blocks into a separate reference file (e.g. `reference/cli-reference.md`) and link from the body, keeping SKILL.md as a lean overview.

Tighten the Configuration-and-Resources and Queues-and-Scheduling sections to bullet essentials; some sentences restate Cloud-specific constraints that could be condensed.

DimensionReasoningScore

Conciseness

Dense and information-rich (Laravel Cloud-specific facts like the 15-minute timeout, ephemeral filesystems, R2 bucket-level visibility) that assume Claude's competence; a few sections could be tightened and the length is high, keeping it just below a 5.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with exact flags and jq examples (e.g., `cloud usage --json -n | jq '.currentSpendCents'`, `echo "$VALUE" | cloud secret:create --name=NAME --json -n`) covering the common cases.

5 / 5

Workflow Clarity

Clear deployment paths, an explicit "When a Command Fails" feedback loop (diagnose, fix once, ask if it recurs), mandatory deploy-then-monitor sequencing, destructive-op confirmation, and a Verification section with checkpoints — validation is present so the destructive-cap does not apply.

5 / 5

Progressive Disclosure

Section structure is good, but the bulk of the CLI command reference, billing, and config detail is inlined rather than split out, and the single external reference — `[reference/checklists.md](reference/checklists.md)` — points to a file that does not exist (no reference/ directory is present), so navigation is not actually viable.

3 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: third-person voice, concrete capabilities, explicit Use-when and Triggers-on guidance, and a distinctive Laravel Cloud niche. No first/second person, no fluff, no over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and managed resources — "deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks" — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both what ("Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI") and when ("Use when the user wants to..." plus "Triggers on...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural terms and synonyms users would actually say — "deploy an app", "ship to Cloud", "billing, usage, or spend", "the `cloud` CLI" — plus a dedicated "Triggers on..." clause covering deployment, shipping, provisioning, and troubleshooting.

5 / 5

Distinctiveness Conflict Risk

Clear niche tied to Laravel Cloud and its `cloud` CLI with platform-specific triggers, making it unlikely to fire for unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
laravel/boost
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.