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에서 보기