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

82%

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

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

An exceptionally actionable, well-sequenced instruction body: deterministic routing, fail-closed ambiguity handling, validation gates on every mutation, and concrete error-recovery loops. Its only real cost is modest token redundancy (repeated rules across Phases/Edge Cases/Anti-Patterns and a version-history rationale section).

DimensionReasoningScore

Conciseness

The body is dense operational instruction — tool calls, ID format, page template, routing table, error procedures — with nothing explaining concepts Claude already knows. Not 5: redundancy costs tokens — the first-run migration rule appears nearly verbatim in both Phases and Edge Cases, the concurrency caveat is repeated in Edge Cases and Anti-Patterns, and the Design Rationale section is version-history meta-commentary rather than guidance; not 3: these are minor trims, not padded sections.

4 / 5

Actionability

Guidance is fully concrete and executable: exact tool calls (`get_page("ops/tasks")`, `put_page("ops/tasks", …)`), the exact slug and its disambiguation from `ops/tasks.md`, a copy-paste-ready persisted page template, a structured returns schema, ID minting rules (`t-YYYYMMDD-NN`), and per-error procedures (revision_conflict re-apply, `write_pending` exit 10 polling). For an instruction-only skill this covers the common cases completely.

5 / 5

Workflow Clarity

Five clearly sequenced phases (Load → Validate → Identify → Execute → Save) with explicit validation gates: zero/multiple match handling returns not_found/ambiguous without mutating, remove requires explicit confirmation (destructive op safeguard), and the When-it-fails section gives feedback loops (re-read + re-apply on revision_conflict; poll on write_pending). The Anti-Patterns list functions as a corrective checklist. Not 4: no checkpoints are missing or implicit.

5 / 5

Progressive Disclosure

The body is well-sectioned (Contract, Tool Interface, Routing, Phases, Edge Cases, Output Format, Failure handling, Anti-Patterns) with a single clearly-signaled one-level-deep reference ([agent-operator-protocol](../conventions/agent-operator-protocol.md)); no bundle files exist to organize. Not 5: at ~118 lines, content such as the Design Rationale and the expanded Anti-Patterns/Edge-Case prose could live in a reference file, and the one external reference target cannot be verified within the bundle; not 3: structure and signaling are consistently clear, with nothing buried or inlined that clearly belongs elsewhere.

4 / 5

Total

18

/

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.

A specific, concrete description that names the full action set and the underlying mechanics, weakened only by the total absence of a "when to use this" trigger clause. Adding an explicit use-when line with natural trigger phrases would lift it into the top band.

Suggestions

Append a trigger clause such as: 'Use when the user mentions tasks, a to-do list, reminders, or asks what's on their plate today.'

Fold one or two natural synonyms (to-do, todo list, reminders) into the description so trigger matching doesn't rely solely on the separate triggers field.

State the audience surface in the description (e.g., 'for agents managing a user's daily task list') to sharpen distinctiveness against generic note-taking skills.

DimensionReasoningScore

Specificity

The description enumerates all five lifecycle actions concretely — "Add, complete, defer, remove, and review tasks" — plus concrete mechanics ("stable task IDs", "deterministic action routing", "fail-closed ambiguity handling", "running task list as a brain page"), which is comprehensive coverage for the domain. Not 4: there are no minor gaps; every capability of the skill is named.

5 / 5

Completeness

The "what" is explicit and multi-part (lifecycle actions, ID stability, task-list-as-brain-page), but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description field, which caps completeness at 3 per the judging guidelines. Not 4: the "when" is entirely absent, not merely implicit or under-specified.

3 / 5

Trigger Term Quality

Natural verb phrases users would say appear directly ("Add... tasks", "task list", "complete", "defer"), giving good keyword coverage. Not 5: common natural synonyms like "to-do", "todo list", "reminders", or "what's on my plate" are absent from the description text itself; not 3 because coverage goes well beyond "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct — "Task lifecycle management with stable task IDs" anchored to a "brain page" store — with lifecycle verbs that a generic notes or reminders skill wouldn't claim. Not 5: "tasks"/"task list" is a common domain with residual overlap risk against todo/reminder-style skills; not 3: the brain-page context and ID mechanics clearly differentiate it.

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

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.