AMindToThink/debrief
skills/debrief/SKILL.md
End-of-conversation debrief — give the user tips on working with Claude more effectively, and share Claude's honest perspective on the collaboration.
tools
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add AMindToThink/claude-code-settings debriefInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 7:08 PM159.8s1 file scanned
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
Related Skills
AMindToThink/accessible-website-check
development
VerifiedTrustedCommunity
Use when the user asks to check, audit, or improve a website or web project for accessibility (a11y), WCAG compliance, screen reader support, keyboard navigation, color contrast, or alt text. Triggers a plan-mode investigation against the TeachAccess design and code checklists, then implements approved fixes.
3SKILL.mdUpdated May 13, 2026
AMindToThink/skills/make-anonymous-branch
development
VerifiedTrustedCommunity
--- name: make-anonymous-branch description: Use when preparing a research repo for double-blind submission via anonymous.4open.science (ICML/NeurIPS/ICLR/workshop). Builds a single `anon-submission` branch with code+data+paper, scrubs identity leaks (author names, home paths, emails, wandb metadata, PDF author fields), patches LaTeX for pdf.js compatibility, and leaves `main` untouched. Triggers: "make an anonymous branch", "anonymize my repo for X submission", "set up anonymous.4open.science",
3SKILL.mdUpdated May 12, 2026
AMindToThink/implement-math
development
VerifiedTrustedCommunity
Translate math (formulas, estimators, algorithms) into code so the implementation faithfully matches what the source actually specifies. Use when writing code from a formula, reviewing an LLM-generated implementation of a formula, debugging a numerical mismatch with a paper, designing a new metric/estimator, or refactoring an existing math-heavy computation. Especially load-bearing whenever aggregation operators (sums, means, expectations, products, geometric means) appear over indices that can be reordered, or whenever the same English label can refer to multiple non-equivalent estimators (e.g. ratio-of-means vs mean-of-ratios, micro-average vs macro-average, sample-weighted vs unweighted). Prevents the failure mode where a code path silently implements the wrong estimator under the same name as the intended one.
3SKILL.mdUpdated May 12, 2026
AMindToThink/finding-old-chats
development
VerifiedTrustedCommunity
Use when the user asks to review, find, summarize, or check Claude Code chat transcripts from a past date or time range ("review my chats from May 1st", "what was I working on yesterday", "any unfinished sessions this week"). Reads transcripts under `~/.claude/projects/`, handles local-time vs UTC correctly so late-evening sessions don't get dropped, and flags chats whose last assistant turn looks like an unanswered question.
3SKILL.mdUpdated May 12, 2026