CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

daily-task-manager

Task lifecycle management with stable task IDs. Add, complete, defer, remove, and review tasks with deterministic action routing and fail-closed ambiguity handling. Maintains a running task list as a brain page.

Quality

79%

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 ./plugin-variants/gbrain-daily/skills/daily-task-manager/SKILL.md

The canonical home for this skill is daily-task-manager in garrytan/gbrain

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 strong instruction-only skill: deterministic action routing, a fail-closed five-phase workflow with validation checkpoints and error-recovery loops, and a copy-paste-ready page template make it fully actionable. Its only real weakness is token efficiency — rules are duplicated across the Phases, Edge Cases, and Anti-Patterns sections, and the Design Rationale section is execution-irrelevant history that could be trimmed or moved to a reference file.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows — it is dense with skill-specific rules — but several rules are stated two or three times across Phases, Edge Cases, and Anti-Patterns (defer target date + reason, remove confirmation, P3 default, single-writer concurrency), and the "Design Rationale" section is version history not needed to execute. This is "mostly efficient but could be tightened" (anchor 3) rather than 4, since the cross-section duplication exceeds minor over-explanation.

3 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact tool calls (`get_page("ops/tasks")`, `put_page`, `add_timeline_entry`), a concrete ID scheme (`t-YYYYMMDD-NN`), a copy-paste-ready persisted page template, a structured return spec, and specific error procedures (revision_conflict → re-read, re-apply one change, save; write_pending exit 10 → poll `gbrain write-request <request_id>`). It is not 4 because no key execution detail is left to inference.

5 / 5

Workflow Clarity

Phases 1–5 (Load → Validate → Identify → Execute → Save) are clearly sequenced with explicit fail-closed checkpoints (zero matches → not_found, multiple → ambiguous, never mutate), explicit confirmation for the destructive remove action, and feedback loops for error recovery (revision_conflict re-apply loop, write_pending polling). The destructive-operation cap does not apply because validation and confirmation are present throughout.

5 / 5

Progressive Disclosure

The single-file body is well organized into clearly headed sections (Contract, Tool Interface, Action Routing, Phases, Edge Cases, Output Format, When it fails, Anti-Patterns) with one clearly signaled one-level-deep reference (../conventions/agent-operator-protocol.md) and no bundle files to mis-navigate. It is not 5 because at ~120 lines some content (Design Rationale, detailed failure handling) could be split into a reference file, leaving minor organization gaps typical of anchor 4.

4 / 5

Total

17

/

20

Passed

Description

71%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 is specific and largely distinct, enumerating the full task lifecycle with concrete actions and a defined storage location. Its main weakness is completeness: the description field itself lacks a "Use when..." clause, so the when-to-use guidance (which exists only in the separate when_to_use frontmatter field) is invisible at the description level. Trigger coverage is good but misses common synonyms like "to-do list" and "reminders".

Suggestions

Append a "Use when..." clause with concrete trigger phrases to the description field itself (e.g., "Use when the user says 'add task', 'what are my tasks', 'to-do list', or asks to defer/complete a task") — the guidance currently lives only in the separate when_to_use frontmatter field, capping completeness at 3.

Include natural synonyms such as "to-do list", "reminders", and "mark done/finished" in the description to broaden trigger term coverage beyond the current add/complete/defer/review/task-list phrases.

Name the user-facing surface in the description (e.g., mention "to-do/task list") to further reduce collision risk with unrelated note-taking or reminder skills.

DimensionReasoningScore

Specificity

"Add, complete, defer, remove, and review tasks" lists five concrete lifecycle actions plus a concrete storage mechanism ("Maintains a running task list as a brain page"), matching the level-5 anchor for multiple specific concrete actions with comprehensive coverage. It is not 4 because action coverage of the task lifecycle is complete rather than having minor gaps.

5 / 5

Completeness

The description clearly answers "what" ("Task lifecycle management with stable task IDs... Add, complete, defer, remove, and review tasks") but contains no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guideline; the skill's when-guidance lives in a separate when_to_use frontmatter field outside the evaluated description. It is not 4 because the "when" is entirely absent from the description text, not merely imprecise.

3 / 5

Trigger Term Quality

"add", "complete", "defer", "remove", and "task list" are phrases users naturally say, giving good keyword coverage. It is not 5 because common synonyms and variations ("to-do list", "reminders", "mark done", "finished") are missing, and not 3 because the core natural phrases are present, not merely "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

"Task lifecycle management with stable task IDs", "deterministic action routing", and "brain page" carve a mostly distinct niche with minor overlap risk against closely related to-do/reminder skills. It is not 5 because generic triggers like "task list" could still collide with another task-tracking skill.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

garrytan/gbrain

Path

plugin-variants/gbrain-daily/skills/daily-task-manager/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.