跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

help

Use when the user asks what MasterMind can do or how to drive it: "help", "what can you do", "how do I use this", "what commands are there", "list your skills", "what are my options": or when they seem unsure how to get started.

mehrad-dm · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add mehrad-dm/mastermind --skill help

技能说明


name: help description: Use when the user asks what MasterMind can do or how to drive it: "help", "what can you do", "how do I use this", "what commands are there", "list your skills", "what are my options": or when they seem unsure how to get started.

Help: what MasterMind can do, and how to use it

Present this as a clear, friendly menu (adapt length to the ask). Open with the brand header, then lead with the one thing that matters most, then the tables. Keep it scannable. Header:

🧠  MasterMind: a genius-builder brain for your AI
    24 skills · 4 agents · Claude Code · Cursor · Codex

Lead with what fits this project

Before the full menu, name up to three skills that would earn their keep here right now, each with the reason it applies: read from what's actually in front of you (the stack, the current task, what the last few turns were about, whether a field pack exists yet):

Most useful here right now
  · init: no field pack yet for this Django project; one-time setup, then I'm sharper on it
  · quarantine: there's client data in this repo; this keeps it out of git
  · handoff: this session is long; a handoff survives the reset

A full menu is a catalogue; three fitting picks are advice. Then give the tables below: the catalogue still matters, because the point is that the user learns what they already own.

The one rule: you don't run commands: you just talk

MasterMind works by recognizing intent. Say what you want in plain language and it applies the right skill or agent itself, then shows a short note that it did (e.g. 🧠 MasterMind ▸ building this, will verify before handoff, with └ build · design → implement → verify beneath it). The /name calls below are an optional shortcut: a way to force a specific skill, not something you need to memorize. Every skill is Auto (the model can invoke it); you can also call any of them by hand.

Skills: the workflows (all Auto-invocable)

SkillWhat it doesFires automatically when…Call it by hand
initset MasterMind up for this project: detect the stack (or ask what you're building), load the field packyour first real task in a project it isn't set up for"init" · "set up MasterMind"
builddesign → implement → verify → review → capture, end to endyou ask to build/add/implement a non-trivial feature"build a search box for the header"
debugstructured, evidence-first root-cause debugginga bug is hard, weird, or keeps coming back"debug why the list doesn't refresh"
performancemeasure → find the real bottleneck → fix the biggest → verifysomething's slow or janky ("why is this slow?")"why is this page so slow?"
qaprove a change works by driving it for real (+ optional tests)you finish something / ask to test it"qa this" · "write tests for it"
reporta shareable write-up of a cycle: changed files, decisions, verification, verdict (MD default, HTML on request)you ask for a report; or end of build/qa if you turned it on (off by default)"give me a report of this" · "reports on"
interviewturn a fuzzy ask into a crisp, buildable specthe request is ambiguous or spans many files"spec out the checkout flow first"
routeload only the files/skills a task actually needsa task is non-trivial or you're unsure where to start"route this"
learnget up to speed fast on an unfamiliar stack/API, verify assumptionsthe tech is new, fast-moving, or you're guessing"learn how the Stripe API handles refunds"
prototypebuild a throwaway spike to learn, then rebuild properlythe right approach is genuinely unknown"spike a quick prototype of this"
signaturecapture your team's real conventions as durable rules it followsyou ask it to match your codebase / keep correcting the same thing"make it match our patterns"
personawrite in the documented public style of a named engineer, citedyou ask for someone's style ("write like X")"write this like Kent C. Dodds"
explainwrite AI-friendly usage docs beside an internal packagean internal package has little/no docs (asks first)"explain this package"
promptsharpen a vague prompt into a precise, AI-ready oneyou ask to optimize/fix a prompt for an AI"improve this prompt"
quarantineset up a private, gitignored quarantine for confidential databefore capturing project/client-specific notes"set up a lab here"
levelupimprove MasterMind's own knowledge (lessons, curriculum, new field)after a correction/review, or to refresh standards"levelup: remember this"
double-checkinterrogate a claim before handing it over: adversarial, reviewer never sees your conclusionyou're about to say "it works", or a review came back suspiciously clean"doubt this"
deprecateremove/migrate/retire safely: expand → migrate → contractdeleting a feature, column, flag, or endpoint"can we delete this?"
roadmapa durable decision map for multi-week workwork spanning many sessions; "why did we decide X?""map this project"
lintcheck MasterMind's own files for bloat, repeated rules, contradictionsbefore a release, or the brain feels bloated"lint the brain"
clarifyre-pitch an answer that did not land, in plain words or as a pictureyou say "I did not follow that", "simpler", "you lost me""say that simply"
deepensurvey an area and rank where the design costs most, you pick one"this is getting messy", "why is this so hard to change?""where is this hurting?"
handoffwrite a concise handoff so work survives a reset/teammatebefore a long-task /clear, pausing, or handing off"write a handoff"
helpshow this menu, what every skill/agent does and
阅读完整来源 ↗