ics-calendar-reader
Read, parse, and summarize iCalendar (.ics) files from Google Calendar, Apple Calendar, and similar providers. Use when extracting upcoming events, filtering by date range, converting ICS events to JSON/text, or debugging calendar fields like DTSTART/DTEND/TZID/RRULE.
95
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific concrete actions, includes natural trigger terms users would actually say (both consumer-friendly like 'Google Calendar' and technical like 'RRULE'), has an explicit 'Use when' clause with multiple scenarios, and carves out a distinct niche around iCalendar files that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Read, parse, and summarize', 'extracting upcoming events', 'filtering by date range', 'converting ICS events to JSON/text', 'debugging calendar fields'. Also names specific technical fields (DTSTART/DTEND/TZID/RRULE). | 3 / 3 |
Completeness | Clearly answers both what ('Read, parse, and summarize iCalendar files') and when ('Use when extracting upcoming events, filtering by date range, converting ICS events to JSON/text, or debugging calendar fields'). Explicit 'Use when' clause with multiple trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'iCalendar', '.ics', 'Google Calendar', 'Apple Calendar', 'upcoming events', 'date range', 'calendar fields', plus technical terms like 'DTSTART/DTEND/TZID/RRULE' for power users. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on iCalendar/ICS files with distinct triggers like '.ics', 'Google Calendar', 'Apple Calendar', and specific calendar field names. Unlikely to conflict with general file processing or other calendar-unrelated skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently documents a calendar parsing tool with concrete, executable examples and good organization. The main weakness is the lack of explicit error handling or validation steps in the workflow, particularly important when fetching remote URLs that may fail or return malformed data.
Suggestions
Add a validation step in the workflow to handle cases where URL fetching fails or returns invalid ICS data (e.g., 'If the script exits with an error, check that ICS_URLS are accessible and valid')
Include an example of expected error output or how to diagnose common failures (missing env var, invalid URL, malformed ICS)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with Python, environment variables, and CLI tools. No unnecessary explanations of what ICS files are or how calendars work. | 3 / 3 |
Actionability | Provides fully executable commands with specific flags and options. Examples are copy-paste ready with clear parameter variations for different use cases (filtering, caching, output formats). | 3 / 3 |
Workflow Clarity | Steps are listed clearly but lack explicit validation checkpoints. For a workflow involving external URL fetching and parsing, there's no error handling guidance or validation step to confirm successful parsing before downstream use. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Prerequisite, Workflow, Cache, Output Contract, Notes). References external file `references/ics-fields.md` appropriately for detailed field semantics without cluttering the main skill. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- gitstua/stu-skills
- Commit
8dd0dc8
- 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.