Menu
SkillsMP has collected 90 skills from SamyakJhaveri/loam. Open a skill to review its source and details.
Showing 40 of 90 collected skills.
Advisor for selecting an optimal model tier (Opus/Sonnet/Haiku) for a specific task. Use before launching an agent team, before a multi-file refactor, or when deciding whether to drop from Opus to Haiku for transactional work (commits, formatting). Analyzes…
Generate ranked, evidence-backed creative ideas the user has not asked for, aimed at a named goal, then execute the cheapest one immediately as proof. Use when the user says "surprise me", "what am I missing", "creative or elegant ideas", "how can we do this…
Fast 30s session bootstrap briefing. Use when resuming work after any break, at the start of a fresh session, or when unsure of current project state. Reports git status, recent commits, environment state, memory-index staleness, pending tasks, and red flags…
Memory consolidation for Claude Code per-project memory files. Use after major milestones, after 5+ sessions without consolidation, when memory feels stale, or before long breaks. Runs a 4-phase audit -> plan -> approval -> execute flow; subcommands `audit`…
Use when a session's implementation work is complete and needs adversarial critique and code quality review before committing. Triggers - after multi-file changes, after feature implementation, before final commit on significant work, when independent review…
Second-opinion review of the current diff via the Codex CLI, read-only. Use when you want an independent adversarial review of a diff from a different model before merging. Manual only. NOT for replacing your project's own diff-review or validation gate;…
Author a CONTEXT.md routing file for a specified project subdirectory using the canonical ICM anatomy (inlined below; richer if the authoring-context-docs skill is installed). Use when adding a new high-traffic area whose routing logic the root CLAUDE.md…
Use when reviewing an implementation plan in a fresh session, after the plan was written in a prior session, and you want an adversarial pass (checklist + elegance gate + a self-contained handoff plan) without copy-pasting a reviewer prompt. Spawns the…
Second-opinion adversarial review of a PLAN file via the Codex CLI, read-only. Use when a plan needs an independent cross-model review before execution. Manual only. NOT for replacing your project's own plan-review gate; Codex never edits - findings are…
Surface what you do not know before prompting, log deviations during implementation, and verify understanding after. Use before starting in an unfamiliar area, when you cannot describe what you want, when a long-horizon task came back wrong, when a plan needs…
Structured post-task reflection - surprises, pattern proposals, prompt improvements, gotchas to record. Use at the end of a significant session, after a debugging marathon, or when patterns emerged that should update CLAUDE.md or .claude/rules/. NOT for…
Run the BLIND frame-breaking elegance review on a plan or implementation via the elegance-reviewer agent. Use AFTER a correctness review (plan-review-invoke, plan-review-fanout, or codex-plan-review) and BEFORE execution, on any plan that creates new files,…
Write the always-loaded rules layer that a plugin cannot ship into the current repo: a CLAUDE.md skeleton (purpose + gotchas only) and a generic workflow.md rule (model notes only). Optionally vendors the pre-commit gate hooks into .claude/hooks/ for…
Deterministic pre-commit validation - two waves (Deterministic / Rule-based) run on demand. Use when a change is risky and before every substantive commit. Enforcement is a native git pre-commit hook, not a sentinel. NOT for: ad-hoc test runs, code review, or…
Use when starting any conversation - a short router for the skills library. Skills are optional tools, not gates.
Write or update a handoff document so the next agent with fresh context can continue this work. Use for IN-PROGRESS work only, not end-of-session cleanup. Writes to the project root. Renamed from `handoff` on 2026-08-02 to avoid a name clash with the…
Sync Claude Code assets between this project and the project-template buffer. Use when promoting a generally-useful agent/skill/hook/rule from this project back to the template, when pulling a template-side update down into this project, or when checking what…
4-skill academic pipeline: deep research (13-agent), academic paper (LaTeX), peer review (7-agent), pipeline orchestrator (10-stage). CC BY-NC 4.0 — non-commercial use only.
Analyzes existing workflows and processes to find inefficiencies, bottlenecks, and optimization opportunities. Goes beyond automation to improve the process itself. Use when user says "optimize my process", "find bottlenecks", "why is this slow", "improve…
Takes a process description and generates a complete Standard Operating Procedure document with numbered steps, decision points, checklists, and troubleshooting guidance. Use when user says "write an SOP", "create SOP", "standard operating procedure",…
Interactive weekly review assistant that helps business owners reflect on their week, measure progress against stated goals, and plan the next week with clarity. Use when user says "weekly review", "review my week", "what did I accomplish", "plan next week",…
Maps business processes from natural language descriptions into structured workflows, identifies automation opportunities using the GREEN/YELLOW/RED framework, and generates visual workflow diagrams. Use when user says "map my workflow", "describe my…
GraphRAG-powered code review with blast-radius analysis via Tree-sitter AST. MCP server. Recommended for 500+ file codebases.
Autonomous multi-source research agent with MCP server. Planner/executor architecture, 5 MCP tools. Requires 3 API keys (Tavily + Anthropic + embeddings). Research-flavor.
Use when you have a free-form draft prompt and want it rewritten into Claude Opus 4.6 or 4.8 conventions before pasting it into a new planning or execution session. Trigger phrases — "align prompt", "rewrite for opus", "tune prompt for claude". NOT for…
Structured decision-making tool that helps users evaluate options systematically using weighted scoring, criteria analysis, and practical recommendations. Use when user says "decision matrix", "help me decide", "compare options", "which should I choose",…
Adversarial research interrogation before launching an eval or making a published claim. Use before /overnight-eval, before adding a claim to the paper, or when a reviewer-style stress test is needed. 4 waves — basics, clarifications, deep probes, assessment.…
Tool recommender — takes freeform intent and returns the best skill/agent/command to use. Use when unsure which tool to invoke next. NOT for: executing tasks directly — only recommending which skill, agent, or command to use next.
Use when invoked automatically by the UserPromptSubmit hook after a prompt is flagged as vague. Researches context, then generates 1-6 targeted clarifying questions before executing. Do NOT invoke this manually — it is triggered by the hook in…
Design polish with 27 deterministic anti-pattern rules + 12-rule LLM critique. By Paul Bakaus (jQuery UI creator). Commands: polish, audit, critique, typeset, animate, colorize, layout, delight. Apache-2.0.
Continuously improve Claude's effectiveness by recognizing patterns, saving memory, creating skills, and refining project knowledge. Use when Claude notices repeated workflows, encounters a problem it solved before, wants to save something for future…
9 Nature-journal skills: figures, polishing, writing, citations, data availability, paper reading, reviewer responses, paper-to-PPT, academic search (MCP). MIT license.
Manus-style persistent markdown planning with task_plan.md, findings.md, progress.md. Hook-based re-injection after /compact.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or…
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (DOMAIN.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and…
Find deepening opportunities in a codebase, informed by the domain language in DOMAIN.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase…
Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user…
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.