CtrlK
BlogDocsLog inGet started
Tessl Logo

cto-advisor

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

75

1.73x
Quality

63%

Does it follow best practices?

Impact

99%

1.73x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/c-level/cto-advisor-64810d10/SKILL.md

The canonical home for this skill is cto-advisor in majiayu000/claude-skill-registry

SKILL.md
Quality
Evals
Security

Quality

Content

38%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 a sprawling, padded CTO playbook heavy on generic management advice Claude already knows, with numbered lists lacking validation checkpoints and references to bundle files that do not exist. It needs aggressive trimming and real supporting files.

Suggestions

Cut generic management content Claude already knows (weekly cadence, quarterly planning, OKRs/1:1s, crisis templates, book and community lists) and keep only the proprietary tooling and framework specifics.

Actually provide the referenced bundle files (references/architecture_decision_records.md, references/technology_evaluation_framework.md, references/engineering_metrics.md and the two scripts) or remove the dangling references.

Move the inlined cadence/planning/crisis/stakeholder/template material into one-level-deep reference files so SKILL.md becomes a lean overview with clear navigation.

DimensionReasoningScore

Conciseness

The ~400-line body is extensively padded with generic CTO guidance Claude already knows (weekly cadence, quarterly OKRs, 1:1s, crisis templates, book/community lists), matching the 'noticeably verbose; several unnecessary padded sections' anchor.

2 / 5

Actionability

Provides some concrete guidance (script invocations and specific metric thresholds like 'Deployment Frequency: >1/day', 'Manager:Engineer = 1:8'), but the scripts referenced do not exist and most sections are abstract bullet advice or placeholder templates with bracketed fill-ins.

3 / 5

Workflow Clarity

Numbered sequences exist (ADR process, vendor evaluation, crisis response phases, strategic initiatives) but they are generic lists with no validation checkpoints or error-recovery feedback loops.

3 / 5

Progressive Disclosure

References to references/*.md and scripts/*.py are signaled in Quick Start, but none of those files or directories exist (dangling references), and large amounts of content that belong in separate files (cadence, planning, crisis, stakeholder, templates) are inlined into SKILL.md.

2 / 5

Total

10

/

20

Passed

Description

88%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 well-crafted description that names concrete tools, includes an explicit 'Use when' clause, and covers natural trigger terms with synonyms. The only weakness is a repetitive, slightly padded trigger enumeration.

DimensionReasoningScore

Specificity

Lists multiple concrete tools/capabilities ('tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates'), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly states both what it does ('Technical leadership guidance... Includes...') and when to use it via a clear 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural-term coverage including synonyms ('tech debt'/'technical debt', 'DORA metrics', 'ADR'), but the trigger enumeration repeats most terms across the 'Use when assessing...' and 'or when user mentions...' clauses, which is padding rather than added coverage.

4 / 5

Distinctiveness Conflict Risk

Has a clear CTO-leadership niche with distinct triggers (CTO, DORA, ADR, tech debt), but the broad engineering-leadership framing carries minor overlap risk with general management/leadership skills.

4 / 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

referenced_paths_exist

Referenced path issues: 10 missing

Warning

Total

15

/

16

Passed

Repository
majiayu000/claude-skill-registry
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.