agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/check-secrets/SKILL.md

check-secrets

Skill2 starsChanged 19 days agoApache-2.0View on GitHub

Verify secrets and configmaps in a namespace. Use for deployment config verification, debugging missing env vars, or auditing secret presence.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Verify secrets and configmaps are properly configured in a namespace.

    line 8
  2. Distinctive:

    If deployment references missing: list missing secrets and configmaps

    line 37

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

Check Secrets

Verify secrets and configmaps are properly configured in a namespace.

Inputs

InputTypeDefaultPurpose
namespacestringrequiredKubernetes namespace
environmentstringstagestage, production, ephemeral
deploymentstring""Optional: specific deployment to check references

Workflow

1. Load Persona

  • persona_load("devops")

2. List Resources

  • kubectl_get_secrets(namespace="{{ namespace }}", environment="{{ environment }}")
  • kubectl_get_configmaps(namespace="{{ namespace }}", environment="{{ environment }}")

3. Check Deployment References (if deployment specified)

  • kubectl_describe_deployment(deployment="{{ deployment }}", namespace="{{ namespace }}", environment="{{ environment }}")
  • Parse for secretKeyRef, configMapKeyRef, secretRef, configMapRef
  • Compare referenced names to existing secrets/configmaps

4. Report Missing

  • If deployment references missing: list missing secrets and configmaps

5. Error Recovery

  • "unauthorized" → kube_login(cluster="stage" or "prod")
  • "no route to host" → vpn_connect()

6. Memory

  • memory_session_log("Checked secrets and configmaps", "namespace={{ namespace }}, secrets={{ count }}")

Output

Report: secrets list (name, type), configmaps list, deployment references (if specified), and any missing resources.

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