agentleFS
davidvornholtdavidvornholt/mailbox/.agents/skills/secrets-and-config/SKILL.md

secrets-and-config

Skill2 starsChanged yesterdayMITView on GitHub

Use when changing application configuration, environment variables, or generated development environments, or when decrypting or changing SOPS secret files.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. davidvornholt/mail-mcp★ 2100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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 repository13 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Never let a decrypted secret reach a command's output, not even through a filter, because the session transcript keeps it and filters miss …

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Secrets and configuration

A value is secret when disclosing it enables impersonation, data access, or cost. Secrets live only in SOPS-encrypted YAML. Every other value lives in plain configuration beside the code that reads it.

Never let a decrypted secret reach a command's output, not even through a filter, because the session transcript keeps it and filters miss multi-line values such as private keys. Pipe it into the command that needs it, or compare values by hash.

Document each value once, where it is declared. A plain value is explained in its configuration file. A secret is explained in the matching *.example.yaml, which mirrors the key shape of the encrypted file, because the encrypted file cannot carry readable comments. Use a workspace README only for setup that these declarations cannot express.

SOPS identities, recipients, CI secrets, and brokered provider credentials are covered in the declarative-infra skill's secrets reference.

Development environments

just dev-env-generate (bun standards dev-env) generates each workspace's .env.local from three layers, keyed by workspace (apps.<name>, packages.<name>). just dev-refresh edits the dev secrets and then regenerates.

LayerFileNotes
Plainconfig/dev.yamlTracked
Secretsecrets/dev.yamlTracked and encrypted; values are strings
Localconfig/dev.local.yamlGitignored; overrides both tracked layers, including secret values

A key lives in at most one of the two tracked layers. Local changes belong in config/dev.local.yaml, because generation rewrites the whole .env.local.

A plain layer can reference one half of a broker-owned S3 credential pair instead of copying it, so the value never goes stale after the broker rotates it: { brokeredS3: <target>, key: <dotted.key>, part: access_key_id | secret_access_key }. The reference resolves only when encrypted secrets/dev.yaml authorizes that pair in its reserved top-level brokeredReferences list as <target>:<dotted.key>.

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.