REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
This repo is a collection of 25 skills
Workflow fluency for AI coding agents. 1 core skill · 25 commands · 7 domain references · memory layer · audit trail — works across Cursor, Claude Code, Gemini CLI, Copilot, and 6 more.作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/sharpdeveye-maestro)同じ作業で 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 一覧と同じ並び
| これ maestro | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | sharpdeveye | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 25 | 1 | 1 | 1 | 1 |
| GitHub スター | 603 | 463,670 | 233,682 | 148,887 | 143,987 |
| 最終コード更新 | 2026年4月29日 | 2026年11月17日 | 2026年4月20日 | 2026年11月17日 | 2026年11月16日 |
| ライセンス | MIT | MIT | – | Apache-2.0 | MIT |
sharpdeveye による 25 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
Install only the ones you use. Open a skill to see how to install it
If you want every one, let the AI install them in one go. Know 2 things first
Uploading to Claude on the web and apps: you need 25 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
Use when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.
Use when porting a workflow to a different AI provider, deployment environment, model tier, or organizational context.
Use when any Maestro command is invoked — provides foundational workflow design principles across prompt engineering, context management, tool orchestration, agent architecture, feedback loops, knowledge systems, and guardrails.
Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
Capture a session summary — what was done, what decisions were made, and what to do next.
Use when the workflow needs multi-step processing with sequential, parallel, or conditional tool compositions and proper data flow.
Use when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.
Use when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.
Use when the agent needs access to information beyond its training data — knowledge sources, RAG pipelines, or grounding data.
Use when the user wants a quality review, interaction audit, or to test the workflow against realistic scenarios.
Use when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.
Use when the workflow lacks error handling, has been failing in production, or needs retry logic, fallback strategies, and circuit breakers.
Use when deploying to production, handling sensitive data, or the workflow needs safety constraints, input validation, and security boundaries.
Use when the workflow needs to self-correct, improve over time, or establish feedback loops and evaluation cycles.
Use when starting a new project, adding a new agent to an existing system, or setting up workflow infrastructure from scratch.
Quick summary of the last session — commands run, files changed, and what to do next.
Use when the workflow works but needs polish, or as the final step in a diagnose → fix → refine cycle before shipping.
Analyze command history to identify which skills work, which fail, and where to improve.
Use when the user wants to tailor a workflow for a specific industry, domain, or vertical with specialized expertise, terminology, and guardrails.
Use when the workflow feels too complex, has accumulated cruft, or has redundant steps and overlapping tools that need consolidation.
Use when starting a new project with Maestro or when no .maestro.md context file exists yet. Run once per project.
Use when the workflow feels over-engineered, has premature optimizations, unnecessary abstraction layers, or complexity beyond actual requirements.
Use when the user wants to push past conventional workflow limits with advanced performance techniques like parallel orchestration, streaming pipelines, or adaptive routing.
Use when you need maximum precision on a critical task — production deployments, security-sensitive code, financial calculations, or any work where mistakes are unacceptable.
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
Claude CodeClaude (เว็บ/แอป)CodexCursorGemini CLIGitHub CopilotOpenCodeKiro
提供元の README と repo のフォルダから判断
This repo has 25 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP
もう入っていますか?先に確認 · ターミナルを開き、このコマンドを入力して Enter
node -vMac:⌘ + Space を押し、Terminal と入力して Enter
Windows:スタートメニューを開き、Windows PowerShell と入力して「開く」
まだ入っていない場合: 公式ダウンロードページで LTS 版と、クリックで進むインストーラーを選びます:Mac は .pkg、Windows は .msi。ダブルクリックして最後まで進めるだけで、curl コマンドは不要です
入れ終わったらターミナルを閉じて開き直し、同じコマンドをもう一度実行します。バージョン番号が出れば完了です: node -v
一度入れれば、Node.js を使うすべてのツールで使えます
コマンドを確認中 · 確認が通るとコピーボタンが出ます
提供元の README から引用。提供元のコードをダウンロードして実行します
質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。