explainer
Skill1 starsChanged 36 days agoMITView on GitHub
Build a bespoke explainer as an interactive HTML page, a narrated 3Blue1Brown-style video, or an ASD-STE100 technical description page. Invocation-only. Use for /explainer, $explainer, or an explicit request to use the explainer skill. Not for quick inline charts, ELI5 chat answers, product demo videos, or /explain lessons.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- AJschoons/robowrighttheir own version, first seen Nov 8, 2026
- akachandan1/video-studiotheir own version, first seen Nov 8, 2026
- alandaitch/explainer-skilltheir own version, first seen Nov 8, 2026
- overment/skillstheir own version, first seen Nov 8, 2026
- agentic-community/mcp-gateway-registrytheir own version, first seen Nov 6, 2026
- artemnovitckii/claude-editing-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use ugc-ads.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AdviblySkillugc-ads
Generate complete multi-shot UGC video ads end to end with the Advibly MCP tools. Takes a brand plus an ad angle and produces a realistic AI creator image (gpt-image-2), a 5-shot direct response script, a user-approved storyboard of start frames, and one video clip per shot animated from its frame (Gemini Omni Flash with native spoken dialogue), then assembles the clips into a finished vertical ad. Use whenever the user wants a UGC ad, a creator-style video ad, a product-in-hand testimonial video, or asks to turn a product into a TikTok/Reels-style ad. Also trigger on phrases like "UGC video," "creator ad," "testimonial ad," or "make an ad for my product" when the Advibly MCP is connected.
Also in 3 projects that use this
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- agentic-community/mcp-gateway-registry★ 1ksame name
- marswaveai/skills★ 82same name
- Pika-Labs/Pika-Plugins★ 40same name
- codetesla51/skills★ 32same name
- overment/skills★ 31same name
- artemnovitckii/claude-editing-skills★ 12same name
- alandaitch/explainer-skill★ 8same name
- akachandan1/video-studio★ 2same name
- barisgit/explainer-skill★ 2same name
- ofoxai/skills★ 2same name
10 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- 60-30-10Skill
- buildSkill
- explainSkill
- icm-architectSkill
- karpathy-guidelinesSkill
- skill-tuneSkill
- swarmSkill
- weekly-signal-diff-aiSkill
- write-discoverable-codeSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Ask every time, before any research or drafting, even when the request names a format.
- Very specific: line 31
Read references/writing.md before writing narration or page text.
- Distinctive: line 39
Never call output STE compliant, certified, or ASD approved.
- Distinctive: line 40
When the execution target is a RemoteBox, the website deploy tool is unavailable there (seen 2026-10-12).
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Explainer
Build a large, custom, discardable artifact whose only job is to make one topic understood.
Pick the mode
Ask every time, before any research or drafting, even when the request names a format. Use one single-select question with Web page, Video, and Technical description as the options, then wait for the answer. If the request names a format, list that option first.
- Web page. Named by "in HTML", "web page", or "interactive". Read
references/web.md. - Video. Named by "video", "3b1b", "animated video", or "narrated". Read
references/video.md. - Technical description. Named by "STE", "ASD-STE100", "Simplified Technical English", "technical description", or "description and operation". Read
references/technical.md.
Rules for all modes
- Pin the one sentence the viewer should leave with and the audience level. Infer both from the request. Ask only when the audience would change the content.
- Establish the facts before drafting. Use supplied material first. Verify facts that change over time. Separate facts, interpretations, unknowns, and examples. Cite as the mode file says. Video narration cannot carry links, so list its sources in the handoff.
- Label illustrative data as illustrative.
- Order the ideas: a question or puzzle, one concrete example, the mechanism, the general rule, a one-line recap. Technical description uses the section order in
references/technical.mdinstead. - Show, then say. Every beat has one visual that carries the idea. Text and narration support the visual, not the reverse. Technical description uses the figure count in
references/technical.mdinstead. - Read
references/writing.mdbefore writing narration or page text. Define each term on first use. Technical description applies the full standard inreferences/technical.mdinstead. - Draw diagrams, labels, and equations with code. Never use image or video generation for them, because generated media cannot render exact labels.
- Use the shared dark theme.
templates/page.htmlandtemplates/explainer_scene.pyhold the same dark palette, role colors, and PPLX type fromassets/fonts/. The page adds a light variant behind a toggle. After editing either file, runpython scripts/test_theme_parity.pyfrom this skill directory. Technical description takes its theme fromtemplates/page.htmlwhenscripts/build_technical.pyruns.
Deliver
- Report the actual result of the mode's Check list and its limits. Never infer browser verification from code inspection.
- List any claim you could not verify.
- Never call output STE compliant, certified, or ASD approved. In Technical description mode, say that a script examined the page and that ASD did not.
- When the execution target is a RemoteBox, the website deploy tool is unavailable there (seen 2026-10-12). Copy the built page to the Cloud sandbox with the file-copy tool, switch to Cloud, deploy, then switch back.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.