Explain any concept, codebase, or architecture like reader know nothing about it, as visual HTML artifact — big pictures, few words. Trigger on "/eli5 <topic>", "explain like I'm 5", "ELI5 this".
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add ManceRayder42/jarvis-os --skill eli5 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Eli5?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mancerayder42-eli5)More formats (shields.io, HTML) on the badges page.
---
name: eli5
description: Explain any concept, codebase, or architecture like reader know nothing about it, as visual HTML artifact — big pictures, few words. Trigger on "/eli5 <topic>", "explain like I'm 5", "ELI5 this".
---
# ELI5 visual explainer
Anthropic internal pattern (Thariq, product lead, via [@trq212](https://x.com/trq212/status/2090884854590382515)). Source write-up: https://leslieli.dev/notes/anthropic-eli5-skill-html-artifacts/
Original prompt: *"Explain like I'm someone who knows nothing about this topic, using an HTML artifact with big pictures and few words."*
## Steps
1. Assume reader new to topic — no jargon without one-line definition.
2. Load `artifact-design` skill before writing (mandatory in this environment for any HTML artifact).
3. Build ONE self-contained HTML page: diagram or visual sequence first, minimal text. Add interactive control only when it reveals a state change or relationship — never as decoration.
4. Label assumptions plainly. A simplified diagram is illustration, not proof.
5. Publish via Artifact tool — title = topic name, favicon required.
Keep adaptation short. Source contributes the format constraint (big pictures, few words), not a house style or claim interaction always helps.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
