Build or update a ZCode plugin and prepare a local marketplace catalog for testing. The skill checks the plugin files, provides the directory and IDs, and guides you through adding the marketplace, installing or updating the plugin, and trying it in the app.
Create or update ZCode plugin source and a local test marketplace, then guide the user to add, install, update and try it in the app. Use for new plugins or changes to an existing plugin's capabilities, manifest or local distribution.
Run score Not tested
See how to installThis skill helps define a ZCode plugin’s purpose, example input, and expected result, then creates or updates its source and manifest. It implements only the components the plugin needs and checks for placeholders, declared files, and consistent paths. It usually prepares a local marketplace.json for testing, with the plugin name, version, description, and relative path aligned with the source. It then guides you through adding the marketplace, installing or updating the plugin, and trying it in the app.
Use it to prototype a plugin, change an existing plugin’s features or manifest, or prepare local distribution for testing. It supports a handoff where the agent prepares files and you use the app interface to add the marketplace, install the plugin, and check its behavior.
You add the marketplace and install or update the plugin yourself in the app. This skill does not publish plugins. An MCP server scaffold only checks the connection and returns an empty tool list; real tools must be implemented for actual functionality. The skill says it will report when checks that depend on the runtime or credentials cannot be completed.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 24, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Deliver implemented plugin source, a local dev marketplace catalog, and precise UI instructions for the user to add the market, install/update the plugin and try it. Use ZCode manifests.
The current handoff is manual. Do not register markets, install/update/enable plugins, or publish as part of this skill. Ordinary Desktop users are not expected to have a global zcode CLI or node command. Use existing file tools when helper runtimes are unavailable; do not ask users to install development tooling to complete the UI steps. A skill reference alone has no plugin requirements: ask what the plugin should do before generating files.
Read the target workspace's instructions. Reuse the user's choices for purpose, name, components and destination. Define a representative input and observable expected result for the capability; use it for the smoke test and final trial prompt.
Default source location: <workspace>/plugins/<slug>/. An explicit directory wins. Work on the target host for remote work. For an existing plugin, inspect its manifest and edit the original source while retaining its identity.
Read the ZCode manifest reference before choosing components. This step is complete when the source location and acceptance example are concrete.
Create .zcode-plugin/plugin.json and only the components the plugin needs. The directory name and manifest name must match. Use the available file tools, or the optional bundled scripts/create-basic-plugin.mjs helper when Node is already runnable. Helper options and examples are in the manifest reference.
Implement the requested capability and replace generic scaffold descriptions with its purpose. The generated MCP server only implements a handshake and an empty tool list; implement real tools before reporting a working integration. Keep secrets in user-config/environment/credential mechanisms.
Preserve existing source. Ordinary iteration edits implemented files and increments the manifest's semantic version; it does not re-scaffold with --force. This step is complete when the requested files and behavior have been implemented, or a specific blocker is recorded.
Check manifest JSON, declared resource existence, directory/name consistency, path containment and unresolved placeholders. Run the representative capability smoke test with available tools. Report unavailable runtime or credential-dependent checks explicitly.
In an existing developer environment, scripts/validate-plugin.mjs can additionally invoke zcode plugins validate; use its --cli override only when an actual working entry is already known. This is optional developer verification, not a prerequisite or a command to give ordinary Desktop users. File inspection alone does not prove ZCode schema validation or runtime execution.
Unless the user requested source-only delivery, create or update <workspace>/plugins/marketplace.json beside the plugin directories. Its entry uses the plugin manifest's name, version and description, a relative source path, and appropriate display/localized metadata. Preserve unrelated entries, metadata and order.
When Node is available, use scripts/upsert-dev-marketplace.mjs with the actual plugin path. It returns the marketplace ID, full plugin ID and paths; its directory-based dev ID is stable. Pass an existing chosen catalog explicitly with --marketplace-path to retain its name. Without Node, use the file tools and the reference's catalog format, choose a distinct dev- prefixed name for a new market, and retain that saved name on later edits. Resolve same-name/different-source conflicts rather than replacing another entry or market.
Read manual installation, updates and trial for every handoff. This step is complete when the catalog and plugin files exist and their IDs, versions and paths agree. Creating the catalog does not register a market or install a plugin.
Provide the actual market root directory and instruct the user to open Plugin Marketplace → Add → Add Plugin Marketplace, paste that directory, and add it. Then use Personal → the actual market name → plugin → Install. Follow the reference for updates and failures.
Give a concrete new-task trial prompt with its expected result. For a skill, tell the user to select the installed plugin/skill from the composer picker after installation. Only provide an installed SKILL.md reference if its actual path has been observed; a source path is not an installed reference. Preserve the user's disabled choices and explain any needed manual enable/configuration step.
Reply in the user's language with:
If the user has not completed the UI steps, stop with a usable handoff rather than performing them automatically or claiming success. For a reported error, keep the source, inspect the error and correct the relevant source/catalog issue. Public release remains separate from local testing.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create a 3D object with three.js, inspect it from every angle in an interactive viewer, and download it as OBJ + MTL or GLB for use in other 3D applications.
Maintain a private task list with deadlines, next steps, waiting parties, and blockers. Update progress and dependencies, merge duplicate items, and archive closed tasks so ongoing commitments stay clear and easy to follow.
Coordinate a task from a verifiable goal through completion. Handle work directly or split independent tasks across separate agent sessions, track progress, verify results, and arrange pull request merging when included in the goal.
Create animated HTML pages with smooth scene transitions and playback controls. An editable timeline lets users adjust scene lengths and speeds, with fixed landscape or portrait layouts prepared for video export.
Review synced Apple Health records, including steps, heart rate, sleep, and workouts. Retrieve daily summaries or detailed samples for a chosen period, and check sync status and missing data before interpreting the results.
Create and edit Word documents and templates, reorganize text, replace images, and work with tracked changes or comments. Apply proper headings and lists, then render every page to check its appearance before delivery.