Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

thinkrail Skill

Repository ↗

by JetBrains★ 8,322 (whole repo)12 skills

★ Stars are for the whole repo, not each skill

Pick the skill to install

What it does

This repo is a collection of 12 skills

  • Connects Instruction files the AI reads
  • Account or key No key found in README or SKILL.md
  • Category Coding
Maker’s original description
ThinkRail is the agentic IDE that gets better every time you use it
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/jetbrains-thinkrail.svg)](https://mcp.popnx.com/en/skills/jetbrains-thinkrail)

Use together with

MCP servers that connect the AI to services for the same work

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 388.7K/wk★ 466.2KUpdated 6 days ago

MCP · Connects a serviceRuns on your computer

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

by fallow-rsWidely used↓ 2.4M/wk★ 5.4KUpdated yesterday

MCP · Connects a serviceRuns on your computer

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 740.3K/wk★ 10.3KUpdated 6 days ago

MCP · Connects a serviceRuns on your computer

Similar Skills

Same kind of work, ordered like the Skills list

Compared with similar ones
This one
thinkrail
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
MakerJetBrainsmorlutomultica-aiGraphify-Labsharry0703
Skills121111
GitHub stars8,322465,460233,910149,364144,149
Last code changeNov 17, 2026Nov 17, 2026Apr 20, 2026Nov 17, 2026Nov 17, 2026
LicenseApache-2.0MIT–Apache-2.0MIT

12 skills (instruction sets) by JetBrains that an AI reads and follows · not an MCP server

Pick the skill to install

Install only the ones you use. Open a skill to see how to install it

Install the whole set (12)

If you want every one, let the AI install them in one go. Know 2 things first

  • Every installed skill’s description is loaded into every chat. The more you install, the easier it is for the AI to pick the wrong one
  • Some skills duplicate tools the AI already has built in. Installing only the ones you use works better
Where to install
Please install all 12 skills from https://github.com/jetbrains/thinkrail: asking-user-questions, brainstorming, choosing-a-workflow, importing-a-codebase, managing-mcp-servers, setting-up-a-project, shipping-a-pr, spec-graph, starting-a-new-project, todos, writing-specs, writing-workflow-skills, for all my projects, putting each at ~/.claude/skills/<skill name> (in Codex use ~/.agents/skills/<skill name>, in Cursor ~/.cursor/skills/<skill name>). Folders in the repo: asking-user-questions = packages/pi-thinkrail-workflow/skills/asking-user-questions · brainstorming = packages/pi-thinkrail-workflow/skills/brainstorming · choosing-a-workflow = packages/pi-thinkrail-workflow/skills/choosing-a-workflow · importing-a-codebase = packages/pi-thinkrail-workflow/skills/importing-a-codebase · managing-mcp-servers = packages/server/skills/managing-mcp-servers · setting-up-a-project = packages/pi-thinkrail-workflow/skills/setting-up-a-project · shipping-a-pr = packages/pi-thinkrail-workflow/skills/shipping-a-pr · spec-graph = packages/spec-graph/skills/spec-graph · starting-a-new-project = packages/pi-thinkrail-workflow/skills/starting-a-new-project · todos = packages/pi-todos/skills/todos · writing-specs = packages/pi-thinkrail-workflow/skills/writing-specs · writing-workflow-skills = packages/pi-thinkrail-workflow/skills/writing-workflow-skills. First show me every file and tell me whether any has scripts or changes machine settings, then tell me the full path you will install each one to and wait for me to agree.
Please install all 12 skills from https://github.com/jetbrains/thinkrail: asking-user-questions, brainstorming, choosing-a-workflow, importing-a-codebase, managing-mcp-servers, setting-up-a-project, shipping-a-pr, spec-graph, starting-a-new-project, todos, writing-specs, writing-workflow-skills, into the project this chat is open in (at .claude/skills/<skill name>; in Codex use .agents/skills/<skill name>, in Cursor .cursor/skills/<skill name>). Folders in the repo: asking-user-questions = packages/pi-thinkrail-workflow/skills/asking-user-questions · brainstorming = packages/pi-thinkrail-workflow/skills/brainstorming · choosing-a-workflow = packages/pi-thinkrail-workflow/skills/choosing-a-workflow · importing-a-codebase = packages/pi-thinkrail-workflow/skills/importing-a-codebase · managing-mcp-servers = packages/server/skills/managing-mcp-servers · setting-up-a-project = packages/pi-thinkrail-workflow/skills/setting-up-a-project · shipping-a-pr = packages/pi-thinkrail-workflow/skills/shipping-a-pr · spec-graph = packages/spec-graph/skills/spec-graph · starting-a-new-project = packages/pi-thinkrail-workflow/skills/starting-a-new-project · todos = packages/pi-todos/skills/todos · writing-specs = packages/pi-thinkrail-workflow/skills/writing-specs · writing-workflow-skills = packages/pi-thinkrail-workflow/skills/writing-workflow-skills. First show me every file and tell me whether any has scripts or changes machine settings, then tell me the project name and the full path you will install each one to and wait for me to agree.

Uploading to Claude on the web and apps: you need 12 uploads, one ZIP per skill. Open each skill in the list below to download it

Checked against official docs Nov 12, 2026 · Source: support.claude.com, code.claude.com, learn.chatgpt.com, cursor.com

  • asking-user-questions

    Use when composing an ask_user_question round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.

  • brainstorming

    Use before implementing a feature, a change in behavior, or a bug fix — however small. Not for questions, checks, or edits that change no behavior (typos, documentation or configuration only, mechanical refactors).

  • choosing-a-workflow

    Use at the start of new project onboarding, PR lifecycle work including PR checks, or any change to what the product does — a feature, a behavior change, or a bug fix. Not for continuing work already routed to a workflow, non-PR questions, checks, explanations, or edits that change no behavior.

  • importing-a-codebase

    Use when asked to create the initial spec graph for an existing codebase that has source code but no specs. Normally reached via setting-up-a-project.

  • managing-mcp-servers

    Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no `pi` command to call.

  • setting-up-a-project

    Use when asked to set up, onboard, initialize, or spec a project with no spec graph, or when invoked by the app's Set-up-project card. Not for ordinary work in an already-specced project.

  • shipping-a-pr

    Use when finished work needs to ship as a pull request, or when creating, syncing, updating metadata, checking status, monitoring CI, or addressing review comments on a PR. Not for reviewing a PR you are not shipping.

  • spec-graph

    Use when locating, reading, creating, updating, or validating project specs, or when work is governed by or may alter a documented boundary, contract, invariant, behavior, or architecture decision.

  • starting-a-new-project

    Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.

  • todos

    Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.

  • writing-specs

    Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.

  • writing-workflow-skills

    Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.

How a Skill differs from MCP

MCP = the hands

Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.

Skill = the manual

A text file that teaches the AI how to do a task. It connects to nothing.

Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.

Works with

CodexCursor

From the maker’s README and the folders in the repo

Install

Pick a skill first

This repo has 12 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP

Let the AI install it
Upload to claude.ai

Go to the skill list ↑

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

From GitHub

GitHub stars
8,322
Stars are for the whole repo, not each skill
Maker
JetBrains
License
Apache-2.0
Last code change
Nov 17, 2026
SKILL.md files in the repo (including translated copies and templates)
12
Topics
agent, agent-skills, agentic-ai, agentic-workflow, ai-coding, ai-tools, pi-agent, pi-agent-extension, spec-driven, spec-driven-coding, spec-driven-development, vibe-coding