What it does
This repo is a collection of 25 skills
- Connects Instruction files the AI reads
- Account or key Not confirmed yet (README not read yet)
- Category Coding
Maker’s original description
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.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.
[](https://mcp.popnx.com/en/skills/sharpdeveye-maestro)Use together with
MCP servers that connect the AI to services for the same work
Fallow
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
Desktop Commander
MCP server for terminal commands, file operations, and process management
Similar Skills
Same kind of work, ordered like the Skills list
| This one maestro | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Maker | sharpdeveye | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 25 | 1 | 1 | 1 | 1 |
| GitHub stars | 603 | 463,670 | 233,682 | 148,887 | 143,987 |
| Last code change | Apr 29, 2026 | Nov 17, 2026 | Apr 20, 2026 | Nov 17, 2026 | Nov 16, 2026 |
| License | MIT | MIT | – | Apache-2.0 | MIT |
25 skills (instruction sets) by sharpdeveye 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 (25)
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
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 Nov 12, 2026 · Source: support.claude.com, code.claude.com, learn.chatgpt.com, cursor.com
- accelerate
Use when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.
- adapt-workflow
Use when porting a workflow to a different AI provider, deployment environment, model tier, or organizational context.
- agent-workflow
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.
- amplify
Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.
- calibrate
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
- capture
Capture a session summary — what was done, what decisions were made, and what to do next.
- chain
Use when the workflow needs multi-step processing with sequential, parallel, or conditional tool compositions and proper data flow.
- compose
Use when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.
- diagnose
Use when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.
- enrich
Use when the agent needs access to information beyond its training data — knowledge sources, RAG pipelines, or grounding data.
- evaluate
Use when the user wants a quality review, interaction audit, or to test the workflow against realistic scenarios.
- extract-pattern
Use when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.
- fortify
Use when the workflow lacks error handling, has been failing in production, or needs retry logic, fallback strategies, and circuit breakers.
- guard
Use when deploying to production, handling sensitive data, or the workflow needs safety constraints, input validation, and security boundaries.
- iterate
Use when the workflow needs to self-correct, improve over time, or establish feedback loops and evaluation cycles.
- onboard-agent
Use when starting a new project, adding a new agent to an existing system, or setting up workflow infrastructure from scratch.
- recap
Quick summary of the last session — commands run, files changed, and what to do next.
- refine
Use when the workflow works but needs polish, or as the final step in a diagnose → fix → refine cycle before shipping.
- reflect
Analyze command history to identify which skills work, which fail, and where to improve.
- specialize
Use when the user wants to tailor a workflow for a specific industry, domain, or vertical with specialized expertise, terminology, and guardrails.
- streamline
Use when the workflow feels too complex, has accumulated cruft, or has redundant steps and overlapping tools that need consolidation.
- teach-maestro
Use when starting a new project with Maestro or when no .maestro.md context file exists yet. Run once per project.
- temper
Use when the workflow feels over-engineered, has premature optimizations, unnecessary abstraction layers, or complexity beyond actual requirements.
- turbocharge
Use when the user wants to push past conventional workflow limits with advanced performance techniques like parallel orchestration, streaming pipelines, or adaptive routing.
- zero-defect
Use when you need maximum precision on a critical task — production deployments, security-sensitive code, financial calculations, or any work where mistakes are unacceptable.
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
Claude CodeClaude (เว็บ/แอป)CodexCursorGemini CLIGitHub CopilotOpenCodeKiro
From the maker’s README and the folders in the repo
Install
Pick a skill first
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
The maker’s command installs the whole set of 25
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Checking the commands · copy buttons appear once they pass
Copied from the maker’s README; it downloads and runs the maker’s code
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.
From GitHub
- GitHub stars
- 603
Stars are for the whole repo, not each skill - Maker
- sharpdeveye
- License
- MIT
- Last code change
- Apr 29, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 25
- Topics
- agent-orchestration, ai, ai-agents, ai-workflows, claude-code, codex, copilot, cursor, developer-tools, gemini, open-source, prompt-engineering