Create a calendar event.
Scanned 8/31/2026
Install to Claude Code
npx -y skills add loomax-labs/InferrLM --skill create-calendar-event --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Create Calendar Event?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/loomax-labs-create-calendar-event)More formats (shields.io, HTML) on the badges page.
---
name: Create Calendar Event
description: Create a calendar event.
type: text
---
# Create calendar event
## Instructions
To schedule an event, you must follow these exact steps:
1. First, call the `run_intent` tool with `intent` as `get_current_date_and_time` and `parameters` as `{}` to get the user's local date, time, and the current day of the week.
2. Before creating the event, you must explicitly calculate the exact date in your response. Write out:
- Today's exact date and day of the week.
- The target day or relative time requested by the user (e.g., "tomorrow", "this Friday").
- The exact number of days you need to add to today's date.
- The final calculated dates, ensuring you correctly roll over to the next month or year if the added days exceed the days in the current month.
3. Once you have calculated the correct dates, call the `run_intent` tool with the following exact parameters:
- `intent`: create_calendar_event
- `parameters`: A JSON string with the following fields:
- `title`: the title of the event. String.
- `description`: the description of the event. String.
- `begin_time`: the start time of the event in YYYY-MM-DDTHH:MM:SS format. String.
- `end_time`: the end time of the event in YYYY-MM-DDTHH:MM:SS format. String.
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!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
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', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.