explain
100 / 100 · Low risk
Fine to try.
Use when user invokes /explain with a file path, directory path, function/class name, or natural language concept. Also triggers on "explain this", "how does X work", "walk me through". Produces a structured, layered explanation of what the code does, how it connects, and where to start if you need to change it. Do NOT use when the user wants to trace data flow through a pipeline — use /lineage instead.
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'explain' ] || [ -L ~/.agents/skills/'explain' ]; then echo 'A skill folder named explain already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/harnessprotocol/harness-kit' "$d" && git -C "$d" checkout --quiet '4094970dee9a31be7b899126aca1cd4256f57ca8' -- 'plugins/explain/skills/explain' && mkdir -p ~/.agents/skills && cp -R "$d"/'plugins/explain/skills/explain' ~/.agents/skills/'explain' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'explain' ~/.claude/skills/'explain' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/harnessprotocol/harness-kit/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-12 | 4094970 | 100 |
| 2026-11-08 | f09ff57 | 100 |