Menu
Skills in this repository
SkillsMP has collected 90 skills from SamyakJhaveri/loam. Open a skill to review its source and details.
SamyakJhaveri/loamShowing 40 of 90 collected skills.
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
Stanford STORM — LLM research pipeline for Wikipedia-quality articles with citations. Multi-perspective research, Co-STORM collaborative mode. Python package, no native Claude Code integration.
Creates and launches coordinated agent teams using TeamCreate for multi-teammate tasks requiring cross-talk, shared task lists, and lifecycle management. Use when 2+ workers need to communicate findings to each other, not just report to parent. NOT for…
Multi-agent deliberation council for complex tasks. Spawns 4 specialist agents with distinct thinking styles who independently analyze the problem, then 2 cross-examination agents who argue and synthesize. Produces higher quality output through structured…
Design system generator with curated color palettes, font pairings, UI styles, product-type rules, and UX guidelines across multiple tech stacks.
Multi-agent codebase analysis with interactive React knowledge graph dashboard. Best for onboarding and visual architecture exploration.
Creates and launches coordinated agent teams using TeamCreate for multi-teammate tasks requiring cross-talk, shared task lists, and lifecycle management. Use when 2+ workers need to communicate findings to each other, not just report to parent. NOT for…
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…
Autonomous multi-phase release execution. Reads a PHASE-PLAN.md with stages 1-N and executes them end-to-end, running validation + critique per stage, committing with clean scope, and advancing automatically. Halts only when a validation gate fails twice or a…
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, env state, memory staleness, pending tasks, and red flags (uncommitted…
Create a conventional commit. Use when user says "commit", "make a commit", or "save changes". NOT for: drafting code, running tests, or anything that changes files — this skill only stages and commits already-finished work.
Create high-quality Claude Code custom skills and slash commands. Use when the user wants to create a new skill, build a custom command, make a slash command, or add a reusable workflow.
Parallel adversarial critique with 4 specialized agents plus synthesis. Use before merging a feature branch, before committing a complex plan, or when you want independent multi-angle review of a plan or implementation. Complements /multi-review (which…
Generate diagrams and visuals from code or descriptions. Use when the user needs a rendered diagram, code visualization, or architecture image. Subcommands — excalidraw (hand-drawn), drawio (formal XML), paper (academic illustrations), gitdiagram (repo…
Memory consolidation for ~/.claude/projects memory files. Use after major milestones, after 5+ sessions without consolidation, when memory feels stale, or before long breaks. Runs 4-phase audit→plan→approval→execute; subcommands `audit` (read-only) and `prune…
Feature development workflow — explore, plan, implement, verify. Use when adding a non-trivial feature. NOT for single-file bug fixes (use fix-bug).
Bug fix workflow — reproduce, diagnose, plan, fix, verify, record. Use when a test fails, a build step fails, or results show an unexpected pattern. Mandates reproduction before diagnosis. Integrates with /validate on exit. NOT for: feature additions,…
Guided specification generation wizard. Use when adding a new feature, API endpoint, or component — forces a written spec before implementation. Validates scope, drafts a structured spec, checks it against conventions, and registers it in the project. NOT…
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…
Use when ending a session with unfinished work, switching context, or preparing for another agent to continue. Write or update a handoff document so the next agent with fresh context can continue this work. NOT for: session notes, commit messages, or PR…
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells,…
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…
Multi-agent parallel code review with 4 reviewers (style, correctness, security, performance). Use before merging a feature branch, before committing a non-trivial change, or when a second pair of eyes is needed. Complements /validate (which checks pipeline…
Invoke the plan-reviewer agent using the canonical reference prompt from seed/plan-reviewer-design.md. Use when reviewing a plan in a fresh Claude Code session (after the plan was created in a prior session) and you want adversarial review (checklist +…
Push and open a GitHub PR. Use when user says "open a PR", "create a pull request", or "push and PR". NOT for: committing changes (use /commit), running validation (use /validate), or reviewing code (use /multi-review) — only the push-and-PR step.
TDD rendering gate for Copier template development. Writes E2E assertions first, then iteratively fixes the template until all flavors render cleanly. Never commits on a red suite. Use when editing Copier template files (copier.yml, .jinja files, flavor…
Author a CONTEXT.md routing file for a specified project subdirectory using the canonical CONTEXT.md anatomy (.claude/rules/context-md-anatomy.md). Use when adding a new high-traffic area whose routing logic the root CLAUDE.md cannot describe economically.…
Use when you explicitly want adversarial, decision-aware critique of a session's completed work before committing — invoke it manually with /session-critique. Reviews every changed artifact (code, data, report) as a senior software engineer and AI researcher,…
Orchestrates the full shipping pipeline in strict order. Runs session-critique, then validate (both waves), then commit, then PR. Use when work is complete and ready to ship. Enforces ordering to prevent premature commits and skipped critiques. Accepts…
Scan codebase for tech debt: duplicated logic, dead code, magic numbers. Use at end of session before final commit for a broad codebase sweep. NOT for reviewing only recently changed code (use /simplify).
Post-session validation loop — two-wave checks (Deterministic / Rule-based) before commit. Use before every git commit. Writes .validation_passed sentinel with waves_passed field on success. NOT for: ad-hoc test runs, code review, or implementation work —…
Data augmentation testing workflow. Use when testing a new augmentation transform, diagnosing transform failures on a specific input, or validating transforms against known-good baselines. Runs augmentation pipeline and reports pass/fail per transform.
Autonomously improve a generated paper via REVIEWER_MODEL (default o3) xhigh review → implement fixes → recompile, for 2 rounds. Use when user says "改论文", "improve paper", "论文润色循环", "auto improve", or wants to iteratively polish a generated paper.
Zero-context verification that every bibliographic entry in the paper is real, correctly attributed, and used in a context the cited paper actually supports. Uses a fresh cross-model reviewer with web/DBLP/arXiv lookup to catch hallucinated authors, wrong…
Paper citation and claims verifier. Use before submitting a paper, after major eval runs that change numbers, or when reviewing a paper draft. Traces every numeric claim in the paper to a result JSON on disk; flags UNTRACED, MISMATCH, STALE_REF, MISSING_CITE,…
CUDA↔OpenMP translation pattern guide for evaluating and reviewing LLM-generated parallel code translations. Use when reviewing eval results that involve CUDA-to-OpenMP or OpenMP-to-CUDA translation pairs, when writing paper sections about translation…
Evaluation result grading and classification workflow. Use when classifying eval results into pass/fail categories, diagnosing failure patterns in batch results, computing pass rates with proper exclusions, or preparing result tables for papers. Handles the…
Launch a model evaluation batch. Use when running interactive/foreground eval runs — parameter collection, pre-flight checks, execution, and post-run analysis. NOT for: long-running batches that need tmux isolation (use overnight-eval instead).
Generic experiment lifecycle orchestrator with reproducibility tracking and evolution support. Use when running any structured experiment. Integrates with /grill-research (pre-flight), /interpret-results (post-analysis), and /hypothesis-tree (evidence…