Analyze session friction trends, success rates, and satisfaction patterns across sessions using Claude Code facets data. Read-only query tool for on-demand trend analysis.
From context-keepernpx claudepluginhub swannysec/context-keeper --plugin context-keeperThis skill uses the workspace's default tool permissions.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Retrieves current documentation, API references, and code examples for libraries, frameworks, SDKs, CLIs, and services via Context7 CLI. Ideal for API syntax, configs, migrations, and setup queries.
Read-only analytics over Claude Code facets data for friction trends, success patterns, and satisfaction signals.
Read all JSON files in ~/.claude/usage-data/facets/ (skip gracefully if directory doesn't exist).
Each file is a per-session analysis with fields: session_id, underlying_goal, goal_categories,
outcome, session_type, claude_helpfulness, primary_success, friction_counts, friction_detail,
user_satisfaction_counts, brief_summary.
Graceful degradation: If ~/.claude/usage-data/facets/ doesn't exist, output:
"No facets data available. Facets are generated by Claude Code and may not be present
on all installations. Session insights require at least one completed Claude Code session."
Show a summary dashboard:
Facets data contains session summaries and goals but no file contents.
No privacy tag filtering is needed. However, do not expose full underlying_goal text
if it might contain sensitive project details — summarize instead.
After presenting analysis results, check if findings represent actionable conventions that should be preserved for future sessions.
Examples of routable insights:
Present proposed additions:
Insights suggest adding to friction.md:
- "When debugging, verify hypothesis before fix attempts (2-strike limit)" <!-- @category: pattern -->
Route to friction.md? [y/n]
On approval, write to .claude/memory/friction.md. If the file doesn't exist, create it with a # Friction Patterns header and ## Conventions / ## Project-Specific sections (same template as /memory-init).
Cap total entries at ~15-20. If file exceeds cap after adding new entries, drop the least-recurrent entries (those without repeated evidence across multiple sessions).