- Home
- Skills
- APIs & Backend
- Repair ICS Recurrence Exception Handling
More screenshots
Works with the AI Agents you already use
Repair ICS Recurrence Exception Handling
Repair calendar import/export drift involving RRULE, EXDATE and moved-instance RECURRENCE-ID
$1
Repair ICS Recurrence Exception Handling
Example session with this skill installed
Weekly meeting's moved Wednesday occurrence reappears on Tuesday after ICS round-trip.
Available evidence: ICS files (partial). Additional evidence requested: timezone definitions, importer code, before-after event map. Review this case; identify evidence gaps; do not invent a live test or production action.
- Read your context and instructions
- Compiled the repair ics recurrence
Repair ICS Recurrence Exception Handling — EVIDENCE-LIMITED REVIEW
Scenario received
Weekly meeting's moved Wednesday occurrence reappears on Tuesday after ICS round-trip.
Source register
- S1: ICS files — PARTIAL SOURCE PROVIDED.
- S2: timezone definitions — NOT PROVIDED; REQUIRED TO VERIFY.
- S3: importer code — NOT PROVIDED; REQUIRED TO VERIFY.
- S4: before-after event map — NOT PROVIDED; REQUIRED TO VERIFY.
Verification gates
- reconstruct original and overridden instances. — INCOMPLETE until source evidence is verified.
- match DTSTART timezone to RECURRENCE-ID. — INCOMPLETE until source evidence is verified.
- preserve cancellation and move semantics. — INCOMPLETE until source evidence is verified.
- test DST and all-day boundaries. — INCOMPLETE until source evidence is verified.
Result
INCOMPLETE / EVIDENCE GAPS — evidence does not justify certification of a real-world outcome.
Next steps
- Request verified timezone definitions with source/version context.
- Request verified importer code with source/version context.
- Request verified before-after event map with source/version context.
Decision boundary
No duplicate or resurrected exception; original occurrence must be replaced exactly once.
No changes to external systems, access grants or communications were performed. An authorized owner must approve consequential actions.
Connects securely to your tools. The creator never sees your data.
About this skill
Repair ICS Recurrence Exception Handling is a ToolForge Labs Cursor Skill workflow. Repair calendar import/export drift involving RRULE, EXDATE and moved-instance RECURRENCE-ID.
What this skill checks
- reconstruct original and overridden instances.
- match DTSTART timezone to RECURRENCE-ID.
- preserve cancellation and move semantics.
- test DST and all-day boundaries.
What to provide
- ICS files.
- timezone definitions.
- importer code.
- before-after event map.
Deliverables
- minimal parser patch.
- recurrence fixture gallery.
- round-trip contract.
Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions and missing inputs; no unperformed live tests, external changes, or approvals are claimed.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Cannot verify inaccessible systems or data not supplied. Missing or contradictory evidence must be marked INCOMPLETE or UNVERIFIED. Owner approval is required for operational or compliance decisions.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 20 days ago
Permissions
Provide only evidence you are authorized to share. Treat examples as untrusted case data. Operational changes and external messages require explicit owner approval.