Skip to content

Feedback on your automating-calendar skill #2

@RichardHightower

Description

@RichardHightower

I took a look at your automating-calendar skill and wanted to share some thoughts.

Links:

The TL;DR

You're at 96/100, which puts you solidly in A territory (production-ready). This is based on Anthropic's skills best practices. Your strongest area is Spec Compliance (14/15) — the structure is tight and follows conventions perfectly. The weakest is Writing Style (7/10), mainly because of tense inconsistencies in your workflow section.

What's Working Well

  • Spec Compliance is chef's kiss — Your YAML frontmatter is clean, naming conventions are correct, and your description hits all the right trigger terms (JXA calendar scripting, EventKit automation, PyXA calendar automation)
  • Solid Progressive Disclosure Architecture — You've got 10 focused reference files that layer nicely from basics through advanced patterns. The PyXA API reference (846 lines) has a TOC, and the shorter references are lean enough they don't need one
  • Clear error handling patterns — Your validation checklist actually tells people what to check (Calendar.calendars.length > 0), and you provide specific error patterns developers will encounter
  • The legacy vs. recommended distinction — You're transparent about moving from JXA to PyXA, which helps developers make the right choice

The Big One: Workflow Tense Issue

Your workflow section uses past tense instead of imperative. This might seem small, but it adds unnecessary tokens and makes the workflow read like a checklist of things you've already done rather than steps to follow.

Current (6 items with past tense):

4) [ ] Implemented batch reads (avoided heavy `.whose()`).
5) [ ] Added EventKit bridge for advanced queries.
6) [ ] Tested with sample events and verified results.

Should be:

4) [ ] Implement batch reads (avoid heavy `.whose()`).
5) [ ] Add EventKit bridge for advanced queries.
6) [ ] Test with sample events and verify results.

This alone could bump you +2 points to 98/100. It's a quick win — find and replace past tense verbs with their infinitive forms in SKILL.md around lines where your workflow is defined.

Other Things Worth Fixing

  1. Cross-skill reference is vague — You mention "see the installation instructions in automating-mac-apps skill" but don't specify the file path. Link directly to the reference file or just say pip install pyxa (+1 point)

  2. calendar-basics.md is too sparse — Only 23 lines with 3 code examples but no context explaining when to use each approach. Add a sentence or two explaining the use case for each example (+1 point)

  3. Missing anchor links in longer references — Your PyXA API reference is comprehensive (846 lines) but has no navigation anchors beyond the TOC. Consider adding section IDs for internal linking

Quick Wins

  • Highest impact: Fix workflow tense (past → imperative) = +2 points
  • Easy addition: Clarify PyXA installation path = +1 point
  • Content depth: Expand calendar-basics with use-case context = +1 point

These three changes could push you to 99-100/100 with minimal effort.


Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions