CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-security

Use when storing credentials securely, encrypting data, implementing passkeys, securing AI/agentic features against prompt injection, code signing, or managing certificates and provisioning profiles.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude-plugin/plugins/axiom/skills/axiom-security/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

A well-architected router skill with excellent progressive disclosure and conflict-resolution guidance, but it is held back by significant routing redundancy and the absence of any in-body executable examples. Consolidating the repeated routing representations would materially improve token efficiency.

Suggestions

Collapse the four redundant routing views (Quick Reference table, dot Decision Tree, numbered list, Example Invocations) into one canonical table plus the decision tree, removing the duplicate numbered list and example invocations.

Prune the Critical Patterns section so it does not re-enumerate every referenced file already named in the Quick Reference; keep only the patterns that add information beyond the file list.

Add at least one tiny in-body executable snippet per common task (e.g. a minimal SecItemAdd keychain write or an AES-GCM seal call) so the skill is actionable without forcing a file read for trivial cases.

DimensionReasoningScore

Conciseness

The body is mostly efficient and does not explain concepts Claude already knows, but it restates the same routing four ways — Quick Reference table, dot Decision Tree, numbered list, and Example Invocations — plus a Critical Patterns section that re-lists the same files, so it could be tightened considerably.

2 / 3

Actionability

Routing is concrete and points to specific files (e.g. 'Read: skills/keychain.md'), but the body contains no executable code or commands itself; the actual instructions live in the referenced files, so guidance is specific yet not copy-paste ready.

2 / 3

Workflow Clarity

A clear sequence exists via the Decision Tree and numbered list for choosing a sub-skill, but the redundant representations can muddy rather than clarify routing, and there are no validation checkpoints (none are required for pure routing).

2 / 3

Progressive Disclosure

The SKILL.md is a clean overview pointing to well-signaled, one-level-deep references (skills/*.md) organized through a table, decision tree, and pattern summaries, with no nested 'see X which says see Y' chains.

3 / 3

Total

9

/

12

Passed

Description

100%

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

A strong, third-person description with an explicit Use-when trigger and a broad list of concrete security actions. It clearly communicates both capability and invocation conditions with minimal overlap risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'storing credentials securely, encrypting data, implementing passkeys, securing AI/agentic features against prompt injection, code signing, or managing certificates and provisioning profiles' — matching the anchor for several specific concrete actions.

3 / 3

Completeness

An explicit 'Use when' clause supplies the trigger while the verb list supplies the what, answering both what the skill does and when Claude should use it.

3 / 3

Trigger Term Quality

Uses natural terms a user would actually say — 'storing credentials', 'encrypting data', 'passkeys', 'prompt injection', 'code signing', 'certificates', 'provisioning profiles' — with good coverage and no jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

The security/credentials niche is well-scoped with distinct triggers (passkeys, prompt injection, provisioning profiles) unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
CharlesWiltgen/Axiom
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.