CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qodo-setup

Set up Qodo in a coding agent — install the CLI, sign in, and verify tools. Use after plugin installation, on setup requests, or when a Qodo skill finds a missing CLI or login.

Quality

84%

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

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 dense, disciplined setup skill with executable verification commands, a clear gated sequence, and genuine one-level references. Its main weaknesses are stale-prone inline version pins, a command-less recovery section, and small structural blemishes.

Suggestions

Move version-sensitive values (CLI 2.0.0 minimum, --skill-version 1.0.14) into a single variable or a versioning note so they don't silently go stale.

Add at least one concrete command (or a direct pointer to the exact reference section) for the runtime compatibility recovery routes instead of policy-only prose.

Fix the inconsistent "## 4. Hand off" heading numbering and link skill-updates.md explicitly or fold its pointer into the body so no reference file sits two levels deep.

DimensionReasoningScore

Conciseness

The body is lean with no padding and assumes competence, but it hardcodes time-sensitive version numbers inline ("Require Qodo CLI **2.0.0 or newer**", "--skill-version 1.0.14" repeated in two commands), which the guidelines penalize unless placed in a deprecated/old-patterns section — so 4 rather than 5.

4 / 5

Actionability

The main flow provides copy-paste-ready commands (`qodo --version`, the fallback path probe, `read whoami --json ...`, `tools --refresh --json ...`), but the "Runtime compatibility recovery" section is abstract policy prose ("Make one approved attempt, reprobe unadorned version") with no executable commands, matching anchor 4's minor gaps rather than anchor 5.

4 / 5

Workflow Clarity

A clear sequence (probe version → update → authenticate → refresh tools → hand off) with explicit checkpoints ("Only after identity succeeds run:", "stop on denial/cancellation") and error-recovery stops, though the stray numbered heading "## 4. Hand off" amid unnumbered sections and some compressed recovery branching keep it from anchor 5.

4 / 5

Progressive Disclosure

References to runtime.md, authentication.md, and host-recovery.md are well-signaled, conditional, and all exist as real files; however skill-updates.md is only reachable two levels deep (via host-recovery.md) and section organization has minor inconsistencies (the "## 4." numbering artifact), fitting anchor 4's "minor organization gaps".

4 / 5

Total

16

/

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: concrete actions, an explicit multi-condition trigger clause, and a distinct product-scoped niche. It is only marginally short of top marks on specificity and trigger synonyms.

Suggestions

Slightly expand the action list (e.g. mention verifying the CLI version or tool refresh) to reach comprehensive specificity.

Add one or two natural trigger synonyms such as "authenticate" or "Qodo CLI" to broaden keyword coverage.

DimensionReasoningScore

Specificity

"install the CLI, sign in, and verify tools" names the domain and three concrete actions with only minor gaps in coverage, matching anchor 4; it falls short of anchor 5 because the actions remain terse and do not enumerate what verification covers.

4 / 5

Completeness

It clearly answers both what ("install the CLI, sign in, and verify tools") and when ("Use after plugin installation, on setup requests, or when a Qodo skill finds a missing CLI or login") with three concrete trigger conditions, matching anchor 5.

5 / 5

Trigger Term Quality

Triggers like "plugin installation", "setup requests", and "missing CLI or login" are phrases users would naturally say, giving good keyword coverage; a few natural variants (e.g. "authenticate", "Qodo CLI") are missing, so it is not anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description is anchored to a named product ("Qodo") with a clear setup niche and triggers deliberately scoped to complement sibling Qodo skills, giving minimal conflict risk — anchor 5.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

qodo-ai/qodo-skills

Path

codex-packages/qodo/skills/qodo-setup/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.