القائمة
Explain any topic in the simplest possible terms using analogies and everyday examples. Use when the user says "explain like I'm 5", "eli5", "explain simply", "dumb it down", or "explain in simple terms".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Safely add a directory to Claude Code's Bash tool PATH. Use when a binary runs in your terminal but is "command not found" inside Claude Code's Bash tool, when adding a directory to PATH for Claude Code, when configuring CLAUDE_ENV_FILE, or when settings.json env.PATH did not work. Explains why env.PATH replaces rather than appends PATH and is not variable-expanded, why ~/.zshrc PATH exports are dropped, and the supported SessionStart hook fix.
Create or improve a Claude Code skill/slash command with best practices for structure, dynamic context, and safety. Use for creating new skills, improving existing ones, or learning skill authoring.
Launch a dynamic Workflow where the top-tier session model (Fable, or Opus when Fable is unavailable) handles planning and orchestration while implementation subagents run on Sonnet for routine tasks and Opus for complex ones. Use when the user wants to orchestrate a build, a dynamic workflow, a model-tiered build, fable or opus planning with sonnet and opus implementation, or tiered agents.
Open a PR, wait for CI to pass, fix failures, address review comments, and loop until fully green. Use when opening a PR, fixing CI, or addressing review feedback.
Manage recurring tasks in the local Argus daemon via its HTTP API. Use when the user wants to schedule a task locally in argus, create a cron-driven task, fire X every weekday/hour/morning, set up a recurring agent that needs local filesystem access (logs in ~/.argus, local databases, dotfiles), list or update existing argus schedules, or run an argus schedule now. Distinct from /schedule, which creates remote cloud routines without local access.
Generate a handoff prompt to pass context to another agent thread. Use when switching repos, handing off work, or sharing context between agents.
| name | eli5 |
| description | Explain any topic in the simplest possible terms using analogies and everyday examples. Use when the user says "explain like I'm 5", "eli5", "explain simply", "dumb it down", or "explain in simple terms". |
Break down a topic so a 5-year-old could understand it.
$ARGUMENTS - The topic, concept, code, error message, or architecture decision to explainRead $ARGUMENTS. If empty, ask the user what they want explained and stop.
The topic can be anything:
If the topic references a file or code, read it before explaining.
Structure your explanation in this order:
Core idea first. State what it is in one plain sentence. No jargon, no acronyms unless you define them immediately. This is the "headline" -- if the reader stops here, they still learned something.
Analogy. Connect the concept to something from everyday life -- toys, food, playgrounds, animals, building blocks, a library, a kitchen. Pick an analogy that maps well to the actual mechanics, not just the surface.
Diagram (when visual). If the concept has structure, flow, or relationships, include a short ASCII diagram. Keep it under 10 lines. Skip this for purely abstract concepts where a diagram would not help.
Example. Walk through one concrete, minimal example. For code concepts, show 3-5 lines of real code with a one-line comment. For non-code topics, give a specific scenario.
Plain-English summary. One sentence a child could repeat back. Connect the analogy to the real thing: "So [analogy] is like [real thing] because..."
Rules:
After the explanation, offer: "Want me to go deeper on any part of this, or see more examples?"