How it behaves
forkprobe treats skill selection as a comparison run. It recommends a small candidate set, runs baseline and the selected skills with identical input, and writes a local HTML report. Depending on the task, the report can include text, previews, source files, QA results, media metadata, estimated token use, elapsed time and AI review comments. The documented workflow ends with a user-selected winner and a continuation handoff.
In DSH, the native forkprobe_compare tool starts candidate subagents in parallel. The README states that this native implementation does not launch a second dsh process or copy DSH credentials. It also retains installation confirmation, local Skill scanning, candidate de-duplication and optional anonymous winner sharing.
Commands
The README shows a direct comparison command:
python3 scripts/compare.py --input /tmp/forkprobe-input.txt --skill baseline --skill writing-anti-ai --skill humanizer-zh --skill remove-ai-flavor-writing-skill --judge --output /tmp/forkprobe-report.html
--input takes an input file, --skill can be supplied for each candidate, --judge enables the documented AI review step, and --output specifies the report path. The DSH-native tool is named forkprobe_compare; its full argument schema is not included in the supplied README.
Candidate sources and outputs
Candidates may be recommended from the curated directory, locally installed Skills, EverMind Skill Hub, GitHub or a BYO path. The documented report types include text outputs, PPTX files, PNG/SVG/PDF/TIFF figure assets, research evidence files, runnable web pages, screenshots, MP4 media, subtitles, transcripts and source code, depending on the comparison mode.
Known limits
Image-generation comparison is listed as planned rather than supported. For external GitHub candidates, the README recommends checking licence, dependencies and final output paths before execution. Simple deterministic tasks are explicitly outside the intended use case.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub