CtrlK
BlogDocsLog inGet started
Tessl Logo

crypto-decode

Cipher detection + automated decryption via Ciphey, Cyberchef recipes, hashcat hash-ID, format conversion, common encoding chains.

62

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/exploit/crypto/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The content is a dense, actionable, token-efficient playbook with concrete commands and clear sectioning. Its weak spots are the absence of explicit validation checkpoints in the unfolding workflow and a monolithic structure with no progressive disclosure into reference files.

Suggestions

Add an explicit verify/validate step to the token-unfolding workflow (e.g., "Confirm plaintext is human-readable before stopping; else repeat from step 1") to lift workflow clarity to 3.

Move the hashcat mode table and CyberChef recipe chains into a references/ file (e.g. HASHMODES.md) referenced from SKILL.md to enable progressive disclosure.

Clarify the decepticon MCP skeleton's completion expectations or mark which fields are illustrative vs. required.

DimensionReasoningScore

Conciseness

The body is a lean reference card of commands, tables, and signatures with no padding or explanation of concepts Claude already knows; nearly every line earns its place.

3 / 3

Actionability

It supplies copy-paste-ready commands (ciphey/ares, hashid, base64/hex transforms, hashcat -m modes) and concrete recipes; the only non-complete snippet is explicitly labeled a "skeleton".

3 / 3

Workflow Clarity

Section 5 gives a numbered unfolding workflow with conditional branches, but it lacks explicit validation/verification checkpoints, so the sequence is present yet checkpoints are only implicit.

2 / 3

Progressive Disclosure

Content is well-sectioned but monolithic — all ~150 lines live inline in SKILL.md with no reference files (none exist in references/scripts/assets), and tables like the hashcat mode list could be split out.

2 / 3

Total

10

/

12

Passed

Description

67%

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 specific and distinct, naming concrete actions and tools, but it omits an explicit "Use when..." trigger clause and relies on tool names over natural user keywords. Trigger guidance lives in metadata.when_to_use rather than the description itself.

Suggestions

Add an explicit "Use when..." clause to the description (e.g., "Use when decoding unknown ciphertext, identifying ciphers/encodings, or reversing base64/hex/Caesar/XOR layers") so completeness can reach 3.

Replace some tool-name emphasis with natural user keywords ("decode", "decrypt", "base64", "hex", "ROT") to improve trigger-term quality.

Confirm the description alone — without metadata.when_to_use — conveys when to invoke the skill, since judges score only the description field.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Cipher detection", "automated decryption", "Cyberchef recipes", "hashcat hash-ID", "format conversion", "common encoding chains" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

It clearly states what the skill does, but lacks any "Use when..." or equivalent explicit trigger clause, so per the guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Relevant terms like "cipher", "decryption", "encoding" appear, but the field leans on tool names (Ciphey, Cyberchef, hashcat) and omits common natural variations ("decode", "base64", "hex") that users would actually say.

2 / 3

Distinctiveness Conflict Risk

The named-tool cryptanalysis/decoding niche (Ciphey, Cyberchef, hashcat) is a clear, distinct scope unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PurpleAILAB/Decepticon
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.