CtrlK
BlogDocsLog inGet started
Tessl Logo

schedule-management

Local schedule management for adding events, tracking deadlines, generating reminders, and detecting time conflicts when users need offline scheduling with optional popup notifications.

68

Quality

84%

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

76%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 actionable and well-structured with executable examples and a genuine one-level reference, but it leans slightly redundant and lacks explicit validation checkpoints for its batch and data-writing operations. Tightening repetition and adding validate-fix-retry steps would lift the workflow score.

Suggestions

Add explicit validation checkpoints to the batch/data workflows — e.g., after 'import' or 'add', show how to run 'list' or 'conflicts' to verify the operation succeeded and what to do on a validation error.

Trim redundancy between 'Key Features', 'Implementation Details', and the worked examples so each section earns its place without restating the others.

Strengthen the progressive-disclosure pointer by replacing 'Additional examples may be available in references/examples.md' with a direct link like 'See [examples.md](references/examples.md) for import-from-CSV and Task Scheduler setup.'

DimensionReasoningScore

Conciseness

Lean and free of padding about concepts Claude already knows, but 'Key Features' and 'Implementation Details' partly restate the 'When to Use' section and the worked examples, leaving minor tightening opportunities rather than a fully trimmed level 5.

4 / 5

Actionability

Five copy-paste-ready 'python scripts/schedule_tool.py' command blocks with all flags plus a PowerShell notifier command fully cover the common cases, matching the score-5 anchor.

5 / 5

Workflow Clarity

Steps are clearly sequenced (add, list, conflicts, reminders, optional popup) but the workflows involve batch ('import') and data-writing ('add') operations with no explicit validate-fix-retry checkpoints, which caps the score at 3 per the destructive/batch guideline; it is not below 3 because the sequence itself is coherent.

3 / 5

Progressive Disclosure

Well-organized overview with a real one-level-deep reference to 'references/examples.md' (a verified file) and real scripts, but the pointer is hedged ('may be available') rather than crisply signaled, keeping it just below the level-5 clear-navigation anchor.

4 / 5

Total

16

/

20

Passed

Description

92%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 strong: concrete, third-person, and explicit about both capabilities and trigger conditions, with a clearly scoped offline-scheduling niche. The only soft spot is trigger-term breadth, where a few natural synonyms (calendar, appointments, meetings) are absent.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'adding events, tracking deadlines, generating reminders, and detecting time conflicts' — with comprehensive coverage of the skill's operations, matching the score-5 anchor rather than the minor-gaps level 4.

5 / 5

Completeness

Explicitly states both what ('adding events, tracking deadlines, generating reminders, and detecting time conflicts') and when ('when users need offline scheduling with optional popup notifications') in third person, matching the clear what-and-when anchor.

5 / 5

Trigger Term Quality

Includes natural terms users would say ('adding events', 'deadlines', 'reminders', 'time conflicts', 'offline scheduling') but misses common synonyms like 'calendar', 'appointments', or 'meetings', placing it above the midpoint between good coverage (4) and comprehensive (5).

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche of local/offline-only scheduling with optional popup notifications, with distinct triggers and minimal overlap risk with other skills, matching the score-5 anchor.

5 / 5

Total

19

/

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.