silo-extension-builder

Solid

Help the user design, write, compile, and install a Silo extension from a natural-language description. The extension follows the same format as any publishable Silo extension and can be shared via npm or a tarball URL when ready.

Code & Development 56 stars 5 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
58
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Extension Builder Turn a natural-language description into a working Silo extension. The extension is real, publishable TypeScript — not a prototype or a hack. `silo install` drops it into Silo immediately; `silo uninstall` removes it cleanly. ## Arguments The skill accepts two optional arguments: `id` and `path`. - **`id`** — the extension id (e.g. `dave.clock`). If not provided, ask the user. - **`path`** — the directory to create the extension in. If not provided, default to `/tmp/silo-ext/<id>` and confirm with the user. Parse arguments from the invocation line. Examples: - `/silo-extension-builder id=dave.clock` — id given, use default path - `/silo-extension-builder path=~/projects/my-ext` — path given, ask for id - `/silo-extension-builder id=dave.clock path=~/projects/my-ext` — both given, skip both questions - `/silo-extension-builder` — neither given, ask for both before proceeding ## Workflow (always in this order) 1. **Resolve args** — extract `id` and `path` from the invocation; ask the user for any that are missing 2. **Scaffold** — run `npx create-silo-extension` to create the directory structure and manifest 3. **Plan** — identify which `ctx.*` APIs the extension needs (see API Reference below) 4. **Write** the implementation to `<path>/src/index.tsx` (overwrites the scaffold placeholder) 5. **Compile** with esbuild (output to `<path>/dist/index.js`) 6. **Ask** — show the user the compiled output path and ask if they want to install it now 7. **Insta...

Details

Author
silo-code
Repository
silo-code/silo
Created
3 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

chrome-extension-developer

Ultimate Codex workflow for Google Chrome extension work: Manifest V3, WXT, Plasmo, CRXJS, content scripts, service workers, popup UI, side panel, permissions, testing, security review, payments, assets, and Chrome Web Store publishing.

0 Updated 1 months ago
andrewr303
AI & Automation Listed

extension-dev

Build, debug, and publish cross-browser extensions (Chrome, Edge, Firefox, and any Chromium- or Gecko-based browser such as Brave, Opera, Vivaldi, Yandex, Waterfox, or LibreWolf, plus Safari) with the extension.dev framework. Use this skill whenever the user mentions browser extensions, Chrome extensions, Firefox add-ons, Safari web extensions, WebExtensions, Manifest V3, manifest.json, content scripts, service workers, side panels, popups, options pages, chrome.* or browser.* APIs, or publishing to the Chrome Web Store or Firefox Add-ons, even if they never name extension.dev or Extension.js explicitly. Also use it when debugging why an extension does not load, inject, or update.

0 Updated 2 weeks ago
extensiondev
Data & Documents Listed

dxkit-author-extension

Write a dxkit extension FOR the user from a prose description of what they want extracted, verified, or delivered — pick the lowest rung (declared artifact → external script → TypeScript plugin), generate the manifest/adapter/plugin, and drive `extensions dev` until green. Use when the user describes a bespoke convention ("our screens are JSX files with a <Screen> root", "our API client is acmeApi.request", "our permissions are hasPermission() calls") or asks to port an existing extractor/report script into dxkit.

10 Updated today
vyuh-labs