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.

Quality

93%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

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 is concise, actionable, and well-structured. It provides concrete CLI commands, a clear output contract, and appropriate security guidance around private URLs. The main weakness is the lack of explicit error-handling or validation steps in the workflow — there's no guidance on what to do when things go wrong (malformed ICS, network failures, missing dependencies).

Suggestions

Add a brief error-handling section or validation checkpoint in the workflow (e.g., 'If the script exits with an error about missing ICS_URLS, prompt the user to configure ~/.config/stu-skills/ics-calendar-reader/.env')

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It avoids explaining what ICS files are or how calendar parsing works conceptually. Every section provides specific, actionable information that Claude wouldn't already know (script paths, CLI flags, env var names, output schema). The .env sample and cache details are necessary operational context.	3 / 3
Actionability	Provides fully executable CLI commands with concrete flags and arguments for every use case (JSON output, date filtering, text output). The output contract specifies exact field names. Environment variable setup is explicit with example values and exact file paths.	3 / 3
Workflow Clarity	The workflow steps are clearly sequenced and cover the main use cases (parse, filter, display). However, there are no validation or error-handling checkpoints — no guidance on what to do if the script fails, if the ICS file is malformed, or if the env var is misconfigured. The script's error behavior is mentioned (exits with instruction) but no feedback loop for recovery is provided.	2 / 3
Progressive Disclosure	Content is well-organized into logical sections (Prerequisite, Workflow, Cache, Output Contract, Notes) with appropriate depth for a SKILL.md overview. References `references/ics-fields.md` for deeper field semantics and delegates actual parsing to `scripts/read_ics.py`, keeping the skill file focused on usage patterns.	3 / 3
	Total	11 / 12 Passed

Description

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 a comprehensive set of natural trigger terms spanning both casual and technical usage, explicitly states both what the skill does and when to use it, and occupies a clearly distinct niche that won't conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: read, parse, summarize iCalendar files, extract upcoming events, filter by date range, convert ICS events to JSON/text, and debug calendar fields with specific field names (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') with an explicit 'Use when' clause and multiple trigger scenarios.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: '.ics', 'iCalendar', 'Google Calendar', 'Apple Calendar', 'events', 'date range', 'ICS', plus technical terms like 'DTSTART', 'DTEND', 'TZID', 'RRULE' that power users would reference.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche focused on iCalendar/.ics files with specific calendar providers and ICS-specific field names. Very unlikely to conflict with other skills given the narrow domain of calendar file parsing.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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: 3fe35d2

Reviewed: 22 days ago

Table of Contents

Discovery Implementation Validation

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.