agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/frontier-ghcp-ttt-rvas/sessions/session-m3-05-agent-skills-ecosystem/lab/solution/integrated-workflow/.github/skills/deployment/SKILL.md

deployment

Skill3 starsChanged 54 days agoMITView on GitHub

Use for approved environment configuration, deployment changes, releases, or dependencies that affect deployment. Use SCREAMINGSNAKECASE names such as DATABASEURL, APIKEY, and PORT. Document required values in .env.example; never hardcode secrets. Redeploy the previous known-good version when a deployment fails. Check logs, health endpoint /api/health, key API responses, error rate, and response time. Record the failure and update the checklist when needed. Confidence: medium

  • Reads credentials

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use for approved environment configuration, deployment changes, releases, or dependencies that affect deployment.

    line 5
  2. Very specific:

    Use SCREAMING_SNAKE_CASE names such as DATABASE_URL, API_KEY, and PORT.

    line 9

“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “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

Deployment Conventions

When to use

Use for approved environment configuration, deployment changes, releases, or dependencies that affect deployment.

Environment

Use SCREAMING_SNAKE_CASE names such as DATABASE_URL, API_KEY, and PORT. Document required values in .env.example; never hardcode secrets.

Before deployment

  • npm test passes.
  • npm run lint has no errors.
  • Target-environment variables and migrations are ready.
  • No secret is in source.
  • README, version, and changelog changes are reviewed.

Rollback and monitoring

Redeploy the previous known-good version when a deployment fails. Check logs, health endpoint /api/health, key API responses, error rate, and response time. Record the failure and update the checklist when needed.

Confidence: medium

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