Capture session learnings
Skill kavins14/claude-goodness/skills/capture-session-learnings
My personal Claude Code setup
npx -y skills add kavins14/claude-goodness --skill capture-session-learningsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Analyze the current Claude Code session and identify useful patterns, workflows, or configurations worth saving to the claude-goodness repository. Use at the end of a session or after completing something useful.
SKILL.md
1.8 KB, 345 tokens by cl100k_base, as published. Nobody here has run it
Review the conversation history and identify valuable learnings to save to the claude-goodness repository.
What to look for:
- Useful Claude Code workflows or patterns demonstrated
- Reusable configurations or setup steps
- Interesting tool combinations or techniques
- Repeated tasks that could become new skills
- Resources or links mentioned that should be documented
Analysis Process:
-
Review the Current Session
- Look for patterns in how Claude Code was used
- Identify repeated tasks or workflows
- Note configurations created or discussed
-
Categorize Findings
- Skills: Repeated workflows that could be automated
- Resources: Useful links, documentation, or references
- Patterns: Common approaches or best practices discovered
- Configurations: Reusable project settings
-
Present Recommendations
Show a summary in this format:
# Session Analysis
## Useful Patterns Found
- [Pattern 1]: Description and why it's useful
- [Pattern 2]: Description and why it's useful
## Recommended Additions
### New Skill: [skill-name]
**Location**: skills/[skill-name]/SKILL.md
**Reason**: [Why this would be useful]
**Content Preview**: [Brief description or draft]
### Resource Addition
**What**: [Resource name/link]
**Where**: README.md resources section
**Why**: [Relevance and value]
## Next Steps
- [ ] Create [item 1]
- [ ] Add [item 2]
- [ ] Update [item 3]
Ask which items the user wants to save, then offer to create the files if approved.