「explanation」の検索結果

Translate existing code-explanation docs into another language, Chinese by default. Translates a whole `CODE_EXPLANATION/` folder into a parallel `CODE_EXPLANATION_<LANG>` copy (e.g. `CODE_EXPLANATION_ZH`), or a single file — either bilingually in place (English + translation interleaved) for small files or as a `<name>_<lang>.<ext>` sidecar copy for larger ones. Keeps filenames, code, identifiers, file paths, and technical terms in English — only the explanatory prose is translated. Use this skill whenever the user wants to translate, localize, or produce a non-English version of code-explanation / codebase documentation: phrases like "translate-explanation", "translate the code explanation", "translate the CODE_EXPLANATION folder", "localize these docs to Chinese", "make a Chinese version of the explanation", or naming any target language for the explanation files. Default to Chinese (ZH) when no language is specified.

日本語の概要は準備中です。原文の説明を表示しています。

Generate a complete, beginner-friendly explanation of an entire code repository as a set of markdown files. Maps the repo structure with `treecap` (installing it if missing), studies the actual source, then writes a `CODE_EXPLANATION/` folder containing an `OVERVIEW.md` plus numbered deep-dive files (01_architecture.md, 02_models.md, ...) that explain how the code is built, what it does, and how the pieces fit together — illustrated with real code excerpts. Use this skill whenever the user wants to understand, document, onboard onto, or get a walkthrough of a codebase: phrases like "explain this repo", "explain the code", "code explanation", "walk me through this codebase", "help me understand how this is built", "document the architecture", or "what does this project do" — even if they don't say the word "skill". Prefer this over ad-hoc summaries whenever the goal is a durable, written explanation of a whole repo.

日本語の概要は準備中です。原文の説明を表示しています。

Explanation documentation patterns for understanding-oriented content - conceptual guides that explain why things work the way they do. Use when writing an explanation doc, conceptual guide, understanding/background doc, design rationale, or architecture explanation, or when asked how/why something works. Builds on the docs-style core writing principles.

日本語の概要は準備中です。原文の説明を表示しています。

Create self-explanation prompts that deepen understanding of worked examples, texts, or diagrams. Use when students read material passively without engaging with underlying principles.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts formal explanation letters for Canadian Study Permit applications by structuring the argument around program attractiveness, background relevance, choice rationale, and family benefits.

日本語の概要は準備中です。原文の説明を表示しています。

Implements data subject rights mechanisms for AI systems including right to explanation of AI decisions, contestation procedures, human review, model output correction, and training data access. Covers GDPR Arts. 15-22 and AI Act Art. 86. Keywords: data subject rights, AI explanation, contestation, human review, training data access, model correction.

日本語の概要は準備中です。原文の説明を表示しています。

Create self-explanation prompts that deepen understanding of worked examples, texts, or diagrams. Use when students read material passively without engaging with underlying principles.

日本語の概要は準備中です。原文の説明を表示しています。

Generate Claim, ClaimResponse, and ExplanationOfBenefit (EOB) resources for healthcare billing including professional, institutional, pharmacy (Rx), dental, and vision claims. Use when user mentions claims, EOB, explanation of benefit, billing, reimbursement, adjudication, pharmacy claims, Rx claims, denied claims, copay, deductible, or allowed amount.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts formal explanation letters for Canadian Study Permit applications by structuring the argument around program attractiveness, background relevance, choice rationale, and family benefits.

日本語の概要は準備中です。原文の説明を表示しています。

コードの構造や処理の流れ、性能比較を対話型の図で説明し、OpenClawのダッシュボードに指標や表を継続して表示するスキルです。

• コード構造やデータの流れを説明したいとき
• 実測した性能を比較したいとき
• UIの試作を操作して確認したいとき

講座の計画から章・演習・問題・解答・解説のフォルダと説明ファイルのひな形を作り、命名規則やリンクを検査して教材づくりの土台を整えるスキル。

• 新しい講座の演習構成を作りたいとき
• 問題・解答・解説のひな形づくり
• 演習の改番と構成チェック

直前の説明が分かりにくかったときに、背景を補って説明し直します。簡略化された技術英語の規格とプロジェクトの用語集に沿い、話の流れを伝え直すスキルです。

