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.

71

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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: lean, scannable, and exemplary in progressive disclosure with precise one-level-deep references. The main cost is triple-redundant routing presentation (table + dot graph + numbered list) that inflates tokens without adding decision power.

Suggestions

Collapse the dot decision graph and the numbered Decision Tree list into a single routing representation to remove the main token redundancy.

The Anti-Rationalization table is the most padded section; trim entries that restate widely-known facts (e.g. UserDefaults being a plist) and keep only the non-obvious guardrails.

DimensionReasoningScore

Conciseness

The body is lean and scannable with terse tables and bullets that never explain concepts Claude already knows, but the routing information is repeated three times — Quick Reference table, dot decision graph, and numbered list — which is trimmable redundancy.

4 / 5

Actionability

As a router skill it gives maximally concrete guidance — exact file paths (skills/keychain.md), specific error codes (errSecDuplicateItem, ITMS-90xxx), and named APIs — so the routing action is unambiguous and immediately executable.

5 / 5

Workflow Clarity

The numbered Decision Tree (1, 1a, 1b, 2, 2a...) sequences routing clearly and the Conflict Resolution section disambiguates sibling-skill overlaps with explicit error-message rules, but there are no true validation checkpoints because routing is not a destructive operation.

4 / 5

Progressive Disclosure

Exemplary one-level-deep structure: SKILL.md is a pure overview pointing to ~13 well-signaled skills/*.md references via the Quick Reference table, with only terse per-file bullet summaries inlined rather than monolithic reference material.

5 / 5

Total

18

/

20

Passed

Description

88%Weight 40%Scale 1-5

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, trigger-first description that covers a comprehensive set of concrete security actions with an explicit "Use when" clause. It is held back from a perfect mark only by missing common synonyms and minor overlap risk with sibling suite skills.

Suggestions

Add high-frequency synonyms users say aloud — keychain, passwords, API keys, tokens, WebAuthn — so the trigger matches more natural phrasings.

Consider narrowing or explicitly bounding the AI-security scope (e.g. "securing AI agents against prompt injection") to reduce overlap with general agentic or networking skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the security domain — "storing credentials securely, encrypting data, implementing passkeys, securing AI/agentic features against prompt injection, code signing, or managing certificates and provisioning profiles" — giving comprehensive coverage rather than a single vague domain.

5 / 5

Completeness

Explicitly answers both what (the security actions listed) and when via a leading "Use when" clause with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Strong natural terms (credentials, passkeys, prompt injection, code signing, certificates, provisioning profiles) that users would actually say, but common synonyms like keychain, passwords, API keys, tokens, or WebAuthn are absent.

4 / 5

Distinctiveness Conflict Risk

The security-and-credentials niche is clearly delineated with distinct triggers, but the breadth (keychain, crypto, signing, AI security) creates real overlap with adjacent build/data/networking skills — the body itself contains conflict-resolution sections acknowledging this.

4 / 5

Total

18

/

20

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.