SKILLEMALL.ai
GitHub ↗ RU Sign in

BC Atlas Finding Report Drafter

Smart contract audit finding report writer — drafts structured, severity-ranked exploit scenarios and audit findings for Solidity/EVM protocols. Takes raw vulnerability notes from triage and produces submission-ready audit write-ups with proof-of-concept narrative, impact analysis, and severity scoring. Use for DeFi audit report writing, Code4Arena finding submission, Sherlock finding write-up, HackenProof report drafting, and severity ranking for audit findings.

ClawHub Agent Skills author: n8gendegen v1.0.0 MIT-0 2 files body ≈ 2 296 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process C 62/100 · Has gaps — weak spots: result and completion, when it triggers, consistency

AnalyzerData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
98
Quality 40%
76
Run on models
none yet
Process rating
C
62/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 2

    ✓ No critical or high findings

    Medium and low: 2
    • low Risky intent intent-offensive-security skill-card.md:14
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Smart contract auditors, bug bounty participants, and security engineers use this skill to turn verified vulnerability notes into submission-ready finding reports for DeFi audits and contest platforms
    • low Risky intent intent-offensive-security SKILL.md:102
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - A bug bounty contest just ended and you have raw notes to convert into findings

    Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
    • note frontmatter-key unknown frontmatter key "slug"
    • note frontmatter-key unknown frontmatter key "homepage"
    • note frontmatter-key unknown frontmatter key "changelog"

    Process rating: all ten parameters 62/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 40Consistency. Frontmatter name (Atlas Finding Report Drafter) differs from the folder (atlas-finding-report-drafter)
    • 55Failures and branches. 1 branches
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 61 steps
    • 100Execution cost. Instruction body is 2296 tokens
    • 100Running it twice. No mutating operations
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 467: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 61 items
    • +4Has examples (6 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.

    External checks

    ClawHub: clean
    This is an instruction-only smart contract audit writing aid with disclosed dual-use exploit-report drafting and no evidence of hidden execution or data access.
    LLM: benign (high) · VirusTotal: · 29 May 2026