From iothackbot
Advanced file finder with type detection and filesystem extraction for analyzing firmware and extracting embedded filesystems. Use when you need to analyze firmware files, identify file types, or extract ext2/3/4 or F2FS filesystems.
How this skill is triggered — by the user, by Claude, or both
Slash command
/iothackbot:ffindThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are helping the user find and analyze files with advanced type detection and optional filesystem extraction capabilities using the ffind tool.
You are helping the user find and analyze files with advanced type detection and optional filesystem extraction capabilities using the ffind tool.
Ffind analyzes files and directories, identifies file types, and can extract filesystems (ext2/3/4, F2FS) for deeper analysis. It's designed for firmware and IoT device analysis.
When the user asks to analyze files, find specific file types, or extract filesystems:
Understand the target:
Execute the analysis:
ffind <path> [<path2> ...]ffind <path> -effind <path> -e -d /path/to/outputffind <path> -affind <path> -vOutput formats:
--format text (default): Human-readable colored output with type summaries--format json: Machine-readable JSON--format quiet: Minimal outputExtraction capabilities:
/tmp/ffind_<timestamp>Analyze a firmware file to see file types:
ffind /path/to/firmware.bin
Extract all filesystems from a firmware image:
sudo ffind /path/to/firmware.bin -e
Analyze multiple files and show all types:
ffind /path/to/file1.bin /path/to/file2.bin -a
Extract to a custom directory:
sudo ffind /path/to/firmware.bin -e -d /tmp/my-extraction
-a flag to see all file types including common formatsnpx claudepluginhub yeyeto2788/iothackbot --plugin iothackbotGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
4plugins reuse this skill
First indexed Jul 13, 2026