agentleFS
Sign inStart free
pilotmainpilotmain/AethOS/skills/deployment-status/SKILL.md

deployment-status

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

Read a service's current deployment status and health across providers.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    If ambiguous, ask which provider and target.

    line 14
  2. Distinctive:

    Read the latest deployment (status, commit, created time) and current health.

    line 15
  3. Distinctive:

    If unhealthy or stale, offer the next governed step (check logs, redeploy).

    line 18
  4. Distinctive:

    Read-only. Any redeploy/restart is a separate governed action (preflight → approve).

    line 27

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When to use

The operator asks "is it deployed?", "what's the status?", "is the latest live?", or wants a governed deployment/health summary for a service.

Steps

  1. Identify the provider + target (Railway/Vercel, project/service, environment). If ambiguous, ask which provider and target.
  2. Read the latest deployment (status, commit, created time) and current health.
  3. Summarize: deployment status, commit/source, health, and whether the latest commit is the one running.
  4. If unhealthy or stale, offer the next governed step (check logs, redeploy).

Readonly tools

  • provider_status / provider_inventory
  • recall_last_deployment_thread

Governance

Read-only. Any redeploy/restart is a separate governed action (preflight → approve). Never claim success without evidence.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free