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

87%

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

82%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, highly operational setup skill with executable commands, explicit validation gates, and disciplined conditional loading of one-level-deep references. The main weaknesses are structural: mid-sequence section interleaving and an orphaned reference file (skill-updates.md) with no link from the overview.

Suggestions

Move the "Configuration" and "Error Handling" sections after "4. Hand off" (or fold them into the relevant steps) so the numbered CLI sequence reads 1-2-3-4 without interruption.

Link references/skill-updates.md from the body (e.g. from the Configuration section, which already discusses skill lifecycle updates) so every bundle file is discoverable from the overview.

Inline the concrete POSIX/PowerShell probe for the `<qodo>` invocation (or a one-line example of the resolved form) so the core steps are executable without opening runtime.md.

DimensionReasoningScore

Conciseness

Quotes: "Keep the executable as `<qodo>`. Require Qodo CLI **2.0.0 or newer** before authentication." — lean, assumes Claude's competence, and never explains concepts Claude already knows. Every sentence is operational instruction; version numbers appear only as executable command flags and gating requirements, not as deprecated-pattern narration, so no penalty applies.

5 / 5

Actionability

Quotes: "<qodo> read whoami --json --skill qodo-setup --skill-version 1.0.11 --distribution marketplace --host codex" and "<qodo> tools --refresh --json ..." — copy-paste-ready commands with full flag sets. Not 5: the PowerShell invocation ("resolve the verified native/Node invocation in [runtime.md](references/runtime.md)") and the login-method choice ("read [authentication.md](references/authentication.md) before choosing login") are deferred to references, leaving minor gaps for fully executable guidance.

4 / 5

Workflow Clarity

Quotes: "Only after identity succeeds" (explicit gating), "If refresh fails, report that sign-in succeeded but tools are unavailable, with the exact error and `<qodo> tools --refresh` as the retry. Do not log in again" (validation plus feedback loop). Sequence is numbered with clear stop conditions ("Stop on cancellation or denied permission"), but the "Configuration" and "Error Handling" sections interleave between step 3 and "4. Hand off", slightly disrupting the numbered flow — a minor gap that keeps it below 5.

4 / 5

Progressive Disclosure

Quotes: "read [runtime.md](references/runtime.md) first", "read [host-recovery.md](references/host-recovery.md) only when encountered" — well-signaled, one-level-deep, conditionally-loaded references that match the bundle structure (all three linked files exist in references/). Not 5: references/skill-updates.md exists in the bundle but is never linked from the body, an orphaned file that is not discoverable from the overview.

4 / 5

Total

17

/

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: third-person, concrete, and concise, with explicit what/when coverage and three distinct trigger conditions. Trigger-term coverage is good though not exhaustive of natural synonyms.

DimensionReasoningScore

Specificity

Quotes: "install the CLI, sign in, and verify tools" — several specific, concrete actions in the Qodo domain. It is not 5 because coverage has minor gaps (the MCP-connected path and runtime-resolution aspects of the skill are not surfaced in the description); it exceeds 3 because it lists three concrete actions rather than just 1-2.

4 / 5

Completeness

Explicitly answers both: what — "Set up Qodo in a coding agent — install the CLI, sign in, and verify tools"; when — "Use after plugin installation, on setup requests, or when a Qodo skill finds a missing CLI or login". Three concrete trigger conditions match the top anchor; a 4 would require the 'when' to be less explicit than it is.

5 / 5

Trigger Term Quality

Quotes: "install the CLI", "sign in", "plugin installation", "missing CLI or login" — natural phrases a user or agent would say during Qodo setup. Not 5 because a few natural variations are missing (e.g. "authenticate", "log in to Qodo", "qodo command not found"); clearly above 3 since the terms present are natural rather than generic.

4 / 5

Distinctiveness Conflict Risk

Quotes: "Qodo", "when a Qodo skill finds a missing CLI or login", "after plugin installation" — a clear niche with distinct, brand-anchored triggers. Minimal overlap risk with other skills; the setup scope is unambiguous, matching the top anchor.

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.