Build .ics calendar files in a Code node or CodeAct action, with ics running on the host
Scanned 9/1/2026
Install to Claude Code
npx -y skills add nodetool-ai/nodetool --skill sandbox-ics --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Sandbox Ics?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/nodetool-ai-sandbox-ics)More formats (shields.io, HTML) on the badges page.
---
name: sandbox-ics
description: Build .ics calendar files in a Code node or CodeAct action, with ics running on the host
---
# iCalendar in the sandbox
Specifier: `@nodetool-ai/sandbox-ics`. Import it at the top of the body.
The published ics bundle does not compile into QuickJS, so this pack is a
**host module**.
## createEvent — one event
```js
import { createEvent } from "@nodetool-ai/sandbox-ics";
const ics = await createEvent({
title: inputs.title,
start: inputs.start,
duration: { hours: 1 },
location: inputs.location
});
return { ics };
```
`start` is `[year, month, day, hour, minute]`, e.g. `[2026, 8, 15, 10, 0]`.
## createEvents — many
```js
import { createEvents } from "@nodetool-ai/sandbox-ics";
const ics = await createEvents(inputs.events);
return { ics };
```
## Gotchas
- **Throws on a bad event.** The host unwraps ics's `{ error, value }` bag.
- **Pair with `@nodetool-ai/sandbox-rrule`** to expand a series first.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...