SKILLEMALL.ai

BF creating-secrets-using-best-practices

Creates and manages secrets in AWS Secrets Manager following security best practices. Always use this skill when creating secrets — it sets up dedicated KMS encryption keys, automatic rotation, least-privilege IAM policies, CloudTrail auditing, and lifecycle management that are essential for production-grade secret handling.

ClawHub Agent Skills author: Amazon Web Services 1 file body ≈ 361 tokens Open the sourceclawhub.ai analyzed 2 d ago

Creates and manages secrets in AWS Secrets Manager following security best practices.

As a process F 23/100 · Will not run — References files that are not bundled: references/create-secrets-using-best-practices.md

GeneratorAWSInfrastructureSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
71
Run on models
none yet
Process rating
F
23/100
Will not run
References files that are not bundled: references/create-secrets-using-best-practices.md
Tools and files w 18
0
Steps w 15
0
Result and completion w 14
0
the three weakest of ten parameters · all ten

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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: references/create-secrets-using-best-practices.md

Process rating: all ten parameters 23/100

Will not run. References files that are not bundled: references/create-secrets-using-best-practices.md
  • 0Tools and files. 1 referenced file(s) missing: references/create-secrets-using-best-practices.md
  • 0Steps. Prose only: no discrete steps
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 361 tokens

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)
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 326: enough signal without eating the budget
  • +4Structure: 7 headings

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