← ClaudeAtlas

recat-findingslisted

Use when bug hunting, reviewing web, smart contract, or other security vulnerabilities, preparing PoC reports, or saving and updating findings for Recat. Applies to authorized security findings and their reporting artifacts.
0xtbug/Recat · ★ 12 · Data & Documents · score 77
Install: claude install-skill 0xtbug/Recat
# Recat findings Save the results of completed bug hunting work to the Recat platform. Apply this workflow when the user requests authorized bug hunting, vulnerability review, PoC reporting, or saving/updating findings. For unrelated tasks, follow the user's task without creating findings. Active source folder: finding/source ## Source configuration Before writing findings, resolve the active source folder to the same directory configured in Recat Settings. An absolute path from the downloaded skill can be used directly on the same machine. A relative path such as finding/source is relative to the Recat project root, one level above its web repository, not to the agent workspace or installed skill. If that root is unknown, ask the user for the absolute source folder first. Do not silently create a different output directory. When installing the repository's skills/SKILL.md, update the Active source folder line to the configured absolute path. No Recat login password or HTTP API call is needed to save files. ## Finding folders Use the active source folder on the same filesystem as the Recat server. Automatically create <project>/bug/<name_poc>/ for each finding and save finding.json inside it. A hostname such as examplemy.com stays the project folder name; for smart contracts use the project or protocol name provided by the user. Use a filesystem-safe name for other project names and a descriptive, filesystem-safe slug for name_poc. Folder names are single path component