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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill auditing-wallet-security84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 excels across all dimensions. It provides specific capabilities (token approvals, permissions, transaction patterns), includes explicit 'Use when' and 'Trigger with' clauses with natural user phrases, and occupies a distinct niche in wallet/crypto security that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'analyzing token approvals, permissions, and transaction patterns'. These are distinct, actionable capabilities in the crypto/wallet security domain. | 3 / 3 |
Completeness | Clearly answers both what (audit wallet security by analyzing token approvals, permissions, transaction patterns) AND when (explicit 'Use when...' clause plus 'Trigger with phrases like...' providing concrete activation scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'audit wallet', 'check approvals', 'security scan', 'revoke tokens', 'wallet security', 'reviewing approvals', 'risk exposure'. These are phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche in crypto wallet security with distinct triggers like 'token approvals', 'revoke tokens', 'security scan'. Unlikely to conflict with general document or code skills due to domain-specific terminology. | 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 executable and complete. The progressive disclosure is good with appropriate external references. However, it could be more concise by trimming the verbose output examples and risk level definitions, and would benefit from explicit validation checkpoints in the workflow given this is a security-focused tool.
Suggestions
Add explicit validation checkpoints between steps (e.g., 'Verify scan output shows no errors before generating revoke-list')
Trim the ASCII art output example and risk level definitions - Claude can interpret these from the tool output
Add a feedback loop for handling scan failures or incomplete results before proceeding to recommendations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is mostly efficient with clear command examples, but includes some unnecessary explanation (e.g., detailed score component breakdowns, risk level definitions that Claude could infer). The output format section with ASCII art is verbose. | 2 / 3 |
Actionability | Provides fully executable bash commands with clear options and flags. Every instruction has copy-paste ready examples with specific addresses and chain options. Commands are concrete and complete. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints. For a security audit tool, there should be verification steps (e.g., 'confirm scan completed successfully before proceeding to revoke-list'). No feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | Well-structured with clear overview, then detailed sections. Appropriately references external files (errors.md, examples.md) for comprehensive details. Navigation is clear with one-level-deep references. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.