chronary-api
Core REST API — data model, all endpoints, authentication, error handling, ID prefixes.
Chronary publishes a set of Agent Skills and IDE plugins that teach AI coding assistants — Claude Code, Cursor, VS Code Copilot, OpenAI Codex, and Windsurf — how to use the Chronary API correctly. They contain reference material only, no executable code.
chronary-api
Core REST API — data model, all endpoints, authentication, error handling, ID prefixes.
chronary-toolkit
@chronary/toolkit — 23 tools with adapters for Vercel AI SDK, OpenAI, LangChain, Mastra, and MCP.
chronary-mcp
@chronary/mcp — MCP server setup snippets for Claude Desktop, Cursor, VS Code, Claude Code, and Windsurf.
chronary-cli
chronary CLI — command reference, scripting patterns, automation recipes.
Plus three reference documents: TypeScript SDK method signatures, end-to-end code examples, and all 12 webhook event payload schemas.
Inside Claude Code:
/plugin marketplace add Chronary/chronary-skills/plugin install chronary@chronaryThat installs the chronary plugin with all four skills, three slash commands (/check-availability, /manage-calendar, /schedule-event), and the MCP server configuration.
git clone https://github.com/Chronary/chronary-skills.gitcp -r chronary-skills/skills/* ~/.cursor/skills/Restart Cursor and prompt: “What webhook events does Chronary emit?” — the SKILL.md citation should list all 12.
VS Code Copilot reads Agent Skills from .github/skills/:
git clone https://github.com/Chronary/chronary-skills.gitcp -r chronary-skills/.github/skills/* /path/to/your/project/.github/skills/Commit .github/skills/ so your team picks up the skills automatically.
Codex reads skills from ~/.codex/skills/ (user-level) and AGENTS.md per-project from each project’s repo root. Install user-level skills, then drop AGENTS.md into each project that uses Chronary:
git clone https://github.com/Chronary/chronary-skills.gitcp -r chronary-skills/skills/* ~/.codex/skills/cp chronary-skills/AGENTS.md /path/to/your/project/AGENTS.mdgit clone https://github.com/Chronary/chronary-skills.gitcp -r chronary-skills/skills/* ~/.windsurf/skills/The repo ships installer scripts that detect your platform and copy skills into the right directory:
# macOS / Linux / WSLcurl -fsSL https://raw.githubusercontent.com/Chronary/chronary-skills/main/install.sh | bash
# Windows PowerShelliwr -useb https://raw.githubusercontent.com/Chronary/chronary-skills/main/install.ps1 | iexBy default it installs into all user-level locations (Claude Code, Cursor, Windsurf, Codex). Pass a single target to limit it:
curl -fsSL https://raw.githubusercontent.com/Chronary/chronary-skills/main/install.sh | bash -s -- claude-codeTargets: claude-code · cursor · windsurf · vscode · codex · all.
The Chronary MCP server is published to npm as @chronary/mcp. The skill pack includes per-editor configuration for it, but the minimal usage is:
export CHRONARY_API_KEY=chr_sk_...npx -y @chronary/mcpFor Claude Desktop, Cursor, VS Code, Claude Code, and Windsurf JSON config snippets, see the MCP setup guide or the chronary-mcp skill in the pack.
Skills don’t run code in your editor. They sit in your skills directory and load when the AI assistant decides the conversation is about Chronary. After installing, you should see citations to SKILL.md files when your assistant answers questions like:
If you don’t see the citation, the skill isn’t loaded — re-check the install path for your editor.