プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。Google でログインするとレビューを書けます。プロトタイプ · 30分ごとに更新
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

thinkrail Skill

リポジトリ ↗

作者:JetBrains★ 8,322 (whole repo)12 個の skill

★ 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 コーディング
Maker’s original description
ThinkRail is the agentic IDE that gets better every time you use it
作者向け:README にバッジを付ける

作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。

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

一緒に使える

同じ作業で AI をサービスにつなぐ MCP

REA

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

作者:morluto広く使われている↓ 38.9万/週★ 46.4万6 日前更新

MCP · サービスにつなぐパソコンで動く

Fallow

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

作者:fallow-rs広く使われている↓ 244.1万/週★ 5374昨日更新

MCP · サービスにつなぐパソコンで動く

似た Skill

同じ種類の作業。Skill 一覧と同じ並び

似たものと比べる
これ
thinkrail
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
作者JetBrainsmorlutomultica-aiGraphify-Labsharry0703
Skill 数121111
GitHub スター8,322465,460233,910149,364144,149
最終コード更新2026年11月17日2026年11月17日2026年4月20日2026年11月17日2026年11月17日
ライセンスApache-2.0MIT–Apache-2.0MIT

JetBrains による 12 個の Skill(指示セット)。AI が読んでそのとおりに作業します · 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 2026年11月12日 · 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.

Skill と MCP の違い

MCP = 手

AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。

Skill = 手順書

作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。

重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。

使えるアプリ

CodexCursor

提供元の README と repo のフォルダから判断

インストール

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 ↑

話し合い

質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。

まだ投稿はありません。最初の質問や共有をどうぞ。

ここの投稿は利用者によるもので、PopNx チームのものではありません。

ログインして投稿

GitHub の情報

GitHub スター
8,322
Stars are for the whole repo, not each skill
提供元
JetBrains
ライセンス
Apache-2.0
最終コード更新
2026年11月17日
repo 内の SKILL.md(翻訳版とテンプレートを含む)
12
トピック
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