thiagofernandes1987-create
thiagofernandes1987-create/APEX
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/thiagofernandes1987-create/APEX --skill board-prep命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Token-aware reasoning workflow with real tools: picks an operating mode to control cost, runs a structured pipeline (decompose → validate → verify → snapshot), and gives Claude Program-of-Thought, RK4/Euler, a code gate, and a safe skill router. Use when: multi-step or high-stakes tasks, real math, precise computation, audits, or the user mentions APEX, PoT, pipeline, or scientific mode.
**v00.33.0**: Ingested from antigravity-awesome-skills community repo
run multiple local CLI agents in parallel (separate tmux sessions)
基于 SOC 职业分类
正在显示 SKILL.md
| name | board-prep |
| description | Manage — /em -board-prep — Board Meeting Preparation |
| executor | LLM_BEHAVIOR |
| skill_id | business.c_level_advisor.executive_mentor.board_prep |
| status | ADOPTED |
| security | {"level":"standard","pii":false,"approval_required":false} |
| anchors | ["business"] |
| tier | 2 |
| input_schema | [{"name":"code_or_task","type":"string","description":"Code snippet, script, or task description to process","required":true}] |
| output_schema | [{"name":"result","type":"string","description":"Primary output from board prep"}] |
Command: /em:board-prep <agenda>
Prepare for the adversarial version of your board, not the friendly one. Every hard question they'll ask. Every number you need cold. The narrative that acknowledges weakness without losing the room.
Your board members have seen 50+ companies. They've watched founders flinch at their own numbers, spin bad news as "learning opportunities," and present sanitized decks that hide what's actually happening.
They know when you're not being straight with them. The question isn't whether they'll ask the hard questions — it's whether you're ready for them.
The best board meetings aren't the ones where everything looks good. They're the ones where the CEO demonstrates they see reality clearly, have a plan, and can execute under pressure.
Before the meeting, every number in your deck should live in your head, not just the slide.
The numbers you must know without looking:
Stress test yourself: Can you answer "what's your burn?" without hesitation? "What's your churn rate by segment?" If you pause, you don't know it.
For every item on the agenda, generate the adversarial version of the question.
Standard adversarial questions by topic:
Revenue performance:
Runway / burn:
Product / roadmap:
Team:
Competition:
The board meeting isn't a status update. It's a leadership demonstration.
The structure that works:
The rule on bad news: Never let the board be surprised. If a quarter went badly, they should know before the deck. A 5-sentence email 3 days before: "Revenue came in at $X vs $Y target. Here's what happened, here's what I'm doing, here's what I need from you."
Do a mock board meeting. Have someone play the hardest director you have.
The simulation:
The questions that made you defensive = the questions you need to prepare for.
Not all board members want the same thing from a meeting.
For each director, know:
Common director types:
48 hours before:
Day of meeting:
What the board is watching:
The single best thing you can do: Name the hard thing before they do. "I want to address the revenue miss directly. Here's what happened, here's what I should have caught earlier, here's what changes."
Within 24 hours:
The next board prep starts now.
Manage — /em -board-prep — Board Meeting Preparation
Use this skill when the task requires board prep capabilities.
If this skill fails to produce the expected output: (1) verify input completeness, (2) retry with more specific context, (3) fall back to the parent workflow without this skill.