CtrlK
BlogDocsLog inGet started
Tessl Logo

c-level-agents

Founder-mode executive team. 13 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, GC, CDO, CAIO, CCO, VPE, Chief of Staff) and 21 /cs:* slash commands for forcing-question office hours, multi-role boardroom deliberation, strategic sprint pipeline, and meta routing. Use when the founder needs a virtual executive team, when invoking /cs:* commands, or when orchestrating multi-role decisions.

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/c-level-agents/SKILL.md

The canonical home for this skill is c-level-agents in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%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-organized plugin overview with clear sequencing and lean command listings, but it is more descriptive than actionable and references bundle files that are not present. Adding concrete usage detail and ensuring referenced files ship with the bundle would raise the weaker dimensions.

Suggestions

Add a short, concrete example of a full run (e.g., actual command outputs or the memo artifact produced) so the body is executable guidance rather than purely descriptive.

Either include the referenced persona-voices.md and llm-wiki-bridge.md in a references/ bundle directory or note explicitly that they live in the parent plugin and may be absent in isolation.

Make validation/checkpoint steps explicit in the sprint pipeline (e.g., 'after /cs:boardroom, confirm consensus before /cs:decide') rather than leaving them implicit.

DimensionReasoningScore

Conciseness

The body is a lean overview with terse one-line command descriptions and no over-explanation of known concepts; the standalone 'Keywords' section mildly duplicates the description, keeping it just below the score-5 anchor.

4 / 5

Actionability

Quick Start provides copy-paste slash commands, but the bulk of the body is descriptive overview (agent-wrapper traits, design principles) with no executable code or internal mechanics — concrete guidance is present but incomplete, matching the score-3 anchor.

3 / 5

Workflow Clarity

The sprint pipeline '/cs:brief → /cs:boardroom → /cs:decide → /cs:execute → /cs:post-mortem' and the architecture diagram give a clear sequence, but checkpoints (Phase 2 isolation, /cs:freeze, cross-eval) are implicit rather than explicit validation steps — above score-3, below score-5.

4 / 5

Progressive Disclosure

Sections are well-organized with a signaled References list, but the bundle contains no references/scripts/assets directories and the referenced '../../references/persona-voices.md' and 'llm-wiki-bridge.md' do not resolve within the bundle — structure is present but references are not actually available, matching the score-3 anchor.

3 / 5

Total

14

/

20

Passed

Description

92%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, third-person description that concretely enumerates capabilities and provides explicit 'Use when…' trigger guidance with synonyms. The only minor gap is a few additional natural trigger phrasings that could broaden keyword coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities ('forcing-question office hours, multi-role boardroom deliberation, strategic sprint pipeline, and meta routing') plus 13 named agents and 21 commands — comprehensive coverage, matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers both 'what' (13 cs-* agents, 21 /cs:* commands, four capability types) and 'when' (a concrete 'Use when…' clause with three trigger scenarios), matching the score-5 anchor.

5 / 5

Trigger Term Quality

'Use when the founder needs a virtual executive team, when invoking /cs:* commands, or when orchestrating multi-role decisions' gives good natural trigger coverage with synonyms, but a few common phrasings are absent — above the score-3 anchor, below fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche (founder-mode C-suite orchestration via /cs:* commands) with distinct triggers and minimal overlap with other skills, matching the score-5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 suspicious

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
Reviewed

Table of Contents

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.