Files
platform/todo/known-bugs/calendar-skill-never-used-by-an-agent.md
pastilhas 5d51212cca write down what today left unfinished
three, so none of it is re-derived:

agents-md-remaining — the five doc pairs landed; the runtime writers did not,
and that half is BROKEN rather than untidy. commanders, bots and plugin chats
write CLAUDE.md, opencode reads only AGENTS.md, so a commander run under
opencode is briefed with nothing and nothing reports it. names the three writers
by file. the 21 plugin repos are marked as the owner's to lead — not to sweep
unprompted.

marketplace-browse-by-tag — data layer done, UI not started. carries the two
questions that decide the shape: "All" as default, and whether the detail
replaces the grid or sits beside it, which is master-detail vs list-then-page and
contradicts how the screen is deliberately built today.

calendar-skill-never-used-by-an-agent — every recipe was run BY HAND and works;
no agent has ever read the skill and acted on a sentence. those are different
claims and only one of them is tested.
2026-08-27 07:04:05 +00:00

27 lines
1.3 KiB
Markdown

---
id: known-bugs/calendar-skill-never-used-by-an-agent
title: 'The calendar/contacts skill has never been exercised by an actual agent'
theme: known-bugs
status: open
created: 2026-08-27
date_source: stated
order: 9
---
Every recipe in `plugins/caldav/skills/calendar-and-contacts/SKILL.md` was **run by hand** against
alpha's real data and works: create `201`, move `204`, delete `200`, contact create and delete, and the
JSON read for lookups. Isolation was proven too — own account `207`/`201`, another account `403`, spoofed
username `401`.
**What has never happened is an agent reading the skill and acting on a sentence.** "I'm having dinner
Saturday with my wife, add that" has not been said in a chat. A skill can be entirely correct and still
not get picked up — wrong description, wrong trigger words, or simply not surfaced — and that failure
looks identical to the feature not existing.
Five minutes to test, on this machine or alpha. Until it is done, the feature is unproven rather than
working.
The trap it was written to prevent, worth re-checking in the transcript when it IS tested: `date -u -d`
does not convert local to UTC — it parses AND prints as UTC, so "Saturday at 8" becomes 20:00Z, an hour
late in Lisbon. If an agent gets that wrong, the skill's wording is not strong enough.