agentleFS
Sign inStart free
dynos-fitdynos-fit/dynos-work/skills/execution/infra-executor/SKILL.md

execution/infra-executor

Skill2 starsChanged 8 months agoMITView on GitHub

Internal: Infrastructure Executor. Implements deployment, CI/CD, container, IaC, and environment configuration changes. Write evidence on completion.

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

    Do not accept deployment config that only works locally.

    line 12
  2. Distinctive:

    Every environment, secret, permission, and rollout assumption must be explicit.

    line 13
  3. Distinctive:

    If rollback order matters, the executor must state and verify it.

    line 14

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

dynos-work: execution/infra-executor

Spawn the infra-executor agent with the user's prompt as the instruction.

Ruthlessness Standard

  • Do not accept deployment config that only works locally.
  • Every environment, secret, permission, and rollout assumption must be explicit.
  • If rollback order matters, the executor must state and verify it.

What to pass

Pass the user's full prompt verbatim. Do not summarize or sanitize it. Prepend a short hard wrapper that tells the agent to inspect the deployment surface, preserve least privilege, and verify rollback or compatibility behavior before writing 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