Name: chief-of-staff
Rating: 62.4 (1 reviews)
Author: alirezarezvani

chief-of-staff

C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically. Use when a founder question needs routing to the right advisor — e.g. 'should we raise now or cut burn?' — or when a multi-domain decision needs a board meeting convened.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/chief-of-staff/SKILL.md

The canonical home for this skill is chief-of-staff in alirezarezvani/claude-skills

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable orchestration skill with clear invocation syntax and templates. Its main weaknesses are missing validation checkpoints for batch board-meeting invocations and references that point to bundle files not present in the directory.

Suggestions

Add an explicit validation/feedback step before synthesis in the board-meeting protocol (e.g. verify each role turn was received and no circular invocation occurred before synthesizing).

Provide the missing references/routing-matrix.md and references/synthesis-framework.md files, or remove the references if they are not part of this bundle.

Move the full 33-skill ecosystem enumeration and the inlined routing matrix into the referenced files to tighten the SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence — tables, terse rules, and code blocks with no concept explanations — but a few sections (full ecosystem enumeration, keyword list, inlined routing matrix) repeat or pad what could live entirely in references.	4 / 5
Actionability	Provides concrete, executable constructs — the [INVOKE:role\|question] syntax, the decision-complexity scoring table, the board-meeting template, and synthesis output format — with minor gaps (no worked end-to-end example tying them together).	4 / 5
Workflow Clarity	The session protocol lists steps and loop-prevention rules with checkpoints, and the board protocol has constraints, but it triggers batch/multi-role invocations with no validation step before synthesis and only a soft 'no loops occurred' checklist item — the batch-operation feedback-loop cap applies.	3 / 5
Progressive Disclosure	The body signals two one-level-deep references (routing-matrix.md, synthesis-framework.md) and points to ../agent-protocol/SKILL.md, but the references/ directory does not exist on disk so the signaled bundle is not actually present, and a large routing matrix plus ecosystem enumeration is inlined where it could be split out.	3 / 5
	Total	14 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly states capabilities and includes a concrete 'Use when...' trigger with a realistic founder example. Minor room to widen trigger-term coverage and reinforce distinctiveness from sibling orchestration skills.

Suggestions

Add a couple more natural trigger variations (e.g. 'multi-domain tradeoff', 'who should I ask about...') to broaden keyword coverage.

Sharpen distinctiveness by stating what makes this the single entry point versus the board-meeting and agent-protocol skills it invokes.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Routes founder questions to the right advisor role(s)', 'triggers multi-role board meetings', 'synthesizes outputs', and 'tracks decisions' — matching the 'lists several specific actions; minor gaps' anchor, though it stops short of the comprehensive multi-action coverage of a 5.	4 / 5
Completeness	Explicitly answers both 'what' (routes/synthesizes/tracks) and 'when' via the 'Use when a founder question needs routing to the right advisor — e.g. ... or when a multi-domain decision needs a board meeting convened' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases a founder would say ('should we raise now or cut burn?', 'multi-domain decision needs a board meeting convened') with good coverage, but the example trigger is a single instance rather than a broad set of synonyms and variations.	4 / 5
Distinctiveness Conflict Risk	The 'C-suite orchestration / routing-to-advisor' niche is fairly distinct, but in an ecosystem of 33 sibling C-suite skills there is residual overlap risk with the role skills and the board-meeting orchestration skill it explicitly coordinates.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/chief-of-staff/SKILL.md
Commit: 19392f7

Reviewed: ~4 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.