samwang0723/learn
templates/skills/learn/SKILL.md
Extract reusable patterns from the current session and save them as skill files. Use when the user says 'learn from this', 'extract patterns', 'save this as a skill', 'what did we learn', or after solving a non-trivial debugging or integration problem worth capturing for future sessions.
$ install --global
skillsauthnpx skillsauth add samwang0723/claudecode-setup learnInstall 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 17, 2026, 7:44 AM51.9s1 file scanned
SKILL.md
- name:
- learn
- description:
- Extract reusable patterns from the current session and save them as skill files. Use when the user says 'learn from this', 'extract patterns', 'save this as a skill', 'what did we learn', or after solving a non-trivial debugging or integration problem worth capturing for future sessions.
Extract Reusable Patterns
Analyze the current session and extract patterns worth saving as reusable skill files in ~/.claude/skills/learned/.
Workflow
Step 1: Identify Extractable Patterns
Review the session for these pattern categories:
- Error Resolution — Non-obvious root causes and their fixes (e.g., "Jest mock hoisting causes undefined when imported after mock setup — move
jest.mock()above imports") - Debugging Techniques — Tool combinations or diagnostic sequences that worked (e.g., "Use
git bisect+vitest --reporter=verboseto isolate flaky test to specific commit") - Workarounds — Library quirks, API limitations, version-specific fixes (e.g., "Next.js 14
useSearchParamsrequiresSuspenseboundary or build fails silently") - Project Conventions — Codebase patterns, architecture decisions, integration approaches discovered during the session
Step 2: Evaluate Reusability
Skip patterns that are:
- Trivial fixes (typos, simple syntax errors)
- One-time issues (specific API outages, transient failures)
- Already documented in project README or CLAUDE.md
Keep patterns that:
- Would save 5+ minutes if encountered again
- Apply across multiple projects or contexts
- Involve non-obvious behavior or undocumented quirks
Step 3: Draft the Skill File
Create ~/.claude/skills/learned/[pattern-name].md using this structure:
# [Descriptive Pattern Name]
**Extracted:** [Date]
**Context:** [Brief description of when this applies]
## Problem
[What problem this solves — be specific about symptoms]
## Solution
[The pattern/technique/workaround — include concrete steps]
## Example
[Code example if applicable]
## When to Use
[Trigger conditions — what should activate this skill]
Step 4: Confirm and Save
- Present the drafted skill to the user with a summary of what was captured
- Ask for confirmation before writing the file
- Save to
~/.claude/skills/learned/on approval
Guidelines
- One pattern per skill file — keep each focused and self-contained
- Use kebab-case for filenames (e.g.,
jest-mock-hoisting-fix.md) - Include concrete examples with real code when possible
- Write trigger conditions that help future sessions auto-activate the pattern
Related Skills
samwang0723/write-tech-spec
development
VerifiedTrustedCommunity
Generate a technical specification document using the DDD template in template.md. Use when the user says 'write tech spec', 'create tech spec', 'technical specification', or needs a structured design document for a new feature or major change covering architecture, domain models, APIs, data design, security, and operations.
1SKILL.mdUpdated Apr 17, 2026
samwang0723/write-prd
testing
VerifiedTrustedCommunity
Write a Product Requirements Document (PRD) using the standard TMAB template with stakeholders, user stories (Given-When-Then), success metrics, and A/B testing plans. Use when the user asks to write a PRD, create product requirements, document a feature spec, or plan a new product feature.
1SKILL.mdUpdated Apr 17, 2026
samwang0723/team-stop
data-ai
VerifiedTrustedCommunity
Clean up an agent team. Removes team resources, optionally cleans worktrees and branches. Use after team work is complete and merged. Use when told to "stop team", "cleanup team", "disband team".
1SKILL.mdUpdated Apr 17, 2026
samwang0723/team-status
testing
VerifiedTrustedCommunity
Check progress of an active agent team. Shows member status, completed tasks, pending work, and any messages. Use when asked "team status", "how's the team", "check team progress", "team update".
1SKILL.mdUpdated Apr 17, 2026