auditing-wallet-security

Audit wallet security by analyzing token approvals, permissions, and transaction patterns. Use when checking wallet security, reviewing approvals, or assessing risk exposure. Trigger with phrases like "audit wallet", "check approvals", "security scan", or "revoke tokens".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

Highly actionable with concrete, copy-paste-ready commands, but the body leans slightly verbose and presents a command menu rather than a guided, sequenced workflow with checkpoints. Progressive disclosure is good but undermined by an unreferenced, off-topic reference file.

Suggestions

Condense or move the decorative ASCII-art sample output block to references/examples.md so the main body stays lean.

Add a short sequenced workflow (e.g., approvals -> scan -> score -> report) with a verification/sanity-check step so the numbered sections form a guided audit process rather than a command menu.

Remove or repurpose references/implementation.md so every bundled file is referenced from the body and stays on-topic for wallet security.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and executable without explaining basics, but the large decorative ASCII-art sample output block (lines 138-150) and the cross-section running numbered list (e.g., '4. Active token approvals' through '23. Stale approvals') add padding that could be tightened; not quite the lean level-3 anchor.	2 / 3
Actionability	Provides fully executable commands with concrete flags (--chain, --verbose, --json, --output), real example addresses, and copy-paste-ready snippets matching the level-3 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	Commands are organized into numbered sections, but it reads as a command menu rather than a sequenced audit workflow with no guidance on ordering scan/score/report and no validation checkpoint; this is below the explicit-checkpoint level-3 anchor and the cross-section numbering is disorienting.	2 / 3
Progressive Disclosure	Overview points clearly to one-level-deep real files (references/errors.md, references/examples.md), but references/implementation.md is unreferenced from the body and is off-topic (general crypto data analysis rather than wallet security), leaving organization incomplete versus the level-3 'appropriately split, easy navigation' anchor.	2 / 3
	Total	9 / 12 Passed

Description

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

A strong, concise description that clearly states capabilities, explicit use-when triggers, and natural trigger phrases. It distinguishes the skill well and answers both what and when.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'analyzing token approvals, permissions, and transaction patterns', matching the level-3 anchor rather than the single-action level-2 example.	3 / 3
Completeness	Explicitly answers both what ('Audit wallet security by analyzing token approvals, permissions, and transaction patterns') and when ('Use when checking wallet security, reviewing approvals, or assessing risk exposure'), satisfying the level-3 'what AND when' anchor.	3 / 3
Trigger Term Quality	Provides natural phrases users would say ('audit wallet', 'check approvals', 'security scan', 'revoke tokens') plus situational triggers, giving good coverage rather than partial level-2 terms.	3 / 3
Distinctiveness Conflict Risk	The crypto-wallet-approvals niche with distinct triggers ('audit wallet', 'revoke tokens') is unlikely to conflict with other skills, matching the clear-niche level-3 anchor.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/crypto/wallet-security-auditor/skills/auditing-wallet-security/SKILL.md
Commit: 4c47e33

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.