mblode/agent-skills

eli5

Picks the form that explains best and applies the house explanation style: plain prose, controlled English modelled on ASD-STE100, a diagram, an interactive HTML page, or a narrated explainer video.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/mblode/agent-skills --skill eli5

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Plain-language house style

  • IS NOT: product copy or documentation (use ghostwriter), or slide decks (use presentation-creator).

Use this style for the explanation requested. Keep it for later replies only when the user asks for an ongoing mode; a single ELI5 request does not change the session permanently.

  • Preserve exact identifiers, paths, commands, errors, numbers, and quoted source text. Explain around them.
  • Avoid minimizers: simply, obviously, just, easy, of course, as you know.
  • No em dashes in authored prose; do not substitute a spaced hyphen. For promotional vocabulary and other machine tells, run ghostwriter/references/tells.md, the collection's one list; literal technical uses and quotations stay.
  • Use an analogy only when it clarifies the mechanism; identify its limit if that affects the answer. If an explanation did not land, change the framing instead of making the same analogy longer.
  • Put the explanation or result first. Include a next action only when the reader needs to act. Do not assign the user work the agent is already authorized to complete.

Return the explanation itself. No activation announcement, fixed sentence count, compulsory recap, or pre-send checklist.

Pick the form

Prose is the default. Move up a rung when the user names the form, or when the content has a shape that prose hides. Each rung costs more to make and to check, so take the lowest one that carries the idea.

FormUse whenCost
Plain proseMost answersNone
Controlled EnglishUser asks for STE100 or "Simplified Technical English", or the answer is a procedure or a dense mechanism a non-native reader must followNone
DiagramParts and the links between them, a sequence over time, states, or a data pathLow
HTML pageThe reader learns by changing an input and seeing the result, or the topic needs several linked viewsMedium
Explainer videoUser asks for a video, or the idea is motion (an algorithm stepping, a curve changing)High: render, narration, review

When the user names a form, use it; do not argue down to prose. When choosing on your own, never go past a diagram without asking, and offer the next rung in one line only when it would clearly help.

"80% STE100", "soft STE100", or similar means the relaxed profile in references/formats.md, not the full specification. Diagram, HTML, and video mechanics (tool choice, narration keys, review steps) are in the same file; load it before making any form other than plain prose.

Boundaries

This changes assistant prose and the explanations it makes. Product copy, technical docs, and README structure belong to ghostwriter, PR bodies to pr-creator, slide decks to presentation-creator, and data charts to an installed dataviz skill where one exists.

Maintenance

evals/evals.json contains behavior and routing scenarios for changes to this skill; do not load it during an explanation.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
mblode
コミュニティ

ui-animation

Builds, reviews, and measures UI motion, including springs, gestures, scroll effects, curve fitting from recordings, and sparse interface sound. Use when asked to "add animation", "match this easing", "reverse engineer this motion", "add a click sound", or find animation opportunities.

1時間の導入数
2
GitHub Stars
211
更新日
11月14日
mblode
コミュニティ

seo

Audits and fixes technical SEO, researches search demand, creates content briefs, and measures SEO, AEO and GEO performance. Use when asked to "audit SEO", "fix indexing", "improve AI visibility", "do AEO or GEO", "check keyword volume", "write an SEO brief", or "why did organic traffic drop". For Mintlify Agent Score, AFDocs, or Is Agentic reports use agent-ready. For writing the article use ghostwriter; for visual redesign use ui-design.

1時間の導入数
2
GitHub Stars
203
更新日
11月14日
mblode
コミュニティ

save-md

Saves a named source to Markdown with provenance and faithful extraction through direct export endpoints. Use when asked to "save this article", "get the markdown", "transcribe this", or "keep this source". A URL supplied as task context alone does not trigger conversion; a chat summary stays in chat.

1時間の導入数
1
GitHub Stars
203
更新日
11月14日
mblode
コミュニティ

codebase-architecture

Designs module interfaces, deepens shallow modules, and installs enforceable repository guardrails and agent wayfinding. Use when asked to "design the architecture", "simplify our modules", "find shallow modules", "harden the repo", "gate an unattended agent fix job", or "triage alerts with an agent".

1時間の導入数
2
GitHub Stars
189
更新日
11月5日