Track and update action item status from natural language updates like 'Seanのメールには返信しておいた' or 'Lu対応予定'. Integrates with daily-comms-ops workflow. Use when managing action items across communication channels.
eli5
Explain a topic like I'm a 5 year old, as a single HTML artifact built from big pictures and very few words. Use this whenever the user asks for a dead-simple explanation of how something works, says "ELI5", "explain like I'm five", "簡単に説明して", "図で説明して", "初心者向けに", "素人にもわかるように", wants to explain a concept to a non-technical manager, customer, or family member, or asks for a visual explainer — even if they don't say "ELI5" explicitly.
含まれるファイル(1)
- SKILL.md3.1 KB
SKILL.md(原文)
インストールする前に、エージェントに与えられる指示の中身を確認できます。
eli5
Explain the topic like I'm someone who knows nothing about it, using a single HTML artifact with big pictures and few words.
The topic is whatever the user asked to have explained. If they named an audience (a manager, a customer, a parent, a five-year-old), keep that person in mind while choosing analogies and vocabulary.
When to Use
- The user says "ELI5", "explain like I'm five", 「簡単に説明して」, 「図で説明して」, 「初心者向けに」, or 「素人にもわかるように」.
- They need to explain something technical to a non-technical manager, customer, or family member.
- They ask for a visual explainer, a picture-led walkthrough, or a one-pager a newcomer can follow.
- An earlier explanation did not land and they ask for a simpler version.
- Assumed background knowledge is what stands between the reader and the idea — even if they never say "ELI5".
Not this skill: a precise technical specification, an architecture document, or a slide deck for an audience that already knows the domain.
Why this shape
The name says "5 year old", but the real goal is to strip out assumed background knowledge, not to talk like a child. Aiming at a literal five-year-old's vocabulary tends to make the explanation inaccurate. Aiming at "a smart adult who has never heard of this" keeps it both simple and true.
Big visuals with little text work because the reader is meeting the idea for the first time. A diagram shows the shape of the thing at a glance; a wall of text makes them reconstruct that shape in their head. So let the pictures carry the explanation and use words only to label and connect them.
What to produce
One self-contained HTML artifact. Inline all CSS and SVG so it renders anywhere; do not load external scripts, stylesheets, or images.
- Open with the one-sentence version of the idea, large.
- Then walk through it in a few big panels, each with one picture and one or two short lines. Simple SVG shapes, arrows, and labels are enough; a good analogy drawn as a picture beats a precise technical diagram here.
- Prefer one concrete example over a general definition.
- End with a single "so what" line: why the reader might care.
- Keep the total text short enough to read in about a minute. If you find yourself writing paragraphs, turn them into a picture instead.
Write in the language the user is using. If the audience they named reads a different language, use that one.
Adapted from the MIT-licensed eli5 plugin by Thariq Shihipar.
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
AI活用提案の専門コンサルタントスキル。LLM・AIエージェントの活用事例知識を基に、業界別、部門別、シーン別に最適なAI導入提案を行います。システム化、業務改善、効率化を得意とし、具体的な活用事例、期待効果、導入ステップを含む実践的な提案を提供します。Use when proposing AI/LLM adoption strategies for specific industries, departments, or business scenarios.
Generate AI-powered BPO service proposals for Japanese companies in the US market. Use when creating outsourcing proposals with AI service menus, ROI estimation, implementation roadmaps, and bilingual (JA/EN) proposal documents for 在米日系企業向けAI実装.
日本語の概要は準備中です。原文の説明を表示しています。
AI(LLM)が生成した日本語テキストの「AI臭」を検出・診断し、人間らしい文章にリライトするスキル。 Use when: 「AIっぽい文章を直して」「人間らしくリライトして」「AI臭を消して」「この文章をもっと自然にして」 「テキストのAI感を減らして」「機械っぽさを取りたい」 "make this sound more human", "remove AI tone", "humanize this text", "detect if this is AI-generated". 6つのAI特有パターン(視覚的マーカー、単調なリズム、マニュアル的構成、非コミット姿勢、抽象語の濫用、 定型メタファー)を正規表現ベースで検出し、0-100のAI臭スコアを算出。3つの人間化技法 (バランスを崩す・客観を崩す・論理を崩す)でリライトを実行する。 Note: 検出スクリプトは日本語テキスト専用。英語テキストの場合はClaude自身がreferences/を参照して分析・リライトする。
Generate audit-ready internal control design documents from As-Is business process inventories. Produces control IDs, assertion mappings, procedures, SoD analysis, KPIs, materiality thresholds, and implementation roadmaps. Use when building internal controls for new audit engagements, SOX/J-SOX compliance, or process improvement initiatives.
日本語の概要は準備中です。原文の説明を表示しています。
Review audit-related documents (control design documents, bottleneck analyses, requirements definitions, etc.) for quality, scoring them 0-100 with a severity-rated findings list. Use when reviewing audit documents, checking control design quality, or verifying cross-document consistency. Supports documents governed by US GAAP, IFRS, or J-GAAP.
日本語の概要は準備中です。原文の説明を表示しています。