SKILLEMALL.ai

BF secret-safe

Secure API key and secrets management for agent skills. Use this skill whenever a task requires authenticating with an external service, reading or writing API keys, tokens, passwords, or credentials of any kind. Also trigger when auditing other skills for credential leaks, when a user asks how to securely pass a secret to a skill, or when reviewing a SKILL.md that handles sensitive values. This skill teaches the agent how to handle secrets WITHOUT ever placing them in the LLM context, prompts, logs, or output artifacts — using OpenClaw's native env injection instead.

modbender/skill-library-mcp Agent Skills author: modbender MIT 3 files body ≈ 1 760 tokens Open the sourcegithub.com analyzed 2 d ago

Secure API key and secrets management for agent skills.

As a process F 46/100 · Will not run — References files that are not bundled: scripts/run-with-secret.sh

IntegrationAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
91
Quality 40%
82
Run on models
none yet
Process rating
F
46/100
Will not run
References files that are not bundled: scripts/run-with-secret.sh
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 5

✓ No critical or high findings

Medium and low: 5
  • low Exfiltration read-dotenv SKILL.md:157
    Reads a .env file (documentation table row; documentation of a security skill)
    | `cat ~/.env` or reading raw env files | Entire env dumped into context |
    tablesecurity skill

A further 4 matches are quotations in this security skill's documentation and are not counted as findings.

Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: scripts/run-with-secret.sh

Process rating: all ten parameters 46/100

Will not run. References files that are not bundled: scripts/run-with-secret.sh
  • 0Tools and files. 1 referenced file(s) missing: scripts/run-with-secret.sh
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 5 mutating operations with no state check
  • 55Failures and branches. 1 branches
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 23 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1760 tokens
  • 100Progress reporting. Reports progress

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 574: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 23 items
  • +4Has examples (8 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.