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".
87
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is a well-crafted skill description that hits all the key criteria. It provides specific capabilities, explicit trigger guidance with natural user phrases, and a clear 'Use when' clause. The domain is distinct enough to avoid conflicts with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'analyzing token approvals, permissions, and transaction patterns' clearly describes what the skill does with distinct, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (audit wallet security by analyzing token approvals, permissions, and transaction patterns) and 'when' (explicit 'Use when...' clause plus a 'Trigger with phrases like...' clause providing concrete trigger guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'audit wallet', 'check approvals', 'security scan', 'revoke tokens', 'wallet security', 'reviewing approvals', 'risk exposure' — these are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around wallet security auditing, token approvals, and revocation — highly specific to blockchain/crypto wallet security and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability—every command is concrete and executable with real examples. The main weaknesses are moderate verbosity (the ASCII output mockup, numbered lists for score breakdowns, and some explanatory text could be trimmed) and the lack of explicit validation/feedback loops in the workflow for what is essentially a security-sensitive audit process.
Suggestions
Trim the ASCII art output example and score component breakdowns—Claude can interpret JSON output descriptions without visual mockups
Add a validation workflow: e.g., after running a scan, verify findings by cross-referencing with revoke-list before recommending actions
Remove the prerequisites explanation of hex format and what Python/requests are—Claude already knows these
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary sections like the ASCII art output example, verbose numbered lists for score components and risk levels, and the overview paragraph explaining what a security analysis tool does. The prerequisites section explaining what Python and hex format are is slightly patronizing for Claude. | 2 / 3 |
Actionability | Every command is fully executable with concrete CLI syntax, real example addresses, specific flags, and copy-paste ready bash commands. The skill provides clear, specific commands for each operation with all necessary arguments. | 3 / 3 |
Workflow Clarity | Steps are clearly listed and sequenced (approvals → scan → score → history → revoke-list → report), but there are no validation checkpoints or feedback loops. For a security audit tool, there should be explicit guidance on what to do when the scan reveals issues—e.g., verify findings before acting on revoke recommendations. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled references to external files (errors.md, examples.md) that are one level deep. Content is appropriately split between the main skill file and reference documents, with inline quick examples for immediate use. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
c8a915c
- 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.