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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
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.
Not this skill: a precise technical specification, an architecture document, or a slide deck for an audience that already knows the domain.
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.
One self-contained HTML artifact. Inline all CSS and SVG so it renders anywhere; do not load external scripts, stylesheets, or images.
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.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。