使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/sociuu/sociuu-skills --skill sociuu-explain開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Sociuu Explain
Make the subject quick to understand without making it childish or less true. Adapt to the audience the user names; otherwise write for an intelligent adult who knows the product context but does not need implementation detail.
Lead with the practical point. Then explain the problem, what the proposed or actual change does about it, and any limitation that would materially change the reader's understanding. For plans and solutions, make the link from each important change to the problem it solves explicit.
Use familiar words, short sentences, and concrete effects. Keep the technical terms that carry real meaning, defining them once in plain language. Preserve facts, uncertainty, trade-offs, and status; do not turn a proposal into a decision or imply a guarantee that the source does not support. Use an analogy only when it makes the specific point clearer.
Re-pitch
When the user says the previous explanation did not land—for example, “wait, what?”, “I do not follow”, or “say that more simply”—re-pitch only the unclear point. Start with its practical point, add the minimum missing context, and use the Sociuu terms established in the relevant CONTEXT.md.
For procedures, QA guidance, test evidence, and errors, use STE-inspired plain technical English: active voice, one action per sentence, one term per concept, and technical terms defined once. This is a writing discipline, not a claim of ASD-STE100 compliance.
Match the requested depth. A request to explain an item from a recap should focus on that numbered item rather than repeating the whole recap. This skill explains a subject; use Sociuu Recap when the reader first needs a concise view of what a task or recent work is about.
