CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

todoist

Use when invoked on any codebase to perform a thorough scan of its structure, completion state, features, and gaps, then produce a ranked TODOIST.md of actionable work items with context, rationale, and competitive insight.

Quality

74%

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 ./skills/development-skills/todoist/SKILL.md
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.

This is a strong, well-structured workflow skill: five ordered phases, executable commands, a deterministic ranking formula, a complete output template, and a pre-delivery validation checklist, all written for an intelligent reader without padding. The main refinements are showing one worked example of a finished TODOIST.md entry, clarifying that the Phase 5 self-check applies before the final file is committed (versus Phase 4's write instruction), and deduplicating the secrets/paths rules repeated across four sections.

DimensionReasoningScore

Conciseness

The body is dense with task-specific value — exact file lists to read, a copy-paste grep command, a scoring formula, an output template, and a mistakes table — with almost no explanation of concepts Claude already knows. It is not a 5 because of minor trimmable redundancy: the secrets/paths rules are repeated in the privacy guarantee, Content Rules, Self-Check, and Common Mistakes, and the "Quick Reference" recapitulates the five phases; it is well above 3 since nearly every section earns its tokens.

4 / 5

Actionability

The guidance is largely executable: a ready-to-run grep command with explicit --include filters, exact search strings for Phase 2, a deterministic formula ("Impact × 2 + Effort + Risk") with tier thresholds (≥ 12 P0, 9–11 P1, 6–8 P2, ≤ 5 P3), and a complete output template. It stops short of a 5 only because no fully worked example of a completed TODOIST.md item is shown (the template is placeholder brackets, with concrete examples like "Add unit tests for `AuthService.verifyToken()`" appearing only in the mistakes table); it is well above 3 because commands and rules are concrete, not pseudocode.

4 / 5

Workflow Clarity

The five phases are explicitly ordered ("Run these steps in order"), each phase has defined sub-steps and evidence to collect, and Phase 5 provides an explicit validation checklist before delivery — including for the overwrite operation in Phase 4. It misses a 5 because the validate→fix→retry loop is implicit (the checklist says "Before writing the final file, verify" even though Phase 4 already instructs writing the file, a mild sequencing ambiguity) and no error-recovery path is spelled out; it is clearly above 3 because checkpoints are present and explicit rather than missing.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the single SKILL.md is well structured: numbered phases, headed subsections, a table of contents-like Quick Reference, and clearly labeled output sections. Content is mostly appropriately placed for a self-contained skill; the minor gap keeping it from 5 is that bulkier material — the ~60-line output template and the project-type reference table — could live in reference files to slim the always-loaded overview, but the inline choice is defensible since both are used on every run.

4 / 5

Total

16

/

20

Passed

Description

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

The description clearly states what the skill does and names a concrete, distinctive deliverable (a ranked TODOIST.md), but its trigger guidance is weak: "Use when invoked on any codebase" is circular, adds no discriminating situations, and omits the natural synonyms users would say. It is a solid mid-to-upper-middle description that would be substantially improved by one sentence of genuine trigger conditions.

Suggestions

Replace the circular trigger with concrete situations, e.g. "Use when starting work on an unfamiliar codebase, before a sprint or release, after a large refactor, or when the user asks for a TODO list, backlog, or gap analysis."

Add natural trigger synonyms users would actually say — "TODO list", "backlog", "prioritize work", "gap analysis", "technical debt" — to improve trigger matching.

Narrow the scope from "any codebase" to the specific situations where the skill applies, so it does not compete with code-review or refactoring skills for generic code requests.

DimensionReasoningScore

Specificity

The description lists several concrete facets — "scan of its structure, completion state, features, and gaps" and "produce a ranked TODOIST.md of actionable work items with context, rationale, and competitive insight" — naming a specific deliverable. It falls short of a 5 because the actions remain at the level of "scan"/"produce" rather than enumerating what the scan concretely does (e.g., grep for TODOs, compare against comparable projects), and it is above a 3 because multiple distinct, specific capabilities and the output artifact are named.

4 / 5

Completeness

Both halves are explicitly present: the "what" is scanning structure/completion/features/gaps and producing a ranked TODOIST.md, and a "Use when" clause opens the description. It is not a 5 because the "when" — "invoked on any codebase" — is circular and gives no concrete trigger situations (unfamiliar codebase, pre-release planning, post-refactor), matching anchor 4 ("'when' could be more explicit or specific") rather than 5; it is clearly above 3 because the when clause is explicit, not merely implied.

4 / 5

Trigger Term Quality

Relevant domain keywords are present ("codebase", "structure", "completion state", "features", "gaps", "TODOIST.md", "ranked"), but the natural phrases a user would actually say — "TODO list", "backlog", "prioritize work", "gap analysis", "technical debt" — are missing. It fits anchor 3 ("some relevant keywords but missing common variations or synonyms") better than 4, since the trigger framing "invoked on any codebase" is developer-tool language rather than user phrasing.

3 / 5

Distinctiveness Conflict Risk

The deliverable ("ranked TODOIST.md", "competitive insight", "completion state") carves out a niche distinct from generic review skills, but the trigger "invoked on any codebase" is maximally broad and would fire on virtually any code-related request, creating overlap with code-review, refactoring, and planning skills. This matches anchor 3 ("somewhat specific but could still overlap with similar skills"); it is above 2 because the named output artifact is distinctive, and below 4 because the any-codebase trigger leaves real conflict risk.

3 / 5

Total

14

/

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

relative_links

Relative link issues: 1 missing, 1 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

administrakt0r/pro-skills-repo-administraktor

Path

skills/development-skills/todoist/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.