• 直前の説明を分かりやすく聞き直したいとき
• 話の流れを理解するための背景説明
• プロジェクトの共通用語での説明

写真や動画、公開記録の少ない手がかりをつなぎ、場所・日時・組織の関係などを検証します。根拠と仮説を分け、反証や未確認事項も整理する調査スキル。

• 公共の場所を写した写真の位置確認
• 公開記録からイベントの時系列を調べたいとき
• 企業とドメインの関係調査

数学の概念や数式の導出、アルゴリズムの動きをアニメーション動画にします。構成づくりから描画、動画の結合まで、図形で理解を促す解説を制作します。

• 数学の概念を図形で説明したいとき
• 数式の導出を順に見せたいとき
• アルゴリズムの動きを可視化

Generate self-contained HTML visual explanations for systems, code changes, plans, data, and technical concepts. Use for diagrams, architecture overviews, diff or plan reviews, project recaps, comparison tables, slide decks, animated explainers, narrated MP4 videos, and other visual explanations.

日本語の概要は準備中です。原文の説明を表示しています。

Turn a wiki topic into a cited Markdown briefing, plain-language explanation, or progressive lecture. Use this skill for topic-based briefing, explanation, and lecture requests that must stay within the evidence compiled in an Obsidian vault.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to explain a problem, issue, PR, or feature as an infographic. Create a step-by-step visual explanation starting from user code or actions, with a clear problem/solution boundary, syntax-highlighted snippets, and focused diagrams. Support standalone educational PDFs and Markdown-first PR explanations, with optional images only for complex diagrams. Also apply when explicitly invoked by the repository PR writer.

日本語の概要は準備中です。原文の説明を表示しています。

Create an offline HTML explanation of a code change (diff, PR, branch) or of a topic, system, or question. Use when a visual walkthrough document is requested.

日本語の概要は準備中です。原文の説明を表示しています。

Reduce defensive writing in drafts and revisions by removing unnecessary caveats, disclaimers, hedges, apology-like framing, negative self-limiting statements, and over-explanations while preserving necessary scope, accuracy, safety, legal, ethical, and methodological limits. Use when drafting or revising academic writing, papers, essays, abstracts, introductions, contribution statements, discussions, conclusions, technical explanations, grant writing, product writing, policy writing, professional reports, or any text the user wants to be clearer, stronger, more direct, more concise, more confident, less verbose, less caveated, less apologetic, or less defensive.

日本語の概要は準備中です。原文の説明を表示しています。

Require the learner to explain a concept in their own words before the AI evaluates or extends it. Ensures the AI works from the learner's understanding rather than providing an explanation from scratch.

日本語の概要は準備中です。原文の説明を表示しています。

Generate self-contained HTML visual explanations for systems, code changes, plans, data, and technical concepts. Use for diagrams, architecture overviews, diff or plan reviews, project recaps, comparison tables, slide decks, and other visual explanations.

日本語の概要は準備中です。原文の説明を表示しています。

Routes AIX360 explainability tasks across local black-box attribution, counterfactuals and certification, interpretable models, time-series explanations, datasets, and explanation-quality metrics.

日本語の概要は準備中です。原文の説明を表示しています。

Surfaces Han's shared Human-Readable Output Standard — the readability rule and the writing-voice profile — into the calling skill's own context, so the caller drafts in voice and runs its self-check against the current standard sourced from one canonical copy. Use when a prose-producing skill needs the shared readability standard available in context before it drafts. Governs the shape of a written deliverable, where explanation-guidance governs what a run says to a person in a turn. Runs in the caller's context and hands control straight back; it does not produce a deliverable of its own, rewrite anything, or judge the caller's work. Does not run the adversarial rewrite pass — dispatch the readability-editor agent for that, or use edit-for-readability to rewrite an existing target. Does not cover explaining technical work to a reader who will not implement it — use explanation-guidance for that.

日本語の概要は準備中です。原文の説明を表示しています。

Require the learner to explain a concept in their own words before the AI evaluates or extends it. Ensures the AI works from the learner's understanding rather than providing an explanation from scratch.

日本語の概要は準備中です。原文の説明を表示しています。