From jlindley-skills
Quick session quality check - single honest grade driven by what would have been better, plus actionable insights
How this skill is triggered — by the user, by Claude, or both
Slash command
/jlindley-skills:gradeclaude-opus-4-6The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Standalone grading — a subset of what `/wrap` does, without the interactive follow-up, document mining, or loose ends scan.
Standalone grading — a subset of what /wrap does, without the interactive follow-up, document mining, or loose ends scan.
# Session Grade
**What would have been better:** [1-3 concrete things that would have improved the session]
**Grade: [A-F]**
## Session Insights (up to 3)
- [Patterns from this specific session, what went well/poorly, process observations]
## Meta Insights (up to 3)
- [Broader learnings beyond this session — tooling, skills, collaboration patterns]
- For sessions involving multi-agent skills or parallel dispatch: Did agents stay in their lanes? Did information flow correctly between phases? Were model assignments appropriate?
npx claudepluginhub jlindley/jlindley-marketplace --plugin jlindley-skillsReviews completed coding sessions to extract actionable improvements: DX friction, documentation gaps, architecture issues, anti-patterns, bug prevention, and tooling updates.
Analyzes current Claude Code session for agent efficiency (tool precision, autonomy) and quality (CLAUDE.md compliance, code patterns), scoring dimensions and surfacing 2-3 actionable improvements.
Analyzes Claude Code agent team session exports against best practices, delivering structured reports with verdicts, scorecards, recommendations, and improved prompt rewrites.