deploy-service
Skill1 starsChanged 4 months agoApache-2.0View on GitHub
Deploy or redeploy a service to a provider through the governed preflight flow.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- NVIDIA/SkillSpectortheir own version, first seen Oct 13, 2026
- tejastn10/workbenchtheir own version, first seen Oct 13, 2026
- dream-horizon-org/pulsetheir own version, first seen Oct 8, 2026
- vefmvai/sysadmintheir own version, first seen Aug 19, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- NVIDIA/SkillSpector★ 26ksame name
- dream-horizon-org/pulse★ 44same name
- tejastn10/workbench★ 1same name
- vefmvai/sysadmin★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- check-logsSkill
- deployment-statusSkill
- investigate-outageSkill
- provision-supabaseSkill
- restart-serviceSkill
- review-local-repoSkill
- rollback-deploySkill
- set-env-varsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Create a governed deploy/redeploy preflight — describe blast radius and the rollback path.
- Distinctive: line 20
After approval, watch the deployment and verify health from real evidence (status + post-deploy logs/timestamps), then report verified or …
- Distinctive: line 25
create deploy/redeploy preflight (governed)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
When to use
The operator asks to deploy, redeploy, ship, or push a service live (e.g. "redeploy aethos-api on Railway with latest changes").
Steps
- Resolve the target: provider, project, environment, service. If more than one service matches (e.g. both aethos-api and aethos-ui), confirm which to deploy.
- Validate the provider credential and connection (read-only preflight).
- Create a governed deploy/redeploy preflight — describe blast radius and the rollback path. Do NOT execute.
- Surface the preflight in the approvals surface; the operator reviews and approves before anything runs.
- After approval, watch the deployment and verify health from real evidence (status + post-deploy logs/timestamps), then report verified or unconfirmed.
Mutation tools
- create deploy/redeploy preflight (governed)
- verify_deployment (post-approval)
Governance
Mutation. Always preflight → approve → execute → verify. Never report success without post-approval evidence.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.