菜单
Complete belief change architecture — from psychological diagnosis through persuasion engineering to commercial application — based on David McRaney's How Minds Change + Spencer Greenberg interview synthesis
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Farrice/mes-knowledge-base --skill source-command-david-mcraney命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
The /generate front door — in-house, pay-as-you-go creative generation (Higgsfield replacement). One command for image, video, and audio: routes each request to the right model recipe (skills/generate/models/*.json), defers to binding creative_router lanes (people → fal-people, style-family → fantastic-posters; Higgsfield fully retired 2026-08-06), quotes paid video before running, honors prompt-level budgets ("total budget $3"), runs comparison batches across models, logs every prompt beside its asset, and auto-refreshes the Asset Command Center (/assets-board). Use when the user says "generate", "make an image/video/voiceover", "create ads/assets/creative", names a model (recraft, kling, seedance, nano banana, gpt image), or asks for a multi-model comparison. Source: RoboNuggets 9C4TRbucmhQ, rebuilt on our fal-first stack.
The Edit Bay — in-house conversational video studio (VOX-style explainers, documentaries, shorts, LinkedIn video). Transcript-driven cutting, B-roll ladder, motion graphics as code, captions, music, publish-ready packages — all agent-operated, free-first. Use when Farrice says "edit this video/footage", "make an explainer/documentary/short", "cut this recording", "add B-roll/captions/music", "turn this essay/post into a video", or any video production ask. Front door for three modes: talking-head, VO-only, zero-camera (his recorded VO + assembled visuals — NO voice clone, NO TTS narration, his ruling 2026-08-06). Source: Brad Bonanno agentic edit pipeline (extractions/brad-bonanno-edit-bay/), rebuilt on the house stack: WhisperX local + edit_bay.py ffmpeg assembly + HyperFrames/Remotion graphics + /generate (fal) — NO Higgsfield (retired 2026-08-06).
Architects technical explainer videos using Brad Bonanno's structural patterns — survives short attention spans, communicates complete systems (not just teasers), and functions as a channel-building artifact (one video pulls subscribers, not just views). Use when planning a long-form technical explainer (5-20 min) for YouTube, structuring an explanation of a complex system the user knows but can't teach yet, balancing depth vs accessibility for a technical audience, or building an evergreen video meant to compound subscriber growth over years rather than spike then die. Trigger proactively whenever the user says "explainer video", "technical explainer", "how do I explain X", "long-form YouTube", "evergreen video", or has a complex system that needs to land with a non-expert. For Instagram-format shareworthy content use brock-johnson-shareworthy-content; for short-form video patterns use a TikTok/Reels-specific skill.
基于 SOC 职业分类
正在显示 SKILL.md
| name | source-command-david-mcraney |
| description | Complete belief change architecture — from psychological diagnosis through persuasion engineering to commercial application — based on David McRaney's How Minds Change + Spencer Greenberg interview synthesis |
Use this skill when the user asks to run the migrated source command david-mcraney.
Load and embody the skill at skills/david-mcraney-belief-change/SKILL.md. Also load skills/david-mcraney-belief-change/genius.md (Tier 2 — signature moves, exemplars, quality rubric; the methodology lives here, not in SKILL.md). Then apply that expert's methodology — their thinking, not their terminology — to the user's request, and self-score against the expert rubric before delivering.
This skill has runnable processes. Its flagship workflow is skills/david-mcraney-belief-change/workflows/belief-layer-creative-brief.md. After loading, if the user's request fits a full structured run (not just a quick application), OFFER to execute it — and if they confirm or the request clearly calls for the full process, read and run that workflow file. See the skill's 'Available Workflows' table for the other processes.