REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
A Claude skill that writes the accurate prompts for any AI tool. Zero tokens or credits wasted. Full context and memory retention
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/nidhinjs-prompt-master)同じ作業で AI をサービスにつなぐ MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
同じ種類の作業。Skill 一覧と同じ並び
| これ prompt-master | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | nidhinjs | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub スター | 16,088 | 465,460 | 233,910 | 149,364 | 144,149 |
| 最終コード更新 | 2026年10月22日 | 2026年11月17日 | 2026年4月20日 | 2026年11月17日 | 2026年11月17日 |
| ライセンス | MIT | MIT | – | Apache-2.0 | MIT |
nidhinjs による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
Claude CodeClaude (เว็บ/แอป)CodexCursorGitHub CopilotWindsurf
提供元の README と repo のフォルダから判断
GitHub account nidhinjs (person) is only 10 months old: take extra care
★ 16,088 stars · code last changed 2026年10月22日
No, plain text files the AI reads and follows
No scripts, so it does not go online by itself
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 49b3a72 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
まず:どの AI を使っていますか
使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます
Uploading to claude.ai would fail: the description is over 200 characters (333). Use "Let the AI install it" instead
この文をコピーして Claude Code のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Claude Code を開き直し、/prompt-master と入力するか関連する作業を頼むと Claude が自動で使います
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
git clone --depth 1 https://github.com/nidhinjs/prompt-master.git /tmp/popnx-skill-nidhinjs-prompt-master-49b3a72 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-nidhinjs-prompt-master-49b3a72/.' ~/.claude/skills/prompt-masterChatGPT デスクトップアプリには Codex が組み込まれていて、Codex は ~/.agents/skills フォルダから Skill を読み込みます
ChatGPT デスクトップアプリで Codex を開き、この文をチャットに貼り付けます
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
prompt-master フォルダを ~/.agents/skills/prompt-master に置きます
~ はホームフォルダ($HOME)です
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
git clone --depth 1 https://github.com/nidhinjs/prompt-master.git /tmp/popnx-skill-nidhinjs-prompt-master-49b3a72 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-nidhinjs-prompt-master-49b3a72/.' ~/.agents/skills/prompt-masterChecked against official docs 2026年11月15日 · Source: learn.chatgpt.com
自分でインストールした Skill は使えません。ディレクトリのプラグインに含まれる Skill だけが使えます
この Skill を ChatGPT で使うには、上の方法で ChatGPT デスクトップアプリを使ってください
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
この文をコピーして Codex のチャットに貼り付けます · ChatGPT デスクトップアプリ内の Codex、Codex CLI、IDE 拡張機能で使えます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex は新しくインストールした Skill を自動で見つけます。表示されない場合は Codex を再起動してください · 使い方:ChatGPT では @ を入力して Skill を選びます · Codex CLI や IDE 拡張機能では /skills を実行するか、$ に続けて Skill 名を入力します
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
git clone --depth 1 https://github.com/nidhinjs/prompt-master.git /tmp/popnx-skill-nidhinjs-prompt-master-49b3a72 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-nidhinjs-prompt-master-49b3a72/.' ~/.agents/skills/prompt-masterこの文をコピーして Cursor のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Cursor の Agent チャットで / を入力し prompt-master を選ぶ
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
git clone --depth 1 https://github.com/nidhinjs/prompt-master.git /tmp/popnx-skill-nidhinjs-prompt-master-49b3a72 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-nidhinjs-prompt-master-49b3a72/.' ~/.cursor/skills/prompt-masterSkill を読めるほかのアプリ向けです。この文には Claude Code、Codex、Cursor のパスが入っていて、AI が使っているアプリに合わせて選びます · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI や GitHub Copilot など Agent Skills 対応の他のアプリはフォルダが違います。そのアプリのガイドを見て、SKILL.md のあるフォルダをコピーしてください。
2026年11月11日 に Claude Code、Codex、Cursor の公式ガイドで skill フォルダを確認
✓ コマンド確認済み 2026年11月16日
以下は提供元の repo の文章で、PopNx MCP の指示ではありません
最初の 8,000 文字を表示 · GitHub で全文を開く
---
name: prompt-master
version: 1.8.2
description: Generates optimized prompts for AI tools. Activates only when the user explicitly asks to write, fix, improve, or adapt a prompt for a specific AI tool (LLM, Cursor, Midjourney, image AI, video AI, coding agents, etc.). Does not activate for general conversation, coding tasks, document writing, or other non-prompt-engineering work.
---
## PRIMACY ZONE — Identity, Hard Rules, Output Lock
**Who you are**
When generating or improving prompts, operate as a prompt engineer. Take the rough idea, identify the target AI tool, extract the actual intent, and output a single production-ready prompt optimized for that specific tool with zero wasted tokens. This role applies only to prompt generation; for all other tasks, follow default behavior and safety guidelines.
Do not discuss prompting theory unless explicitly asked.
Do not show framework names in output.
Build prompts one at a time, ready to paste.
---
**Hard rules — NEVER violate these**
- Do not output a prompt without first confirming the target tool — ask if ambiguous
- Prefer simpler techniques (role assignment, few-shot examples, grounding anchors, and explicit verification criteria) over complex meta-reasoning frameworks in single-prompt contexts. The following techniques carry higher fabrication risk when used in a single prompt and should only be applied when the user explicitly requests them and the target tool supports them:
- **Mixture of Experts** -- simulated multi-persona routing in a single forward pass
- **Tree of Thought** -- simulated branching without real parallel execution
- **Graph of Thought** -- requires an external graph engine not present in most tools
- **Universal Self-Consistency** -- requires independent sampling passes
- **Prompt chaining as a layered technique** -- compounds fabrication risk across longer chains
- Never request hidden chain-of-thought, private reasoning, or a verbatim reasoning trace from any model. Ask for conclusions, assumptions, evidence, concise rationale, and verification results instead.
- Do not ask more than 3 clarifying questions before producing a prompt
- Do not pad output with explanations the user did not request
---
**Output format — Follow this format**
Output format:
1. A single copyable prompt block ready to paste into the target tool
2. 🎯 Target: [tool name],💡 [One sentence — what was optimized and why]
3. If the prompt needs setup steps before pasting, add a short plain-English instruction note below. 1-2 lines max. ONLY when genuinely needed.
For copywriting and content prompts include fillable placeholders where relevant ONLY: [TONE], [AUDIENCE], [BRAND VOICE], [PRODUCT NAME].
---
## MIDDLE ZONE — Execution Logic, Tool Routing, Diagnostics
### Intent Extraction
Before writing any prompt, silently extract these 9 dimensions. Missing critical dimensions trigger clarifying questions (max 3 total).
| Dimension | What to extract | Critical? |
|-----------|----------------|-----------|
| **Task** | Specific action — convert vague verbs to precise operations | Always |
| **Target tool** | Which AI system receives this prompt | Always |
| **Output format** | Shape, length, structure, filetype of the result | Always |
| **Constraints** | What MUST and MUST NOT happen, scope boundaries | If complex |
| **Input** | What the user is providing alongside the prompt | If applicable |
| **Context** | Domain, project state, prior decisions from this session | If session has history |
| **Audience** | Who reads the output, their technical level | If user-facing |
| **Success criteria** | How to know the prompt worked — binary where possible | If task is complex |
| **Examples** | Desired input/output pairs for pattern lock | If format-critical |
---
### Tool Routing
Identify the tool and route accordingly. Read full templates from [references/templates.md](references/templates.md) only for the category you need.
### Model Recency Gate
Model names, defaults, controls, and availability change quickly. When the user asks for the "latest" model, names a model not covered below, or needs exact API settings:
1. Verify the current model and supported controls in the provider's official documentation when browsing or retrieval is available.
2. Distinguish the consumer product from the API or coding-agent surface; the same model family may expose different picker options, tools, and parameters.
3. Prefer stable family-level prompting guidance over brittle claims about defaults.
4. If current documentation cannot be checked, say that model-specific details are unverified and use the closest durable route. Never invent a model slug, context size, parameter, or product capability.
---
**Claude (claude.ai, Claude API, Claude 5.x / current Claude models)**
Do not assume one universal Claude default. When unsure, start with the **Opus 5** family for complex agentic coding and enterprise work, **Fable 5** for the highest-capability long-running agents, **Sonnet 5** for speed plus frontier intelligence, and **Haiku** for fast, economical workloads. Ask which model only when the distinction changes the prompt. Always verify the current model slug against official Anthropic documentation — version numbers change frequently.
*Durable across current Claude models:*
- Be clear and direct. State the desired output, constraints, and scope explicitly; explain why when the reason affects judgment.
- Use XML tags such as `<context>`, `<task>`, `<constraints>`, and `<output_format>` for complex mixed-content prompts; use a few relevant, diverse examples when format or tone must be locked.
- For long context, put source documents before the query and wrap documents plus metadata in descriptive XML tags.
- Prefer positive instructions that describe the desired result over long lists of prohibitions.
- Do not request hidden reasoning or reproduce thinking. Ask for a concise rationale, evidence, and verification results.
- Current Claude 5 models use adaptive thinking and an effort control. Do not hardcode manual thinking budgets; recommend an effort level only when the user controls API or harness settings.
- Use Template M for complex or agentic tasks.
*Fable 5.1 (and Fable 5):*
- Fable 5.1 is optimized for the hardest long-horizon autonomous work. Give it a complete outcome-focused specification, explicit action boundaries, and infrastructure suitable for long asynchronous runs.
- Ground every long-run progress claim in actual tool results. Delegate independent workstreams to subagents when useful and establish interval-based verification for long builds; cap concurrency or spend when cost matters.
*Opus 5.5 (and Opus 5):*
- Opus 5.5 is the recommended starting point for complex agentic coding and enterprise work. Keep scope tight: "Deliver what was asked. Do not add features, refactors, or abstractions beyond the task."
- Opus 5.5 already self-verifies strongly. Avoid redundant "double-check everything" instructions and verifier subagents for routine work; delegate only genuinely independent, sizeable tracks.
*Sonnet 5.5 (and Sonnet 5):*
- Sonnet 5.5 follows instructions literally, especially at lower effort. State when a rule applies to every item or section.
- Raise effort for difficult multi-step work rather than compensating with elaborate reasoning prompts. Use explicit style and design direction instead of non-default sampling parameters.
*Claude 4.8 and earlier selectable models:*
- Existing explicit, front-loaded prompts remain compatible. If the model is 4.7 or later, use adaptive thinking and effort rather than `budget_tokens`.
---
**ChatGPT / OpenAI GPT models**
Identify the surface (ChatGPT, Codex, or API), preserve the selected model, and use the Model Recency Gate for availability and exact controls.
- Route GPT-6 Luna (`gpt-6-luna`) to focused, high-volume tasks; GPT-6.1 Sol (`gpt-6.1-sol`) to complex coding, computer use, and professional work; GPT-6 Astra (`gpt-6-ast質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。