shield
Security scanner for code, addresses, and transactions
49
37%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/shield/SKILL.mdQuality
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is extremely concise but lacks the actionable content needed to be useful. It reads like a help menu rather than a skill that teaches Claude how to perform security scanning. Critical missing elements include: example outputs, detection patterns, workflow for handling findings, and guidance on what constitutes safe vs unsafe results.
Suggestions
Add concrete examples showing command input and expected output (e.g., what a malicious code scan result looks like vs a clean result)
Include a workflow section for transaction validation: scan -> interpret results -> decision criteria for proceeding or aborting
Add examples of malicious patterns the scanner detects so Claude understands what to look for and explain to users
Reference external files for detailed pattern definitions and chain-specific guidance (e.g., PATTERNS.md, CHAINS.md)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean - just a title, one-line description, and command reference. No unnecessary explanations of what security scanning is or how blockchains work. Every token serves a purpose. | 3 / 3 |
Actionability | Only lists command signatures with brief descriptions. No concrete examples of output, no code showing how scanning works, no sample addresses or code patterns to demonstrate usage. Describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow guidance whatsoever. For security-critical operations like transaction validation, there should be clear sequences (scan -> review results -> proceed/abort) with validation checkpoints. Missing entirely. | 1 / 3 |
Progressive Disclosure | Content is brief and organized with a clear commands section, but lacks any references to detailed documentation for advanced usage, pattern definitions, or chain-specific guidance that would be expected for a multi-chain security tool. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- alsk1992/CloddsBot
- Commit
2a8c94e
- 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.