agentleFS
Sign inStart free
pilotmainpilotmain/AethOS/skills/set-env-vars/SKILL.md

set-env-vars

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

Set or update environment variables on a provider service, governed and redacted.

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:

    Read the current variables so the change is additive and non-conflicting.

    line 14
  2. Distinctive:

    Create a governed set-env preflight listing exactly which keys change (mask values).

    line 15
  3. Distinctive:

    Verify the variable is applied and the service is healthy afterward.

    line 19
  4. Distinctive:

    create set-env preflight (governed)

    line 23

≈ “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 to add, change, or remove environment variables / config on a service ("set WORKSPACE_SUITE_ENABLED=true on aethos-api").

Steps

  1. Resolve provider + project + environment + service. Confirm if ambiguous.
  2. Read the current variables so the change is additive and non-conflicting.
  3. Create a governed set-env preflight listing exactly which keys change (mask values). Secrets are read from the vault, never echoed into chat or logs.
  4. Operator approves; a service restart/redeploy may be required for the new value to take effect — call that out and offer it as the next governed step.
  5. Verify the variable is applied and the service is healthy afterward.

Mutation tools

  • create set-env preflight (governed)
  • provider_status (post-approval verification)

Governance

Mutation. Preflight → approve → execute → verify. Never print secret values; keys only.

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