recipe-review-overdue-tasks
Find Google Tasks that are past due and need attention.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-review-overdue-tasks59
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 identifies a specific domain (Google Tasks) and a focused use case (past due items), but lacks explicit trigger guidance and comprehensive action coverage. The absence of a 'Use when...' clause significantly weakens Claude's ability to reliably select this skill, and the limited trigger terms may miss common user phrasings.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about overdue tasks, late Google Tasks, missed deadlines, or wants to review incomplete todos in Google Tasks.'
Expand trigger terms to include natural variations: 'overdue', 'late', 'missed deadline', 'incomplete tasks', 'todo list'
Consider adding more specific actions beyond 'find' such as 'list', 'review', or 'prioritize' to clarify the skill's full capabilities.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Tasks) and one action (find past due tasks), but lacks comprehensive actions like listing, updating, or managing tasks. | 2 / 3 |
Completeness | Describes what it does (find past due Google Tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Google Tasks' and 'past due' which are relevant, but misses common variations like 'overdue tasks', 'late tasks', 'task deadlines', or 'todo' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Specific to Google Tasks which helps distinguish it, but 'past due' and 'need attention' could overlap with other task management or reminder skills without clearer boundaries. | 2 / 3 |
Total | 7 / 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 skill that provides good CLI commands but falls short on actionability in the final step. The workflow would benefit from explicit guidance on filtering/identifying overdue tasks (e.g., comparing due dates to current date) and concrete next actions rather than the vague 'prioritize overdue items'.
Suggestions
Add specific guidance on how to identify overdue tasks (e.g., filter criteria or date comparison logic)
Replace vague 'prioritize overdue items' with concrete actions like updating due dates, marking complete, or creating follow-up tasks
Consider adding an example output showing what overdue tasks look like in the table format
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient - no unnecessary explanations, assumes Claude knows what overdue tasks are and how to interpret results. Every line serves a purpose. | 3 / 3 |
Actionability | Provides concrete CLI commands which is good, but step 3 'Review due dates and prioritize overdue items' is vague - doesn't specify how to identify overdue items or what actions to take with them. | 2 / 3 |
Workflow Clarity | Steps are sequenced but lack validation checkpoints. No guidance on what to do if no overdue tasks are found, how to filter for overdue specifically, or what 'prioritize' means in practice. | 2 / 3 |
Progressive Disclosure | For this simple skill, the structure is appropriate - clear prerequisite callout, concise steps, no need for external references given the scope. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- 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.