CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

crypto-audit

Audit cryptography implementation — algorithm choice, key sizes, KDF parameters, IV/nonce handling, signature verification, randomness, TLS configuration, and key rotation. Deeper than owasp-audit A04. Use when the user mentions 'crypto review,' 'cryptography audit,' 'encryption review,' 'KDF,' 'PBKDF2,' 'Argon2,' 'bcrypt cost,' 'IV reuse,' 'nonce reuse,' 'AES mode,' 'AES-GCM,' 'AES-ECB,' 'signature verification,' 'TLS configuration,' 'cipher suites,' 'key rotation,' 'libsodium,' 'BoringSSL,' or 'is this crypto right.'

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An excellent, high-density audit skill: every section carries specific, non-obvious domain guidance with executable commands and grep patterns, a clearly sequenced verify-then-record workflow with explicit validation gates, and a clean one-level-deep reference structure backed by real bundle files. The only room for improvement is trimming minor rhetorical and redundant passages to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious domain facts (exact OWASP parameter floors, per-language library footguns like 'Cipher.getInstance("AES")' defaulting to ECB) and avoids explaining concepts Claude already knows, but contains minor trimmable material: the second intro paragraph partly overlaps the first, the rhetorical 'There are < 50 people on Earth' line, and a long output template. Not 5 because of these minor padding instances; not 3 because nearly every line carries a specific, actionable fact.

4 / 5

Actionability

Guidance is copy-paste ready throughout: per-section grep patterns ('AES.*ECB', 'pbkdf2_hmac (check iterations arg)'), executable commands ('testssl.sh --jsonfile', 'aws kms get-key-policy --key-id <id> --policy-name default', 'node references/validate-findings.mjs findings.json'), concrete vulnerable-code examples, and specific parameter floors (PBKDF2 ≥ 600,000 iterations, scrypt N=2^17, bcrypt cost ≥ 12, 128-bit token entropy).

5 / 5

Workflow Clarity

The multi-step process is explicitly sequenced with validation checkpoints: audit checklist → refutation pass ('Before anything is confirmed, run the refutation pass') → verdict classification (confirmed/needs_validation/rejected/hardening) → write and validate findings.json → render report, with a runtime fix-verification section covering round-trip testing and migration. Feedback loops are explicit and the destructive/batch-sensitive audit output is schema-validated.

5 / 5

Progressive Disclosure

SKILL.md serves as the operational overview while detail lives one level deep in references/ — findings format, verification refutation pass, severity calibration, validator, SARIF exporter, and schema — each well-signaled with purpose ('run the refutation pass in [references/verification.md]', 'Rate severity with [references/severity-calibration.md]') and all six referenced files verified to exist as real, substantive content in the bundle.

5 / 5

Total

19

/

20

Passed

Description

96%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 description: comprehensive concrete capability list paired with an extensive, natural-sounding trigger vocabulary and an explicit use-when clause. The only weakness is mild trigger overlap with the sibling owasp-audit skill on TLS-related terms, partially mitigated by the explicit 'Deeper than owasp-audit A04' positioning.

DimensionReasoningScore

Specificity

The description enumerates concrete audit actions — 'algorithm choice, key sizes, KDF parameters, IV/nonce handling, signature verification, randomness, TLS configuration, and key rotation' — covering the crypto-implementation-audit domain comprehensively with no gaps in scope.

5 / 5

Completeness

Both questions are answered explicitly: the 'what' is the enumerated audit scope and the 'when' is 'Use when the user mentions' followed by concrete trigger phrases — a direct match for the anchor-5 example pattern.

5 / 5

Trigger Term Quality

The 'Use when' clause lists 19 natural trigger phrases spanning synonyms ('crypto review,' 'cryptography audit,' 'encryption review'), parameter-level terms ('PBKDF2,' 'Argon2,' 'bcrypt cost,' 'IV reuse'), library names ('libsodium,' 'BoringSSL'), and a colloquial user phrase ('is this crypto right').

5 / 5

Distinctiveness Conflict Risk

The skill has a clear niche, explicitly differentiated as 'Deeper than owasp-audit A04,' but trigger terms like 'TLS configuration' and 'cipher suites' overlap with closely related sibling audit skills (owasp-audit A04, secrets-audit), leaving minor conflict risk. Not 5 because the overlap with the referenced sibling skills is acknowledged rather than eliminated; not 3 because the boundary statement and parameter-specific triggers (Argon2, nonce reuse) keep it mostly distinct.

4 / 5

Total

19

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

briiirussell/cybersecurity-skills

Path

skills/crypto-audit/SKILL.md

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.