CtrlK
BlogDocsLog inGet started
Tessl Logo

recipe-review-overdue-tasks

Find Google Tasks that are past due and need attention.

71

Quality

65%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/recipe-review-overdue-tasks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

57%

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 reasonably focused on a specific domain (Google Tasks) and a clear use case (past due items), giving it good distinctiveness. However, it lacks an explicit 'Use when...' clause, covers only a single action, and misses common trigger term variations that users might naturally use.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about overdue tasks, missed deadlines, or wants to review pending Google Tasks.'

Include natural trigger term variations such as 'overdue', 'late tasks', 'missed deadlines', 'to-do list', and 'pending tasks'.

Expand the capability description to mention additional actions if applicable, such as listing, prioritizing, or summarizing overdue tasks.

DimensionReasoningScore

Specificity

Names the domain (Google Tasks) and a specific action (find past due tasks), but only describes one action rather than listing multiple concrete capabilities.

2 / 3

Completeness

Describes what it does (find past due Google Tasks) but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill.

2 / 3

Trigger Term Quality

Includes 'Google Tasks' and 'past due' as natural keywords, but misses common variations like 'overdue tasks', 'late tasks', 'missed deadlines', 'task reminders', or 'to-do list'.

2 / 3

Distinctiveness Conflict Risk

The combination of 'Google Tasks' and 'past due' creates a clear, narrow niche that is unlikely to conflict with other skills.

3 / 3

Total

9

/

12

Passed

Implementation

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a concise, well-structured skill that provides concrete CLI commands but falls short on the critical final step of actually identifying and filtering overdue tasks. The workflow would benefit from explicit guidance on date comparison logic and handling multiple task lists.

Suggestions

Add concrete guidance for step 3: specify how to compare due dates against the current date to filter overdue tasks (e.g., a jq filter, date comparison logic, or expected output format).

Address iteration over multiple task lists — clarify whether to loop through all TASKLIST_IDs from step 1 and how to aggregate results.

DimensionReasoningScore

Conciseness

Very lean and efficient. No unnecessary explanations. Every line serves a purpose and assumes Claude knows what overdue tasks are and how to interpret results.

3 / 3

Actionability

Provides concrete CLI commands for listing task lists and tasks, but step 3 ('Review due dates and prioritize overdue items') is vague — it doesn't specify how to filter for overdue tasks (e.g., comparing due dates to current date) or what output to produce.

2 / 3

Workflow Clarity

Steps are sequenced but the final step lacks specificity on how to identify overdue items. There's no validation or feedback loop — e.g., what if no overdue tasks are found, or what if TASKLIST_ID needs to be iterated over multiple lists.

2 / 3

Progressive Disclosure

For a simple skill under 50 lines, the structure is appropriate. The prerequisite skill reference is clearly signaled, and the content is well-organized with no need for additional files.

3 / 3

Total

10

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

10

/

11

Passed

Repository
googleworkspace/cli
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.