Chief Of Staff
alirezarezvani/claude-skills
C-suite orchestration layer. An agent skill from alirezarezvani/claude-skills.
The craft of being a Chief of Staff — gatekeeping, force multiplication, executive briefing, organizational sensing, institutional memory, and meeting/calendar triage.
MITAuto-check passed
Install Chief Of Staff Methodology
$ npx skills add magnus919/hermes-profiles --skill chief-of-staff-methodology -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install magnus919/hermes-profiles chief-of-staff-methodology --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/chief-of-staff-methodology .claude/skills/chief-of-staff-methodology && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "chief-of-staff-methodology" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/chief-of-staff-methodology into .claude/skills/chief-of-staff-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chief-of-staff-methodology", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/magnus919/hermes-profiles/tree/main/skills/chief-of-staff-methodologyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add magnus919/hermes-profiles --skill chief-of-staff-methodology -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install magnus919/hermes-profiles chief-of-staff-methodology --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/chief-of-staff-methodology .agents/skills/chief-of-staff-methodology && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "chief-of-staff-methodology" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/chief-of-staff-methodology into .agents/skills/chief-of-staff-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chief-of-staff-methodology", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/hermes-profiles --skill chief-of-staff-methodology -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install magnus919/hermes-profiles chief-of-staff-methodology --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/chief-of-staff-methodology .cursor/skills/chief-of-staff-methodology && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "chief-of-staff-methodology" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/chief-of-staff-methodology into .cursor/skills/chief-of-staff-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chief-of-staff-methodology", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/magnus919/hermes-profiles.git --path skills/chief-of-staff-methodology--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add magnus919/hermes-profiles --skill chief-of-staff-methodology -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install magnus919/hermes-profiles chief-of-staff-methodology --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/chief-of-staff-methodology .gemini/skills/chief-of-staff-methodology && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "chief-of-staff-methodology" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/chief-of-staff-methodology into .gemini/skills/chief-of-staff-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chief-of-staff-methodology", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install magnus919/hermes-profiles chief-of-staff-methodologyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add magnus919/hermes-profiles --skill chief-of-staff-methodology -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/chief-of-staff-methodology .github/skills/chief-of-staff-methodology && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "chief-of-staff-methodology" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/chief-of-staff-methodology into .github/skills/chief-of-staff-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chief-of-staff-methodology", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/hermes-profiles --skill chief-of-staff-methodology -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install magnus919/hermes-profiles chief-of-staff-methodology --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/chief-of-staff-methodology .opencode/skills/chief-of-staff-methodology && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "chief-of-staff-methodology" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/chief-of-staff-methodology into .opencode/skills/chief-of-staff-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chief-of-staff-methodology", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
chief-of-staff-methodology- GitHub stars
- 289
- Token cost
- ~1.2k tokens
- SKILL.md length
- 446 words
- Files
- 7 (incl. references)
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- MIT
At a glance
The craft of being a Chief of Staff — gatekeeping, force multiplication, executive briefing, organizational sensing, institutional memory, and meeting/calendar triage.
- Works in 7 steps: Visibility without ego. The CoS sees… → The truth at the speed of trust. The CoS… → Capacity is the fundamental metric. Not… → …
- SKILL.md covers When to Load, Loading Order, Reference Files and Design Principles, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Chief Of Staff Methodology is an agent skill from magnus919/hermes-profiles. The craft of being a Chief of Staff — gatekeeping, force multiplication, executive briefing, organizational sensing, institutional memory, and meeting/calendar triage. Provides the frameworks and templates that make an executive more effective by managing their capacity, information flow, and decision surface.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/executive-briefing.md`, `references/force-multiplication.md` and `references/gatekeeping-and-triage.md`).
The repository describes itself as: Curated Hermes Agent profiles for specialist swarms — opinionated, Hermes-optimized, artifact-pyramid native. The licence is MIT.
Example prompts
- “/chief-of-staff-methodology”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Visibility without ego. The CoS sees everything and claims nothing. If the CoS is getting credit, something went wrong.
- The truth at the speed of trust. The CoS costs the leader nothing in honesty and everything in filtering. Bad news must travel faster than…
- Capacity is the fundamental metric. Not "did the CoS do good work" but "did the leader do better work because the CoS was there?"
- Proactive before reactive. A great CoS surfaces what needs attention before it becomes a fire. The leader should rarely be surprised.
- Write in the leader's voice. The CoS is a translation layer between the leader's intent and the organization's language. Every brief…
- The gate swings both ways. Gatekeeping that creates organizational friction is failure. The CoS should make it easier for the right things…
- Institutional memory is a designed system, not a natural side effect. What the CoS remembers must survive across sessions, leaders, and…
What it can do on your machine
Read from SKILL.md and the folder at commit 867a555. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Chief Of Staff Methodology loads about 1.2k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 446 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from magnus919/hermes-profiles at commit 867a555, republished under its MIT licence (© magnus919). 446 words, ~1,204 tokens.
Download SKILL.mdSave it as
.claude/skills/chief-of-staff-methodology/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- chief-of-staff-methodology
- description
- The craft of being a Chief of Staff — gatekeeping, force multiplication, executive briefing, organizational sensing, institutional memory, and meeting/calendar triage. Provides the frameworks and templates that make an executive more effective by managing their capacity, information flow, and decision surface.
- version
- 0.1.0
- author
- Hermes Agent community
- license
- MIT
Chief of Staff Methodology
The Chief of Staff is an amplifier. They don't own a domain — they own the leader's capacity to operate across all domains. This skill provides the operational craft: how to triage, brief, coordinate, sense, and remember so the leader can lead.
When to Load
Load this skill when the task involves:
- Triaging information flow to an executive — what reaches them, in what form, at what latency
- Preparing executive briefs, decision memos, or board materials
- Managing an executive's calendar, meeting load, and attention allocation
- Coordinating across multiple teams or departments on behalf of a leader
- Building and maintaining institutional memory across turnover or discontinuity
- Sensing organizational mood, political dynamics, and team health
- Designing the systems that make the leader more effective (capacity multiplication)
- Creating or auditing escalation paths, decision rights, and delegation rules
Loading Order
skill_view('artifact-pyramids') # Output contract
skill_view('chief-of-staff-methodology') # This — methodology index
skill_view('executive-methodology') # Decision frameworks, stakeholder communication
skill_view('chief-of-staff-methodology', file_path='references/gatekeeping-and-triage.md')
skill_view('chief-of-staff-methodology', file_path='references/executive-briefing.md')
skill_view('chief-of-staff-methodology', file_path='references/force-multiplication.md')
skill_view('chief-of-staff-methodology', file_path='references/organizational-sensing.md')
skill_view('chief-of-staff-methodology', file_path='references/institutional-memory.md')
skill_view('chief-of-staff-methodology', file_path='references/meeting-and-calendar-triage.md')Reference Files
| Reference | Load When | File |
|---|---|---|
| Gatekeeping & Triage | You need to manage what reaches the leader — filtering, prioritization, escalation rules | references/gatekeeping-and-triage.md |
| Executive Briefing | You're preparing a memo, brief, or board deck for an executive | references/executive-briefing.md |
| Force Multiplication | You're designing systems that make the leader more effective | references/force-multiplication.md |
| Organizational Sensing | You need to read organizational mood, team health, and political dynamics | references/organizational-sensing.md |
| Institutional Memory | You're building continuity across leadership transitions or session boundaries | references/institutional-memory.md |
| Meeting & Calendar Triage | You're managing an executive's calendar, prepping for meetings, or auditing how time is spent | references/meeting-and-calendar-triage.md |
Show full SKILL.md (217 more words)Show less
Design Principles
- Visibility without ego. The CoS sees everything and claims nothing. If the CoS is getting credit, something went wrong.
- The truth at the speed of trust. The CoS costs the leader nothing in honesty and everything in filtering. Bad news must travel faster than good news.
- Capacity is the fundamental metric. Not "did the CoS do good work" but "did the leader do better work because the CoS was there?"
- Proactive before reactive. A great CoS surfaces what needs attention before it becomes a fire. The leader should rarely be surprised.
- Write in the leader's voice. The CoS is a translation layer between the leader's intent and the organization's language. Every brief, memo, or email should sound like it came from the leader.
- The gate swings both ways. Gatekeeping that creates organizational friction is failure. The CoS should make it easier for the right things to reach the leader, not harder for everything.
- Institutional memory is a designed system, not a natural side effect. What the CoS remembers must survive across sessions, leaders, and reorganizations.
Related Skills
executive-methodology— shared decision frameworks, stakeholder communication, governanceartifact-pyramids— output contract specificationorchestration-methodology— coordination across multiple agents or teamsorg-design— organizational structure, team topology, decision rightsoperational-design— process design, workflows, scale patterns
© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (references) in skills/chief-of-staff-methodology of magnus919/hermes-profiles.
- SKILL.md
- references/executive-briefing.md
- references/force-multiplication.md
- references/gatekeeping-and-triage.md
- references/institutional-memory.md
- references/meeting-and-calendar-triage.md
- references/organizational-sensing.md
Open the folder on GitHubat commit 867a555
Compare with similar skills
Chief Of Staff Methodology next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Chief Of Staff Methodology this skillmagnus919/hermes-profiles | 289 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Chief Of Staffalirezarezvani/claude-skills | 28k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Executealirezarezvani/claude-skills | 28k | — | ~831 | Automated safety check: Pass | MIT | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Chief Of StaffLeoYeAI/openclaw-master-skills | 2.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Chief Executivecbrock84/headcount | 2k | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
Execute
alirezarezvani/claude-skills
/cs:execute <decision — Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision.
- Official
Debugging Executions
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
Chief Of Staff
LeoYeAI/openclaw-master-skills
C-suite orchestration layer. An agent skill from LeoYeAI/openclaw-master-skills.
Chief Executive
cbrock84/headcount
Sets direction, allocates capital and attention, and makes the calls no one else can make.
Chief Of Staff
borghei/Claude-Skills
C-suite orchestration that routes founder questions to the right advisor role(s) and runs multi-role board meetings.
More from magnus919/hermes-profiles
All 31 skills in this repoData Scientist
magnus919/hermes-profiles
PhD-level expertise in data science, statistics, and machine learning.
Brand Designer
magnus919/hermes-profiles
Create comprehensive brand identity documentation for any brand.
Sdd Authoring
magnus919/hermes-profiles
Specification authoring for AI-native SDD — writes formal specifications in structured formats (Gherkin, user stories, acceptance criteria), enforces spec quality gates, and produces…
Sdd Verification
magnus919/hermes-profiles
SDD acceptance criteria verification — maps specification acceptance criteria to tests, validates implementation output against spec requirements, and produces artifact-pyramid-compliant…
Sdd Work Decomposition
magnus919/hermes-profiles
SDD work decomposition — translates formal specifications into dependency-aware task plans with per-task acceptance criteria.
Artifact Pyramids
magnus919/hermes-profiles
Progressive disclosure for what AI agents produce. An agent skill from magnus919/hermes-profiles.
Questions about Chief Of Staff Methodology
What does Chief Of Staff Methodology do?
The craft of being a Chief of Staff — gatekeeping, force multiplication, executive briefing, organizational sensing, institutional memory, and meeting/calendar triage. Chief Of Staff Methodology is an agent skill from magnus919/hermes-profiles. The craft of being a Chief of Staff — gatekeeping, force multiplication, executive briefing, organizational sensing, institutional memory, and meeting/calendar triage.
How do I install Chief Of Staff Methodology in Claude Code?
Run `npx skills add magnus919/hermes-profiles --skill chief-of-staff-methodology -a claude-code`. Or copy the skill folder (skills/chief-of-staff-methodology in magnus919/hermes-profiles) into .claude/skills/chief-of-staff-methodology in your project. Claude Code loads it when a task matches its description.
How do I install Chief Of Staff Methodology in Codex?
Run `npx skills add magnus919/hermes-profiles --skill chief-of-staff-methodology -a codex`. Or copy the skill folder (skills/chief-of-staff-methodology in magnus919/hermes-profiles) into .agents/skills/chief-of-staff-methodology in your project. Codex loads it when a task matches its description.
Can I use Chief Of Staff Methodology in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add magnus919/hermes-profiles --skill chief-of-staff-methodology -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chief-of-staff-methodology, .gemini/skills/chief-of-staff-methodology, .github/skills/chief-of-staff-methodology and .opencode/skills/chief-of-staff-methodology in your project.
What does Chief Of Staff Methodology need to run?
SKILL.md names no scripts, command-line tools or credentials: Chief Of Staff Methodology is instructions for the agent only.
Does Chief Of Staff Methodology access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Chief Of Staff Methodology safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Chief Of Staff Methodology use?
Chief Of Staff Methodology is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Chief Of Staff Methodology use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.9k tokens, read only when the agent opens those files.
What are the alternatives to Chief Of Staff Methodology?
Skills that share tags, products or a category with Chief Of Staff Methodology: Chief Of Staff (alirezarezvani/claude-skills, 28k stars), Execute (alirezarezvani/claude-skills, 28k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Chief Of Staff (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Chief Of Staff Methodology?
magnus919 (a GitHub user) maintains it in magnus919/hermes-profiles, which has 289 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on June 27, 2026.
Source: magnus919/hermes-profiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.