CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chief-ai-officer-advisor

Chief AI Officer advisory for startups: model build-vs-buy decisions (API vs fine-tune vs in-house), AI risk classification under EU AI Act + US state patchwork, AI cost economics (API-to-self-hosted breakeven), and AI team org evolution. Use when deciding whether to call an API or fine-tune, classifying AI use cases for regulatory risk, calculating when self-hosting pays off, sequencing AI hires, or when user mentions CAIO, AI strategy, model selection, foundation model, fine-tuning, EU AI Act, NIST AI RMF, AI governance, model risk, or AI economics. Strategic only — does not duplicate engineering AI/ML skills.

66

Quality

83%

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

The canonical home for this skill is chief-ai-officer-advisor in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 strategic skill with excellent actionability — real, verified scripts with copy-paste commands — and clear sequenced workflows. Its main weakness is token efficiency: a redundant keyword dump, a long adjacent-skills list, and regulatory/pricing detail inlined that the reference files already carry.

Suggestions

Delete the Keywords section — trigger terms belong in the frontmatter description; the ~60-term list in the body is pure token cost.

Trim the US state patchwork and industry-overlay lists to a one-line pointer to references/ai_risk_governance.md, keeping only the tier table that drives the decision.

Cut the Adjacent Skills section to the 3-4 most relevant cross-check targets (CTO, CFO, general counsel) since the workflows already name the cross-checks inline.

DimensionReasoningScore

Conciseness

The four decision sections are dense and number-rich, but the ~60-term Keywords section duplicates trigger terms already in the description, the 10-item Adjacent Skills list is padding, and the inlined US-state patchwork and industry-overlay lists duplicate content stated to be in references/ai_risk_governance.md. Mostly efficient with several sections that should be trimmed or moved — fits the 3 anchor better than 4, where over-explanation would be only minor.

3 / 5

Actionability

Fully executable guidance: exact run commands for three scripts (verified to exist with matching optional-path CLIs and embedded samples), a copy-paste Output Standards template, and concrete cross-check steps per workflow. Covers the common cases without requiring the user to construct inputs, matching the 5 anchor.

5 / 5

Workflow Clarity

Four workflows each with a stated goal, duration, and numbered steps, plus cross-checks with other advisor skills and a 'Key Questions (ask these first)' section that function as checkpoints. Minor validation gaps — no explicit 'if the output says X, do Y' feedback loops — but these are advisory, non-destructive decisions so the destructive-operation cap does not apply; fits the 4 anchor, not 5 which requires explicit validation steps and error-recovery loops.

4 / 5

Progressive Disclosure

Clear overview with four real one-level-deep reference files, each signaled both inline ('See references/ai_risk_governance.md for the full regulatory landscape') and in a dedicated References section with descriptions. Minor gap: reference-type material (EU tier table detail, US state list, 2026 API pricing) is inlined in the body rather than fully delegated to the reference files, keeping it just below the 5 anchor's 'content appropriately split'.

4 / 5

Total

16

/

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 with an explicit what-and-when structure, third-person voice, and a clear niche boundary. Trigger coverage is good but could add common synonyms, and capabilities are named at advisory-domain level rather than as concrete operations.

Suggestions

Add natural trigger synonyms such as 'build vs buy', 'self-hosting vs API', 'GPU cost', and 'AI hiring' to the 'when user mentions' list.

Ground each capability in a more concrete operation, e.g. 'runs build-vs-buy TCO calculations' or 'classifies use cases into EU AI Act risk tiers with required controls' rather than naming the advisory domain alone.

DimensionReasoningScore

Specificity

Names several specific capability areas with parenthetical elaboration ("model build-vs-buy decisions (API vs fine-tune vs in-house)", "AI cost economics (API-to-self-hosted breakeven)"), but they are framed as advisory domains rather than the concrete executable actions of the 5 anchor. Well above the 3 anchor's 1-2 actions; the minor gap is that capabilities like 'AI team org evolution' are described at domain level without the underlying operation.

4 / 5

Completeness

Explicitly answers both what ("Chief AI Officer advisory for startups: model build-vs-buy decisions... AI risk classification... AI cost economics... and AI team org evolution") and when ("Use when deciding whether to call an API or fine-tune, classifying AI use cases for regulatory risk... or when user mentions CAIO...") with concrete trigger phrases, matching the 5 anchor's structure exactly.

5 / 5

Trigger Term Quality

Good coverage of natural terms users would say ("CAIO, AI strategy, model selection, foundation model, fine-tuning, EU AI Act, NIST AI RMF, AI governance"), but misses common variations like "build vs buy", "self-hosting", "GPU cost", and "AI hiring". Clearly above the 3 anchor (relevant keywords with missing synonyms would be sparse); not 5 because several natural synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

A clear CAIO-strategy niche with an explicit boundary ("Strategic only — does not duplicate engineering AI/ML skills"), but trigger terms like "fine-tuning", "model selection", and "foundation model" carry moderate overlap risk with tactical engineering AI/ML skills. Mostly distinct with minor overlap risk against closely related skills, per the 4 anchor; not 5 because those shared terms would still compete.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alirezarezvani/claude-skills

Path

c-level-advisor/chief-ai-officer-advisor/skills/chief-ai-officer-advisor/SKILL.md

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.