Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
Explain content or any concept inside it at the depth the user needs — ELI5, practitioner level, or expert deep-dive — with a jargon glossary and context the original assumes.
Install Explain
$ npx skills add SerhiiKorniienko/bullshit-detector --skill explain -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SerhiiKorniienko/bullshit-detector explain --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/SerhiiKorniienko/bullshit-detector.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/analysis/explain .claude/skills/explain && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "explain" agent skill from https://github.com/SerhiiKorniienko/bullshit-detector/tree/main/skills/analysis/explain into .claude/skills/explain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/SerhiiKorniienko/bullshit-detector/tree/main/skills/analysis/explainType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add SerhiiKorniienko/bullshit-detector --skill explain -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SerhiiKorniienko/bullshit-detector explain --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SerhiiKorniienko/bullshit-detector.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/analysis/explain .agents/skills/explain && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "explain" agent skill from https://github.com/SerhiiKorniienko/bullshit-detector/tree/main/skills/analysis/explain into .agents/skills/explain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SerhiiKorniienko/bullshit-detector --skill explain -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SerhiiKorniienko/bullshit-detector explain --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SerhiiKorniienko/bullshit-detector.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/analysis/explain .cursor/skills/explain && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "explain" agent skill from https://github.com/SerhiiKorniienko/bullshit-detector/tree/main/skills/analysis/explain into .cursor/skills/explain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/SerhiiKorniienko/bullshit-detector.git --path skills/analysis/explain--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add SerhiiKorniienko/bullshit-detector --skill explain -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SerhiiKorniienko/bullshit-detector explain --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SerhiiKorniienko/bullshit-detector.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/analysis/explain .gemini/skills/explain && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "explain" agent skill from https://github.com/SerhiiKorniienko/bullshit-detector/tree/main/skills/analysis/explain into .gemini/skills/explain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install SerhiiKorniienko/bullshit-detector explainInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add SerhiiKorniienko/bullshit-detector --skill explain -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SerhiiKorniienko/bullshit-detector.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/analysis/explain .github/skills/explain && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "explain" agent skill from https://github.com/SerhiiKorniienko/bullshit-detector/tree/main/skills/analysis/explain into .github/skills/explain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SerhiiKorniienko/bullshit-detector --skill explain -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SerhiiKorniienko/bullshit-detector explain --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SerhiiKorniienko/bullshit-detector.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/analysis/explain .opencode/skills/explain && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "explain" agent skill from https://github.com/SerhiiKorniienko/bullshit-detector/tree/main/skills/analysis/explain into .opencode/skills/explain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
explain- GitHub stars
- 154
- Token cost
- ~443 tokens
- SKILL.md length
- 206 words
- Files
- 2
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Explain content or any concept inside it at the depth the user needs — ELI5, practitioner level, or expert deep-dive — with a jargon glossary and context the original assumes.
- Works in 3 steps: Get the text (via fetch-content skill… → Pick the depth — from the user's… → Explain, structured as
- The user says explain this
- SKILL.md covers Workflow and Rules
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Explain is an agent skill from SerhiiKorniienko/bullshit-detector. Explain content or any concept inside it at the depth the user needs — ELI5, practitioner level, or expert deep-dive — with a jargon glossary and context the original assumes. Use when the user says "explain this", "what does X mean here", "break this down", "I don't understand this part", or shares content and asks how something in it works.
Its SKILL.md is about 440 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.
It sits in Research & Science. The repository describes itself as: Agent skills that fact-check the internet: claim-by-claim verification with sources and a 0-10 BS score for any YouTube video, article, tweet, or PDF. The licence is MIT.
When your agent uses it
- The user says explain this
- What does X mean here
- Break this down
- I dont understand this part
Example prompts
- “explain this”
- “what does X mean here”
- “break this down”
- “/explain”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Get the text (via fetch-content skill script if it's a URL, else web fetch or paste).
- Pick the depth — from the user's request, or ask one short question if genuinely unclear
- Explain, structured as
What it can do on your machine
Read from SKILL.md and the folder at commit d5f6156. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Explain loads about 443 tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 206 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from SerhiiKorniienko/bullshit-detector at commit d5f6156, republished under its MIT licence (© SerhiiKorniienko). 206 words, ~443 tokens.
Download SKILL.mdSave it as
.claude/skills/explain/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- explain
- description
- Explain content or any concept inside it at the depth the user needs — ELI5, practitioner level, or expert deep-dive — with a jargon glossary and context the original assumes. Use when the user says "explain this", "what does X mean here", "break this down", "I don't understand this part", or shares content and asks how something in it works.
explain
Make the content understandable without dumbing it down dishonestly.
Workflow
- Get the text (via
fetch-contentskill script if it's a URL, else web fetch or paste). - Pick the depth — from the user's request, or ask one short question if genuinely unclear:
- ELI5 — analogies, zero jargon, the core mechanism only
- Practitioner — assumes general technical literacy, focuses on how it works and what to do with it
- Deep dive — mechanisms, edge cases, history, competing views
- Explain, structured as:
- The one-sentence version first
- The mechanism: how it actually works, step by step
- Glossary: every jargon term the content uses without defining, one line each
- What the content assumes you know — the missing prerequisites that made it confusing
- Where the content's own explanation is wrong or oversimplified, if it is — flag it, don't repeat it
Rules
- Explaining ≠ endorsing. If the content's claim is contested, present the explanation and note the contest ("the video asserts X; the standard view is Y").
- Analogies must survive scrutiny — say where the analogy breaks.
- If the user points at a specific segment ("the part at 12:30", "section 3"), explain that segment in the context of the whole, not in isolation.
- Don't pad: a concept that takes three sentences gets three sentences.
© SerhiiKorniienko, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/analysis/explain of SerhiiKorniienko/bullshit-detector.
- SKILL.md
- VERSION
Open the folder on GitHubat commit d5f6156
Compare with similar skills
Explain next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Explain this skillSerhiiKorniienko/bullshit-detector | 154 | — | ~443 | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
More from SerhiiKorniienko/bullshit-detector
Coverage Check
SerhiiKorniienko/bullshit-detector
Count how many independent origins are behind news coverage of a claim, instead of counting URLs.
Fetch Content
SerhiiKorniienko/bullshit-detector
Fetch and normalize any content source into clean text with metadata — YouTube video transcripts, TikTok captions, web articles, PDFs, tweets/X posts, local files.
Report Card
SerhiiKorniienko/bullshit-detector
Render a finished BS report as a self-contained HTML page — score hero, filterable claims, readable on a phone, prints to a clean PDF.
Share
SerhiiKorniienko/bullshit-detector
Turn a BS report (or any analysis result) into ready-to-paste posts for X/Twitter, LinkedIn, Facebook, Reddit, Hacker News, or a newsletter issue — plus a branded image carousel (PNGs + PDF) for…
Bullshit Detector
SerhiiKorniienko/bullshit-detector
Fact-check and hype-audit content. An agent skill from SerhiiKorniienko/bullshit-detector.
Summarize
SerhiiKorniienko/bullshit-detector
Produce a structured summary of a video, article, tweet thread, or PDF — TLDR, key points with timestamps/locations, notable quotes, and who should read/watch it.
Related
Categories
Questions about Explain
What does Explain do?
Explain content or any concept inside it at the depth the user needs — ELI5, practitioner level, or expert deep-dive — with a jargon glossary and context the original assumes. Explain is an agent skill from SerhiiKorniienko/bullshit-detector. Explain content or any concept inside it at the depth the user needs — ELI5, practitioner level, or expert deep-dive — with a jargon glossary and context the original assumes.
When should I use Explain?
Explain fits situations like: the user says explain this; what does X mean here; break this down; I dont understand this part.
How do I install Explain in Claude Code?
Run `npx skills add SerhiiKorniienko/bullshit-detector --skill explain -a claude-code`. Or copy the skill folder (skills/analysis/explain in SerhiiKorniienko/bullshit-detector) into .claude/skills/explain in your project. Claude Code loads it when a task matches its description.
How do I install Explain in Codex?
Run `npx skills add SerhiiKorniienko/bullshit-detector --skill explain -a codex`. Or copy the skill folder (skills/analysis/explain in SerhiiKorniienko/bullshit-detector) into .agents/skills/explain in your project. Codex loads it when a task matches its description.
Can I use Explain in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SerhiiKorniienko/bullshit-detector --skill explain -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/explain, .gemini/skills/explain, .github/skills/explain and .opencode/skills/explain in your project.
What does Explain need to run?
SKILL.md names no scripts, command-line tools or credentials: Explain is instructions for the agent only.
Does Explain access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Explain safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Explain use?
Explain is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Explain use?
About 443 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Explain?
Skills that share tags, products or a category with Explain: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Explain?
SerhiiKorniienko (a GitHub user) maintains it in SerhiiKorniienko/bullshit-detector, which has 154 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 29, 2026.
Source: SerhiiKorniienko/bullshit-detector on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.