CtrlK
BlogDocsLog inGet started
Tessl Logo

task-reminder

Organize scattered tasks into actionable lists and generate daily/weekly/deadline reminder plans when you need a structured schedule and exportable outputs (MD/CSV), with optional system notifications.

63

Quality

75%

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 ./scientific-skills/Other/task-reminder/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.

The body is highly actionable with executable commands and a complete worked example, and it is well-structured with a verified bundle reference. Its main weakness is conciseness: several generic process/safety/checklist sections pad the document with content Claude already knows.

Suggestions

Trim or merge the generic process sections (Required Inputs, Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling, Deterministic Output Rules, Completion Checklist) into a short validation checklist, keeping only skill-specific guidance.

Move the detailed input schema and reminder-mode reference into a separate reference file (e.g. references/SCHEMA.md) and link to it from SKILL.md to improve progressive disclosure.

Replace abstract workflow steps with concrete checkpoints tied to the actual script (e.g. 'Run validate_payload; on missing field, print the exact field name and the minimum fix').

DimensionReasoningScore

Conciseness

The schema, JSON example, and CLI commands are efficient, but several boilerplate sections ('Required Inputs', 'Recommended Workflow', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling', 'Deterministic Output Rules', 'Completion Checklist') restate generic process Claude already knows and could be trimmed.

3 / 5

Actionability

Provides a complete copy-paste input.json example, exact CLI commands ('python scripts/task_reminder.py --json input.json'), and expected output files; the referenced scripts exist and are executable, covering the common cases fully.

5 / 5

Workflow Clarity

The Recommended Workflow is a clear four-step sequence with validation checkpoints ('Validate the request', 'Run a final validation pass'), and the skill is non-destructive file generation, so the destructive-operation cap does not apply; checkpoints are somewhat generic rather than concrete, keeping it at 4.

4 / 5

Progressive Disclosure

Body is organized into clear sections and references a real one-level-deep bundle file (scripts/task_reminder.py, which exists), but substantial implementation detail (input schema, modes, output files) is inlined in SKILL.md rather than split into separate references, so it is not a 5.

4 / 5

Total

16

/

20

Passed

Description

75%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 concrete, covers both what the skill does and when to use it, and carries natural trigger terms with low conflict risk. It is solid across the board but stops short of the top anchor because trigger phrases and synonyms/file extensions could be more comprehensive.

DimensionReasoningScore

Specificity

Names the domain plus several concrete actions ('Organize scattered tasks into actionable lists', 'generate daily/weekly/deadline reminder plans', 'exportable outputs (MD/CSV)', 'optional system notifications'); minor coverage gaps keep it just below a 5.

4 / 5

Completeness

Clearly answers 'what' (organize tasks, generate reminder plans, export) and includes an explicit 'when you need a structured schedule and exportable outputs' trigger; the trigger is present but not as concrete as an ideal 'Use when...' with specific scenarios, so it stays at 4 rather than 5.

4 / 5

Trigger Term Quality

Good coverage of natural phrases users would say ('scattered tasks', 'daily', 'weekly', 'deadline', 'reminder plans', 'structured schedule', 'MD/CSV'); a few synonyms and file extensions (e.g. .md, .csv, to-do) are missing, so it is not a 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a fairly distinct niche (daily/weekly/deadline reminder planning with MD/CSV export) with concrete triggers; minor overlap risk with generic task-management skills keeps it from a 5.

4 / 5

Total

16

/

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.

Validation15 / 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
aipoch/medical-research-skills
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.