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의 Skill(지시 묶음) 25개, 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에서 가져온 명령으로, 제작자 코드를 내려받아 실행해요
질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.