Explore skills
Showing 15571–15600 of 19983 skills
在需求刚提出时,先挑战它是否该做,写下一条能验证的预期效果,再用模板建飞书需求文档和飞书项目(Meegle)工作项,两边互相链接。Use when someone raises a product or technical requirement, says 提需求 / 我想要 / 能不能加, or before any requirement work starts without a doc and a work item.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodex上线后对照 intake 写下的预期效果收集证据,判断是否达成;没达成就写清差距和下一步;只有拿到证据才关闭需求。Use after the observation window of a shipped requirement, when someone asks 这个需求效果怎么样 / 可以关了吗, or before closing a work item.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodex对一个已受理的需求,对照当前在做的工作(WIP)评估成本、影响、风险,给出排期建议和理由;提出人提建议,负责人拍板。Use after req-intake, at backlog grooming or sprint planning, or when someone asks 这个需求优先级多高 / 能不能插队.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodex上线前做就绪检查(回滚方案、可观测性、完成定义 DoD),全部有证据后再推进 Meegle 状态或节点。Use before a requirement is deployed or marked done, when someone says 可以上线了吗 / 准备发布, or before transitioning the work item to a released state.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodex按固定节奏跟进进行中的需求,用站会格式记录进展、阻塞和下一步;超过约定时间没有更新的需求要显式标出来,不能悄悄沉下去。Use for daily or weekly requirement check-ins, when asked 这个需求到哪了 / 有没有卡住的, or from a scheduled routine.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexWrite the brief before handing a non-trivial task to an agent or subagent, covering stakes, your own hypothesis, goal and scope in your words, what "verified" will mean, and whether the agent is thinking with you or for you. Use before starting a MiniMax Code session, spawning a subagent, or delegating a PR, analysis or doc.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexInventory everything an agent injects into each request besides the user's message, such as system prompt, environment info, skill list, tool definitions, per-turn context blocks and reminders, and check necessity, frequency, precision, position and prompt-cache impact. Use when reviewing an agent's prompt assembly, chasing low cache hit rates, or trimming per-turn overhead.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexUse when writing, rewriting, or reviewing PR/CL descriptions, commit messages, or code-change summaries that explain what changed and why. TRIGGER on "write PR description", "improve this commit message", "summarize this diff", "CL description", "change description", or "make this PR/CL description easier to review". DO NOT TRIGGER for code review, PR splitting, code restructuring, user-facing changelogs, or reviewer replies unless the requested output is a change description.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexUse when reviewing code, pull requests, patches, CLs, diffs, or proposed implementations for engineering quality, code health, design, functionality, tests, maintainability, specialist risk, or approval risk. TRIGGER on "review this PR", "code review", "LGTM?", "approve?", "is this code/diff/change safe to merge/deploy?", and local diff reviews. DO NOT TRIGGER for PR descriptions, PR splitting, author review-feedback responses, or non-code safety questions unless code review is requested.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexUse when a code hotfix, rollback alternative, production/security/legal fix, launch blocker, or hard external deadline claims expedited review or relaxed process. TRIGGER on "emergency change", "hotfix", "prod incident", "major security hole", "must ship today", "hard deadline", "bypass review", or "fast-track this PR" for qualification only. DO NOT TRIGGER for ordinary urgency, soft deadlines, Friday timing, manager pressure, time-zone delay, or review unless emergency status is disputed.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexUse when drafting, rewriting, classifying, or improving code review comments as a reviewer. TRIGGER on rough review notes, requests to make comments clearer or kinder, severity labels, "how should I phrase this review comment?", "write review comments", author pushback, or turning findings into PR comments. If role is unclear, ask reviewer or author. DO NOT TRIGGER for full code review, PR descriptions, or author responses unless wording is requested.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexUse when handling code review feedback as the change author, addressing reviewer comments, drafting replies, resolving disagreements, or summarizing updates. TRIGGER on "address review feedback", "respond to this review comment", "reviewer asked", "I disagree with reviewer", "what should I reply?", or "apply PR comments". If role is unclear, ask reviewer or author. DO NOT TRIGGER for reviewer comment writing, full code review, or PR descriptions unless author-response behavior is requested.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexUse when planning, splitting, shrinking, or sequencing large features, refactors, migrations, or pull requests into small reviewable PRs or CLs. TRIGGER on "split this PR", "this diff is too large", "stacked PRs", "change sequence", "reviewable chunks", "migration plan", "how should I break this up?", or implementation scope too broad for one review. DO NOT TRIGGER for full code review, PR description writing, or tiny one-file edits that already form one self-contained change.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexReview an agent's finished work by reading the evidence before its summary, naming what each check proves and what it misses, pulling out the decisions it made silently, and trying to falsify the result before accepting it. Use when a MiniMax Code session, subagent or cloud agent reports a task done, before merging its PR or acting on its analysis.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexWrite a hand-off document so a fresh session or another person can continue the current task without the chat history. Use when switching tasks, after several compactions, before clearing a session, or when asked to write a handoff, brief, or progress doc.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexRun a harness change as a controlled experiment, with a small end-to-end eval, one change at a time, repeated runs, and looking at flipped tasks, request count, tokens and cache hits, not just the average score. Use before and after changing prompts, tools, skills, subagent layout, compaction or other agent scaffolding, or when asked whether a change helped.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexReview a code change from a clean context, the way an outside reviewer would. Use after the agent finishes an implementation, before merging, or when asked for an independent or second-opinion review of a diff.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexAudit how an agent harness runs long shell commands, covering foreground wait limits, moving to background without re-running, timeouts, completion notification, polling, output size, cleanup and behaviour after compaction. Use when building or reviewing an agent's shell or background-task tool, or when an agent hangs on dev servers, long builds or test runs.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexCheck how an agent or a working session handles long conversations, covering tool-result clearing, compaction, what gets written to files, when to start a new session, and how memory is scoped. Use when a long session starts forgetting constraints, after several compactions, or when reviewing an agent's compaction and memory design.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexCheck whether finished agent work is piling up faster than we can stand behind it, and fix that by tightening automatic checks or running fewer parallel sessions instead of starting another one. Also checks that multi-agent chains read original sources, and which skills we are letting go. Use before launching another parallel session or subagent batch, at the end of a day with many agent PRs, or in a weekly review.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexDecide whether a piece of work should go to a subagent or stay in the main agent loop. Use before spawning subagents, when designing a multi-agent architecture, or when auditing an existing set of subagents for merging back.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexTurn a review correction we keep making on agent output into something that runs on its own, a test, lint rule, hook, CI step or project rule, so the miss does not come back next session. Use when we keep correcting agents on the same mistake (import order, naming, a forbidden API, a missing test), when the same review comment shows up on a second PR, or after a review finds a miss that a check could have caught.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexAudit how much context an agent's tools consume, through tool definitions and tool results, and decide whether to trim the catalog, add tool search, or add programmatic tool calling. Use when an agent has many tools or MCP servers, picks the wrong tools, or burns context on tool output.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexReview how an agent reached its result, not only whether the result passed, covering tools called, detours, unverified assumptions and wasted round trips, and turn the findings into concrete harness or prompt fixes. Use after an agent task finishes or fails, when an eval task flips, or when asked to look at the process behind a result.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexBuild Keynote-style Magic Move slide decks as one offline 1920×1080 HTML file: every slide is an architecture / flow diagram seen through a camera, and the elements two slides share morph and fly instead of cross-fading. Four visual styles (hand-drawn, minimal, dark neon, neo-brutalist): the agent first renders one sample slide in each style, the user picks one, then the whole deck is built in that style. Also exports 4K / 1080p video. Use for 做演示 / 做 slides / 做 PPT / Magic Move / 神奇移动 / 架构图演示 / 技术分享 deck / 动画 slides / animated architecture walkthrough. Not for bullet-point decks or a single static diagram.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodexReplace with one sentence on what this skill does, then when the agent should use it. The agent decides whether to load the skill from this line, so be specific.
MiniMax-AI/mcode-stack
Stars: 725Claude CodeCodex华尔街式的财经/科技解读短片(1–3 分钟、16:9,风格学自小Lin说),两种模式按有没有真人视频自动选:用户给了口播视频(真人或数字人,一个机位)就走真人口播模式——她是片子的"地面",证据挂到她身后的墙上、关键词她身后换成织物舞台和巨字、讲证据时缩进圆窗或竖窗再长回全屏;没给就走无人动效包装模式——当事人实拍抠像站在巨字前面。两种模式共用:真实的人、新闻原文和官方画面作证据,图形(照片圆盘、金色大数字、柱子、图表、金价线、因果链)只演钱和关系,细斜纹深蓝织物底,克制的 2.5D,每一镜接住上一镜。模板档(镜头表 + render.mjs --check 自检)和手写档。工具:找片下片、新闻截图和荧光笔、逐帧抠像、口播逐字对齐、配音时间线、逐帧渲染、合成音效、混音。用户说"wallstreet-explainer""wallstreet-presenter""像《AI到底有多烧钱》那样""做一条财经/科技解读""真人口播财经""小Lin说那种""我有口播视频,帮我包装成财经解读""把一笔账讲清楚"时使用。
HeyChengC/wallstreet-explainer
Stars: 720Claude CodeCodex分析单篇、系列、周度或月度自媒体数据并形成可执行复盘。用于读取平台后台截图、CSV、表格、公开链接或用户提供的数据,计算关注效率和深度互动,比较同平台基线,归因选题、标题、封面、开头、结构、发布时间、标签和行动,并输出加码、改包装、再适配、停止或继续收集样本的决策。
yanhua1010/self-media-content-workflow
Stars: 711Claude CodeCodex为单篇或多平台自媒体创作澄清需求并生成可确认的创作简报。用于用户只给一句话选题、一个链接、一份素材、一个产品或模糊创作要求,需要确认目标受众、内容目标、核心判断、角度、深度、调性、证据、禁区和平台差异时。纯数据分析、已确认方向后的改稿和细节微调不使用此 Skill。
yanhua1010/self-media-content-workflow
Stars: 711Claude CodeCodex将自媒体创作里程碑保存成文件,管理版本、核验路径、生成完整发布包并更新内容索引。用于保存平台第一版完整成稿、多平台合集、短视频脚本、分镜、定稿、发布包和复盘报告,或用户说“保存一下、整理交付、归档、生成发布清单”时。标题微调、删一句和临时候选不单独保存新版本。
yanhua1010/self-media-content-workflow
Stars: 711Claude CodeCodex