todero-create-plugin

Scaffold, install, and verify external Todero plugins using the CLI-first workflow.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/nabitllc/todero --skill todero-create-plugin-nabitllc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todero-create-plugin
Source: https://github.com/nabitllc/todero/tree/main/.agents/skills/todero-create-plugin
Command: npx skills add https://github.com/nabitllc/todero --skill todero-create-plugin-nabitllc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developing a Todero plugin involves many moving parts: scaffolding the package, wiring the manifest, installing it into a running Todero instance, and verifying the build. This Skill guides the entire CLI-first workflow so plugins are created as external packages and installed correctly without touching Todero core. ## Core Features & Use Cases - CLI-first scaffolding: Uses todero plugin init with template, category, and SDK snapshot flags to generate a complete plugin package outside the Todero repo. - Local install and rebuild loop: Installs plugins by absolute local path with todero plugin install, leveraging server-side watching of dist/ output for automatic worker restarts. - Verification and reporting: Runs pnpm typecheck, pnpm test, and pnpm build, then reports scaffold path, install status, and reload limitations. - Use Case: You want to build a new connector plugin for Todero. The Skill scaffolds it into ~/dev/todero-plugins/my-connector, installs it into your local Todero instance, and confirms the plugin reports ready status. ## Quick Start Create a new Todero plugin called @acme/my-plugin, install it into my local Todero instance, and verify it builds and passes tests.

Frequently Asked Questions about todero-create-plugin

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Todero plugin?

Run `todero plugin init @acme/my-plugin --output <dir>` to scaffold a plugin package outside the Todero repo. Then run `pnpm install`, `pnpm dev`, and `todero plugin install <absolute-path>` to load it into your running Todero instance.

How do I install a local Todero plugin for development?

Use `todero plugin install` with an absolute local path; the CLI auto-detects local paths and forwards `isLocalPath: true` to the server. The server watches the plugin's `dist/` output and restarts the worker on rebuild, so reinstalling after each edit is unnecessary.

Should I add my plugin under packages/plugins in the Todero repo?

No. Plugins are external packages and should live outside the Todero checkout unless the task explicitly asks for a bundled in-repo example. Bundled examples also require updating `server/src/routes/plugins.ts` and related docs.

What plugin capabilities are not supported in the current Todero runtime?

The current runtime does not support `ctx.assets`, provides no host-shared plugin UI component kit, and does not sandbox plugin UI by manifest capabilities. Plugin workers and UI run as trusted code, with worker APIs gated by capabilities.

Why is my Todero plugin not hot-reloading after changes?

The server only watches built `dist/` output for local-path plugins, so you must keep `pnpm dev` running to rebuild. Manifest changes may require reinstall, and UI hot reload via `pnpm dev:ui` only works if the template wires `devUiUrl`.