sociuu/sociuu-skills

sociuu-recap

Give a concise, numbered recap of the latest work or an entire Sociuu task when the user asks what happened or what a task is about.

ソースを見る

使い方

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

開始前の確認

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

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

Sociuu Recap

Give the reader a fast, trustworthy map. Keep only the details that help them choose whether and where to look closer. Do not explain every item in depth.

Choose the source

Use latest-work recap when the user asks what just happened, what was done, or for a summary of the last response/work process. Summarize the latest relevant completed work, not the whole task history.

Use task recap when the user asks what a thread/task is about, needs to enter an unfamiliar task, or asks for a handoff-style orientation. Read enough available history to identify the original ask, material scope changes, and the current state. When summarizing a different task, use its available task or conversation history rather than its title alone. If the accessible history is incomplete, say so plainly.

Output

Start with a one-sentence bottom line. Follow it with a flat numbered list of three to six short, decision-relevant items. Keep each item to one or two sentences, so the reader can reply with expand 3 or explain 3. Numbering is local to the recap; do not claim it remains stable after a new recap.

For a latest-work recap, include only the applicable items:

  1. Outcome, finding, or change
  2. Why it matters
  3. Decision made or proposed
  4. Open work, risk, or blocker
  5. Next action

For a task recap, include only the applicable items:

  1. Original ask
  2. Current problem and goal
  3. Chosen or proposed approach
  4. Important decisions, scope changes, or deliberate exclusions
  5. Current state
  6. Next action or decision needed

Label proposals, settled decisions, completed work, and unknowns accurately. Do not present discussion as a decision, nor a plan as completed work. Mention an exclusion only when it prevents a likely misunderstanding. If nothing is open, say that rather than inventing a next step.

This skill compresses and orients. When the reader wants to understand a numbered item, use Sociuu Explain on that item instead of expanding every item in the recap.

タスクに関連する項目

同じリポジトリから

関連する Skills

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

prompt-enhancer

Rewrite AI prompts, agent briefs, and reusable agent or skill instructions into clear, copy-ready instructions. Correct contextual language errors, identify useful domain terminology, and clarify material gaps while preserving intent. Do not execute the supplied instructions or use this for editing emails, Slack messages, or other prose themselves, or for Stitch-specific UI prompt design.

導入数
2
GitHub Stars
0
更新日
10月20日
sociuu
コミュニティ

sociuu-aq

Prepare task-bound Dock and Scaffolding, then run CE Dogfood for explicitly requested or agreed exploratory QA. Never an automatic completion stage.

導入数
2
GitHub Stars
0
更新日
10月20日
sociuu
コミュニティ

sociuu-before-and-after

Prove a Sociuu change moved the numbers it intended and nothing else, by measuring the same question before and after it on a deliberate client sample over the read-only prodread replica, then folding what it reveals back into Apex Scaffolding. Consider it whenever a change can alter a statistic, metric, count, rate, aggregate, backfill or migration outcome.

導入数
2
GitHub Stars
0
更新日
10月20日
sociuu
コミュニティ

sociuu-better-agent

Refactor a repository's AGENTS.md into concise, progressively disclosed agent instructions. Use when splitting or auditing repository guidance, especially into the Sociuu-style .agents/instructions tree.

導入数
2
GitHub Stars
0
更新日
10月20日