CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qodo-review-notes

Preserve reasoning for independent review of plans and PRs through Qodo notes tools. Use during substantive planning and development, when decisions, scope or validation change, when resuming or handing off work, and before opening or updating a PR. Tracks hold the evolving plan across issues and repositories; PR notes explain one change. Also use to read or maintain reviewer context. This skill does not review or approve a plan or code, implement it, or open a PR.

Quality

78%

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 ./antigravity-plugins/qodo/skills/qodo-review-notes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Operationally dense and unusually rigorous: executable CLI/JSON examples, explicit validation gates, and genuine error-recovery loops for conflicts and pagination. The costs are repetition of the update-gate rules across three sections, tangled update/recovery prose, and heavy inline conditional detail (enterprise updates, pagination, provider resolution) that should be split into reference files.

Suggestions

State the version/update-gate rules once and cross-reference them from 'Manual enterprise skill updates' and 'Runtime recovery' instead of restating them three times.

Move the enterprise skill-update, runtime-recovery, and paged-read reconstruction detail into references/ files (like the existing windows-*.md pattern), keeping SKILL.md to the trigger condition and a one-line pointer.

Add short example invocations for save-track, find-tracks, and for-pr to match the quality of the prepare-pr and bind-pr examples.

DimensionReasoningScore

Conciseness

The body does not tutor Claude on known concepts, but at ~450 lines it is noticeably tightened-beyond-need in places: the update-gate rules (presence-only QODO_UPDATE_BASE_URL check, 'ask once', 'never switch origins', 'one recovery attempt') are restated across 'Choose the available tools', 'Manual enterprise skill updates', and 'Runtime recovery', and dense passages like 'If the version is older or cannot be parsed... For parsed 1.x, normal qodo update can reach approved 2.x...' repeat conditions already covered. Anchor 3 ('mostly efficient but could be tightened') fits; not 2 because there is no filler explaining known concepts, not 4 because the cross-section repetition is more than minor.

3 / 5

Actionability

Gives copy-paste-ready commands ('qodo --version', 'qodo read whoami --json --skill qodo-review-notes --skill-version 1.0.4 ...', 'qodo read tools review-notes --json'), a complete prepare-pr args-file JSON example, an MCP bind-pr JSON example, an operations table mapping every tool suffix, concrete field mappings ('contentMarkdown → content_markdown'), and exact pagination flags ('--read-cursor', 'prs_after', 'next_before'). Not anchor 5: several common operations (save-track, find-tracks, for-pr, publish-track) have no example invocation and defer entirely to 'discover the live schemas'.

4 / 5

Workflow Clarity

Intake/resume is a clear numbered 1–5 sequence with an explicit 'ask which effort this change belongs to' checkpoint; validation gates are explicit ('check qodo --version before discovering', 'confirm localGitCapture: true', 'read the latest draft before editing', 'Wait for a durable publication receipt and ready_to_open_pr=true before opening'), and error handling defines real feedback loops (MT-CONFLICT → reread latest draft → retry with a new transport idempotency key; discard fragments and restart paged reads on conflict). Not anchor 5 because the enterprise-update and runtime-recovery sections tangle many nested exception conditions into prose that is hard to follow sequentially.

4 / 5

Progressive Disclosure

The two bundle files are real, one level deep, and clearly conditionally signaled ('read [shell guidance](references/windows-shells.md) before the first call; [launcher recovery](references/windows-launcher.md) only if invocation fails'), but the SKILL.md body inlines large conditional material that belongs in separate references — the ~80-line manual enterprise update / runtime recovery procedure (needed only on update notices), the detailed pagination reconstruction rules, and the full Git-provider URL resolution cataloging. Anchor 3 ('content that should be separate is inline') fits; above anchor 2 because structure and existing references are clear, below anchor 4 because several whole sections are deferrable detail.

3 / 5

Total

14

/

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: explicit what/when structure, natural trigger conditions, and a rare explicit negative-scope sentence that reduces conflict risk. Main gaps are the abstract core verb ('preserve reasoning'), missing common synonyms like 'take notes' or 'handoff', and residual overlap with generic PR-workflow triggers.

Suggestions

Name the concrete operations in the description (e.g. create, publish, and bind review notes) instead of the abstract 'preserve reasoning'.

Add natural synonyms users would say, such as 'take notes', 'session handoff', or 'review notes', to broaden trigger coverage.

Sharpen the 'before opening or updating a PR' trigger to mention notes specifically (e.g. 'when preparing PR review notes') to reduce overlap with PR-creation skills.

DimensionReasoningScore

Specificity

Enumerates several concrete capabilities — 'Preserve reasoning for independent review of plans and PRs through Qodo notes tools', 'Tracks hold the evolving plan across issues and repositories; PR notes explain one change', 'read or maintain reviewer context' — plus explicit negative scope ('does not review or approve a plan or code, implement it, or open a PR'). Falls short of anchor 5 because the core verb 'preserve reasoning' stays abstract and no concrete note operations (save/publish/bind) are named; above anchor 3 since multiple distinct functions are listed with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both questions: what ('Preserve reasoning for independent review of plans and PRs through Qodo notes tools', with the track vs PR-note split) and when ('Use during substantive planning and development, when decisions, scope or validation change, when resuming or handing off work, and before opening or updating a PR'). Matches anchor 5's requirement of concrete trigger phrases; anchor 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Contains natural developer phrases — 'substantive planning and development', 'when decisions, scope or validation change', 'when resuming or handing off work', 'before opening or updating a PR'. Not anchor 5: common synonyms a user would actually say are missing, e.g. 'take notes', 'save context', 'session handoff', 'review notes'; clearly above anchor 3 because multiple natural trigger conditions are covered rather than a bare domain keyword.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Qodo notes tools) and the closing sentence 'This skill does not review or approve a plan or code, implement it, or open a PR' actively disambiguates from review/PR-creation skills. Not anchor 5 because the trigger 'before opening or updating a PR' and 'planning and development' still overlap with closely related PR-workflow skills; well above anchor 3's 'could still overlap with similar skills' given the vendor-specific framing.

4 / 5

Total

17

/

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

antigravity-plugins/qodo/skills/qodo-review-notes/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.