How to use AI skills to get daily briefings, weekly accountability, priority triage, and a strategic sounding board that has no agenda. Setup takes 30 minutes.
Your inbox lives in Gmail. Your calendar is in Google Calendar. Your tasks are split between a notes app and a tool your team uses that you check reluctantly. Slack has notifications you're ignoring. Your actual priorities, the ones that determine whether this quarter succeeds, live exclusively in your head.
No tool currently has the full picture. And the cognitive overhead of maintaining it mentally, session after session, meeting after meeting, compounds into a kind of strategic fog: you know what matters, but you spend most of your time on what's in front of you rather than what's most important.
A real chief of staff solves this. They hold context across everything: your priorities, your key decisions, your commitments, the things you said you'd follow up on three weeks ago. They brief you before you walk into the room. They ask the question that challenges your assumption before you make the call. They don't let important things disappear into the operational noise.
AI skills can replicate this function. Not the relationship, not the presence, not the judgment that comes from a decade of working alongside you. But the context-holding, the briefing, the decision support, and the accountability structure. Here's how to build one.
Why This Is Different From Asking AI for Help
The failure mode of executives who try to use AI and conclude it's not useful for them: they open a chat window, explain their situation from scratch, get a generic response, and close the tab. The problem isn't the AI. It's that a cold session with no context produces cold output.
A skill works differently. The CLAUDE.md file holds your standing context permanently: your priorities for the quarter, your decision-making style, your key stakeholders, your constraints, your current open questions. Every session starts with Claude already knowing what you're working on and what matters to you. You don't brief it. It briefs you.
Generic AI chat: "I'm a CEO of a 60-person B2B SaaS company. We have a board meeting next week and I'm trying to decide whether to raise a bridge round or push for profitability. Here's the context: [ten minutes of explaining]..."
With an AI Chief of Staff skill: "Board meeting is Thursday. Help me think through the bridge vs. profitability decision." Claude already knows: company stage, burn rate, board dynamics, your stated Q3 priorities, and that you've been leaning toward profitability for two months. The answer is immediately useful.
The setup takes 30 to 45 minutes once. After that, every session starts from a complete picture.
Skill 1: Executive Chief of Staff (The Daily Operating Layer)
This is the skill you open every morning and every time you need to think through something quickly. It knows your role, your company context, your team, your current priorities, and your preferred communication style. It functions as a persistent operating layer, not a one-off assistant.
Morning briefing. Start the day with a structured brief: what's on today's calendar, what decisions are pending, what you said you'd follow up on, and what the one highest-leverage thing is to accomplish before anything else. Takes two minutes. Replaces the fifteen minutes of context-assembly that used to happen in your head while reading emails.
Pre-meeting prep. Before any significant meeting, ask for a quick brief: the person's background, the relevant context from previous interactions, what you want to get out of it, and what you should be careful about.
Priority triage. When the inbox is full and everything appears urgent, paste in the list of demands on your attention and ask for a prioritized view: what genuinely moves the needle vs. what feels urgent but isn't, what you should do, delegate, defer, or decline.
Communication drafting. Board updates, all-hands memos, investor emails, difficult conversations with direct reports. The skill knows your voice and your context. It drafts in your register, not a generic corporate register.
"Brief me for today. What's on my calendar, what decisions have I been deferring, and what's the one thing I should make sure happens today?"
"I have 12 things in my head that need attention this week. Here they are: [list]. Prioritize them and tell me what the top three actually are, and why."
"Draft my Friday all-hands update. Key news this week: [bullets]. Tone: direct and honest, no corporate softening. Under 300 words."
Skill 2: Chief of Staff Check-In (The Weekly Accountability Rhythm)
The daily skill handles operations. This skill handles the weekly strategic rhythm: the structured review that most executives know they should do and rarely do consistently.
A real chief of staff runs this meeting with you. They bring the list of commitments you made last week, hold you accountable to what didn't get done, surface the pattern of what keeps slipping, and ask the uncomfortable question about whether the current week's plan is actually aligned with the quarter's priorities.
The skill replicates this structure: a weekly session that reviews what you committed to, what actually happened, what's blocking progress on what matters most, and what the adjusted plan is for the coming week. It asks the hard questions. It doesn't let you reframe a missed commitment as a strategic pivot without justification.
"Weekly check-in. Last week's commitments: [list]. What happened: [list]. Run the review. What got done, what slipped, what's the honest explanation, and what am I going to stop saying I'll do if I keep not doing it?"
"I've now deferred [specific initiative] three weeks in a row. What are the possible explanations for that, and what should I actually do about it?"
The second prompt (asking directly about a pattern of deferral) is where this skill produces its highest-value output. Most executives have a persistent item they keep moving. The skill will name the possible explanations honestly: it's not actually a priority, you're avoiding a difficult conversation it requires, you don't have enough information to decide, or it's someone else's job and you haven't delegated it clearly. That kind of direct challenge is hard to get from most people in your organization.
Skill 3: CEO Advisor (A Strategic Sounding Board Without an Agenda)
The loneliness-at-the-top problem is real and structural. Everyone in your organization has a stake in your decisions. Your board has its own interests. Your investors are aligned in some ways and misaligned in others. The person who can tell you you're wrong, without any skin in the game, is genuinely rare.
This skill fills a specific gap: a sounding board that knows your company deeply, has no stake in your decisions, and is designed to challenge your assumptions before you commit. It doesn't tell you what you want to hear. It applies structured strategic frameworks (pre-mortem analysis, second-order thinking, devil's advocate) and pushes back on reasoning that isn't solid.
"I'm leaning toward [strategic decision]. Challenge my reasoning. What am I not seeing, what assumptions am I making that could be wrong, and what does the bear case look like if I'm wrong about the key variable?"
"Run a pre-mortem on this decision. Assume it's two years from now and this choice turned out to be a significant mistake. What are the three most likely explanations for why it went wrong?"
"I'm about to have a difficult conversation with [person/board/investor]. Steel-man their position for me. What's the strongest version of the argument I'm going to hear, and what are the points I genuinely can't counter?"
The pre-mortem and steel-man prompts are the highest-leverage uses. They produce the kind of thinking that usually requires an experienced board member or advisor who knows your situation well enough to push on the specific weak points, not generic strategic advice.
Building Your Executive CLAUDE.md
The quality of your AI Chief of Staff is directly proportional to the quality of the context you give it. Here's the template:
# Executive Context
## Role & Company
[Your title, company, stage, industry, headcount, key metrics]
## Current Quarter Priorities (3 max)
1. [Priority: what success looks like in one sentence]
2. [Priority: what success looks like in one sentence]
3. [Priority: what success looks like in one sentence]
## Key Decisions Currently Open
- [Decision: what it is, what I'm leaning toward, what's blocking resolution]
## Key People & Relationships
[Direct reports, board members, key investors, critical external relationships:
one line each on context that matters]
## Communication Style
[How I write and speak: direct/warm/formal/conversational, anything I always/never do]
## My Decision-Making Tendencies (honest version)
[What I tend to over-weight, what I tend to under-weight, biases I'm aware of]
## Current Constraints
[Budget, headcount freeze, board-level mandates, anything I'm working around]
## Last Updated
[Date: review monthly or when major context changes]
Two sections deserve particular attention. Key Decisions Currently Open is what most executives forget to include and what produces the most immediate value. When your CoS skill already knows what you're wrestling with, every relevant conversation and piece of information gets filtered through that lens automatically.
My Decision-Making Tendencies is uncomfortable to write but disproportionately valuable. If you know you tend to over-weight recency bias in people decisions, or that you historically under-invest in operational details when you're excited about strategy, encoding that gives your advisor skill the specific angles to challenge you on. A generic AI will give you generic pushback. One that knows your specific failure modes will ask the right questions.
A Practical Daily and Weekly Routine
Daily (10 minutes):
- Morning: open the Chief of Staff skill. Get the day's brief: priorities, pending decisions, calendar context, one highest-leverage task.
- Before any high-stakes meeting: ask for a quick context brief.
- When inbox overflows: paste threads in for triage and draft replies.
- After any significant meeting: paste notes for structured decisions, owners, next actions, and a follow-up draft.
- Before major decisions: open the CEO Advisor. Run a pre-mortem, steel-man the opposition, and have your assumptions challenged before you commit.
Weekly (30 minutes):
- Open the Chief of Staff Check-In. Review last week's commitments, hold yourself accountable on what slipped, set the top three for the coming week.
What an AI Chief of Staff Doesn't Replace
Being precise about the limits matters.
Real relationships and trust. A human CoS builds relationships with your team, reads the room in a board meeting, and earns political capital on your behalf. The AI skill does none of this. It's a cognitive tool, not an organizational actor.
Real-time information. Claude Code runs locally and reads files you provide. It doesn't monitor your inbox, listen to your meetings, or pull live data. You bring information to it. It doesn't gather it autonomously.
Execution and follow-through. The AI Chief of Staff advises, drafts, and organizes. It doesn't send emails, book meetings, or ensure your direct reports actually do what was decided. Execution still requires humans.
Within those limits, the AI Chief of Staff is most powerful for executives who have the judgment and capacity to act on good input, but who are currently constrained by the friction of context-assembly and the scarcity of advisors who can give them genuinely independent pushback. That's most senior leaders, most of the time.
Getting Started
Build your CLAUDE.md this week. Thirty minutes, no coding, just writing down what's already in your head. Use the Executive Chief of Staff skill for one morning brief. If it produces something useful from your first prompt, you'll know within five minutes whether this is worth building out further. Most executives who try it do.
I publish all three core skills (plus supporting skills for inbox triage, meeting intelligence, decision matrices, and executive dashboards) as free, downloadable templates at claudecodehq.com. Each one is a single file you drop into a folder. No coding, no subscription, no IT ticket.
Originally published on claudecodehq.com
Top comments (0)