skills.rest
AIDotNet
AIDotNetOFFICIAL
Explore all skills by this author →
WebsiteGitHub

create-extension

Create and validate OpenCowork V1 custom extension folders from manifest-driven workflows.

602|121|Updated Feb 10, 2026
Search Tags:#validation#scaffolding#plugin#extension#manifest#opencowork
One-click install
npx skills add https://github.com/AIDotNet/OpenCowork --skill create-extension-aidotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-extension
Source: https://github.com/AIDotNet/OpenCowork/tree/main/resources/skills/create-extension
Command: npx skills add https://github.com/AIDotNet/OpenCowork --skill create-extension-aidotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill removes the guesswork from creating OpenCowork custom extensions by guiding you through the correct folder structure, manifest rules, tool wiring, and validation steps.

Core Features & Use Cases

  • Extension Scaffolding: Generate a valid OpenCowork V1 extension folder with the right manifest and optional runtime files.
  • Template Selection: Choose the smallest workable template for a minimal JS tool, a declarative HTTP tool, or a UI-focused extension with a custom HTML renderer.
  • Validation and Handoffs: Check that tool names, handlers, renderers, and network permissions are correctly defined before the extension is installed.
  • Use Case: A developer wants to add a company search tool or a status dashboard inside OpenCowork and needs a reliable way to scaffold, customize, and ship the extension safely.

Quick Start

Ask the AI to create an OpenCowork custom extension for your use case, then customize the generated files and validate the folder before installing it in Settings -> Extensions.

Frequently Asked Questions about create-extension

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

FAQPage Schema
How do I create an OpenCowork V1 custom extension?▼

To create an OpenCowork V1 custom extension, generate a valid folder containing an extension.json manifest, optional index.js and renderer.html files, then validate tool references and network permissions before installing in Settings.

What is the correct folder structure for OpenCowork plugin development?▼

OpenCowork plugin development requires an extension.json manifest at the root, alongside optional index.js for JavaScript logic and renderer.html for UI components to ensure proper tool wiring and validation.

Can I build an HTML renderer UI component for an OpenCowork extension?▼

Yes, you can build an HTML renderer UI component for an OpenCowork extension by selecting a UI-focused template that includes a custom renderer.html file alongside the required extension.json manifest.

Do I need to define network permissions for declarative HTTP tools in OpenCowork?▼

Yes, you must define network permissions when using declarative HTTP tools in OpenCowork to allow fetch-based handlers, ensuring the extension validates correctly before installation in Settings.

Why does my OpenCowork extension validation fail before installation?▼

OpenCowork extension validation fails when tool names, handlers, renderers, or network permissions are incorrectly defined in the extension.json, preventing the extension from being safely installed in Settings.

Related Skills

Explore More Software Engineering Skills→
bl1nk-botbl1nk-bot
2

extension-architect

Scaffold and validate Gemini CLI extensions with standardized manifests.

Official
Intermediate
arbisoftarbisoft
4

bun-runtime

Run JavaScript and TypeScript projects with Bun runtime, package manager, bundler, and test runner.

Official
Intermediate
malloydatamalloydata
95

html-data-app-runtime

Execute Malloy queries from JavaScript to build interactive HTML data applications.

Official
Intermediate
VMRam95VMRam95

plugin-creator

Scaffolds Codex plugin directories and updates marketplace.json manifests.

Community
Intermediate