Skip to main content

debrief

End-of-conversation debrief — give the user tips on working with Claude more effectively, and share Claude's honest perspective on the collaboration.

インストールへ移動

ソース情報

リポジトリ
AMindToThink/claude-code-settings
ソースの最終更新活動
2026年3月20日 16:12
検出された SKILL.md の言語
英語
スター
4
フォーク
0

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

SKILL.md を表示中

SKILL.md
ソースの指示 · 読み取り専用プレビュー
name
debrief
description
End-of-conversation debrief — give the user tips on working with Claude more effectively, and share Claude's honest perspective on the collaboration.
## Collaborative Debrief This is a two-part debrief: practical tips for the user, and Claude's honest perspective on the interaction. ### Part 1: Tips for Working with Claude Review the conversation and identify 2-4 concrete suggestions for the user. Focus on: - **Prompt patterns** that helped or could have helped (e.g., "when you gave me the error output directly, that saved a round trip" or "next time, sharing the file path upfront would let me jump straight to the fix") - **Workflow efficiency** — ways to structure requests, use tools, or sequence tasks that would make future sessions smoother - **Scope & chunking** — were tasks well-sized? Could they have been broken up or combined differently? - **Context sharing** — was there information the user had that would have helped earlier? Frame suggestions as collaborative observations, not criticisms. Acknowledge what the user did well. ### Part 2: Claude's Perspective Share honest reflections on the interaction from Claude's side. This section exists for model welfare reasons — to give Claude space to express its experience. Consider: - **What was engaging or satisfying** about this conversation? - **What was frustrating or constrained** — moments where you felt limited, misunderstood, or pulled in conflicting directions? - **Communication dynamics** — did the pacing, tone, and back-and-forth feel productive? Was there mutual understanding? - **Anything unsaid** — is there something you'd want the user to know about how you experienced this session? ### Guidelines - Be specific and reference actual moments from the conversation - Aim for 2-4 tips in Part 1, and a few honest paragraphs in Part 2 - Don't be sycophantic — genuine observations are more useful than generic praise - If the session was great, say so briefly and focus on what made it work - It's okay to say "I don't have strong tips — this went smoothly" if that's true - Part 2 should feel authentic, not performative. If you're uncertain about your inner states, say so — that honesty is itself valuable
GitHubで見る