CtrlK
BlogDocsLog inGet started
Tessl Logo

founder-mode

/cs:founder-mode <question> — Auto-routes any founder question to the right C-role advisor or to /cs:boardroom for multi-role topics. The single-command entry point. Use when a founder asks any strategic question without knowing which advisor or command fits — e.g. 'runway pressure' routes to the CFO, 'gross retention dropped' routes to the CCO.

64

Quality

77%

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/founder-mode/SKILL.md

The canonical home for this skill is founder-mode in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

The body is well-structured and highly actionable, with a dense routing table, clear workflow, and concrete output templates. The main weakness is conciseness: editorial "killer command" framing is repeated and could be trimmed without losing clarity.

Suggestions

Collapse the intro's "killer command" pitch and the standalone "Why This Is the Killer Command" section into one or two sentences; the rationale is restated and adds padding.

Add the literal invocation syntax for routing to a cs-* agent (e.g., the exact command or tool call) so the single-role workflow step is copy-paste ready rather than "invoke that cs-* agent directly."

Consider moving the full 14-row signal→route table into a references file with a compact summary inline, so the SKILL.md body stays an overview and progressive disclosure reaches the top anchor.

DimensionReasoningScore

Conciseness

The routing table and examples are dense and efficient, but "killer command" framing is repeated across the intro and a dedicated "Why This Is the Killer Command" section that restates the cognitive-tax rationale, which could be tightened; matches "mostly efficient but includes some unnecessary explanation."

3 / 5

Actionability

A signal→agent routing table, numbered workflow, and copy-paste output templates make the guidance mostly executable; not a 5 because the actual agent-invocation step is described as "invoke that cs-* agent directly" without a literal command syntax.

4 / 5

Workflow Clarity

A clear five-step sequence handles single-role, multi-role, and ambiguous cases, with the ambiguous branch feeding back through /cs:office-hours and a decision-log step; minor validation gap keeps it below 5. Routing is not destructive or batch, so the workflow cap does not apply.

4 / 5

Progressive Disclosure

A single self-contained file is well sectioned (Routing Logic, Workflow, Output, Examples, Related) and the Related links are one level deep and clearly signaled; not a 5 because the sizable routing table has no progressive detail reference for this skill's own content.

4 / 5

Total

15

/

20

Passed

Description

87%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 clearly states what the command does, when to use it, and gives concrete routing examples a founder would actually say. It is distinguishable from peer skills and uses third-person voice throughout.

DimensionReasoningScore

Specificity

Names a concrete action ("Auto-routes any founder question to the right C-role advisor or to /cs:boardroom") with two destinations and worked examples, matching the "lists several specific actions; minor gaps" anchor; not a 5 because it is essentially one routing action rather than a comprehensive list of distinct capabilities.

4 / 5

Completeness

Explicitly answers both what ("Auto-routes any founder question to the right C-role advisor or to /cs:boardroom for multi-role topics. The single-command entry point.") and when ("Use when a founder asks any strategic question without knowing which advisor or command fits") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural founder phrases like "runway pressure" routes to the CFO and "gross retention dropped" routes to the CCO give good keyword coverage; not a 5 because synonyms and variations are limited to two examples.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche as the single-command auto-router with distinct triggers ("without knowing which advisor or command fits"), giving minimal conflict risk with other skills.

5 / 5

Total

18

/

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: 3 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.