MCPInstall

thermos

Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug/security and code-quality branch audits.

Installs
2.2K
Last 24h
+9
Trending rank
#8962
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/cursor/plugins --skill thermos
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads thermos automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Thermos

Run the two thermo review passes as async background subagents in parallel, then synthesize their results.

Workflow

  1. Determine the review scope from the user request, PR, current branch, or relevant changed files.
  2. Gather the diff and any file/context excerpts needed for reviewers to evaluate the change without guessing.
  3. Launch both subagents in the same message with run_in_background: true:
    • subagent_type: "thermo-nuclear-review-subagent" for bugs, breakages, security, devex regressions, feature-flag leaks, and other branch-audit risks.
    • subagent_type: "thermo-nuclear-code-quality-review-subagent" for maintainability, structure, file-size growth, spaghetti, abstractions, and codebase-health risks.
  4. Pass each subagent the same scoped diff/file context and ask it to return prioritized findings with file references and evidence.
  5. After both finish, synthesize the results with findings first, deduplicated across reviewers. Weight overlapping findings more heavily, resolve disagreements with your own judgment, and keep summaries brief.

If individual background summaries are already visible to the user, do not restate them wholesale. Surface the unified verdict, the highest-signal findings, and any remaining uncertainty.

FAQ

What does the thermos skill do?

Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug/security and code-quality branch audits.

How do I install thermos?

Run npx skills add https://github.com/cursor/plugins --skill thermos in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/thermos/ (personal) or .claude/skills/thermos/ (project).

Which AI agents can use thermos?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is thermos safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains thermos?

It is published by cursor in cursor/plugins. It has 2,156 recorded installs.

More from cursor/plugins

View all →

unslop

cursor/plugins

Cut AI tells from any writing.

Docs & Writing28.3K installs

Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.

deslop

cursor/plugins

Remove AI-generated code slop and clean up code style

9.4K installs

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

how

cursor/plugins

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.

blast-radius

cursor/plugins

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.

Docs & Writing5.9K installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.