CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-infra-secrets

This skill should be used when the user says "manage secrets", "arn infra secrets", "infra secrets", "secrets management", "set up secrets", "configure secrets", "audit secrets", "secrets audit", "rotate secrets", "secret storage", "vault setup", "key management", "credential management", "secrets scan", "check for exposed secrets", "secrets provider", "arn-infra-secrets", "set up secret manager", "configure secret injection", "environment variables", "env vars", "secure env vars", or wants to set up, configure, audit, or manage secrets and credential storage for their infrastructure deployment.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a clear, well-validated workflow and good progressive disclosure into reference files. The main improvement is removing the thrice-repeated beginner/expert instruction to improve token efficiency.

Suggestions

State the beginner/expert guidance once (e.g., in a shared "Audience adaptation" note) instead of repeating it verbatim in Steps 3, 4, and 5.

Consolidate the cross-skill reference paths (experience-derivation.md, ensure-config.md) into a single Prerequisites note to reduce scattered plugin-path citations.

DimensionReasoningScore

Conciseness

The body is mostly lean and delegates bulky comparison tables to references, but the line "For beginners, simplify guidance… For experts, show all available options with configuration details" is repeated verbatim across Steps 3, 4, and 5 and could be stated once.

2 / 3

Actionability

It gives concrete executable guidance: specific IaC snippets (e.g., `data "aws_secretsmanager_secret_version"`), exact commands (`fly secrets set KEY=value`, `doppler run -- node server.js`), grep patterns, AskUserQuestion usage, and copy-ready message templates.

3 / 3

Workflow Clarity

Six clearly sequenced steps include explicit validation/confirmation checkpoints ("Wait for user confirmation before executing", "Present… for user approval before applying"), a Pass/Fail/N/A audit step, and a thorough Error Handling section with fallbacks.

3 / 3

Progressive Disclosure

Detailed material is appropriately split into one-level-deep references (`references/secrets-providers.md`, `references/secrets-audit-checklist.md`), both clearly signaled with read directives, keeping the SKILL.md an overview.

3 / 3

Total

11

/

12

Passed

Description

92%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong, with explicit use-when triggers and concrete domain actions, plus excellent natural keyword coverage. Its only weakness is a few overly generic env-var trigger terms that risk overlapping with unrelated skills.

Suggestions

Tighten or qualify the generic "environment variables" / "env vars" / "secure env vars" triggers (e.g., "manage secret environment variables") to reduce overlap with general env-config skills.

Consider trimming the longest raw trigger list slightly in favor of a concise capability sentence to improve signal-to-noise without losing coverage.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — "set up, configure, audit, or manage secrets and credential storage for their infrastructure deployment" — naming several specific operations within the domain rather than vague abstractions.

3 / 3

Completeness

It answers both what (set up/configure/audit/manage secrets and credential storage) and when (an explicit "This skill should be used when the user says…" clause with a long trigger list).

3 / 3

Trigger Term Quality

It provides broad, natural coverage of phrases users would actually say ("manage secrets", "secrets audit", "rotate secrets", "vault setup", "key management", "env vars"), with many common variations.

3 / 3

Distinctiveness Conflict Risk

The secrets niche is clear and mostly distinct (e.g., "arn-infra-secrets", "secrets audit"), but generic triggers like "environment variables", "env vars", and "secure env vars" could plausibly overlap with non-secrets skills.

2 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
AppsVortex/arness
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.