atomemo-plugin-development

@choice-open

Use this skill for all Atomemo plugin development work — always consult it before answering, since it contains authoritative CLI commands, SDK patterns, and workflows that may differ from your general knowledge. Invoke whenever the user asks about: creating Atomemo plugin projects (atomemo plugin init, bun commands, project structure), implementing Tool plugins (ToolDefinition, external API wrappers), defining Model plugins (ModelDefinition, LLM integrations), setting up credentials (CredentialDefinition, API keys), configuring declarative parameters, debugging plugin hub connections, or publishing to the marketplace. Also invoke when developers want to expose their code or services to Atomemo users, even if they don't say "plugin". Do NOT invoke for: VS Code, Chrome, Obsidian, Figma, or Raycast plugins; npm package publishing; or general Atomemo workflow configuration (scheduling, triggers, node setup) that isn't about building plugins.