Stats
Actions
Tags
From Leadtime
Use only when the user wants to build scripts, automations, or external integrations against the Leadtime Public API.
How this skill is triggered — by the user, by Claude, or both
Slash command
/leadtime:leadtime-public-apiThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill only when the user asks Claude to build, debug, or plan scripts, automations, Zapier/n8n-style connectors, or other external integrations with the Leadtime Public API.
Use this skill only when the user asks Claude to build, debug, or plan scripts, automations, Zapier/n8n-style connectors, or other external integrations with the Leadtime Public API.
For normal Leadtime workspace operations inside Claude, prefer the bundled Leadtime MCP connector instead of telling the user to create a personal access token.
For integration work, check the user's available API docs, workspace-specific credentials, and integration requirements before proposing endpoints. Keep credentials out of prompts, source files, logs, and generated examples. Use bearer-token examples with placeholders unless the user has explicitly provided a safe local test token.
When writing rich content through the Public API, use HTML for Leadtime editor fields unless the endpoint schema says otherwise. Read action details for the endpoint and follow the field's supported nodes and marks.
When updating official Leadtime integrations, keep Zapier, n8n, public API DTOs/controllers, and integration docs aligned with the changed API surface.
npx claudepluginhub workcio/claude-leadtime-plugin --plugin leadtimeGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.