plugin-creator
Scaffold a local Ghosty plugin bundle with a versioned manifest, namespaced Skills, and an explicit trust review.
- License 许可
- MIT
- 最近更新
- 2026-11-01
- Stars
- ★ 8
- Forks
- 0
01 前言 Front Matter
- name
- plugin-creator
- description
- Scaffold a local Ghosty plugin bundle with a versioned manifest, namespaced Skills, and an explicit trust review.
03 SKILL.md 正文
Plugin Creator
Use this skill when a user wants a local Ghosty plugin bundle. Ghosty v0.9.1 has a deliberately bounded loader: trusted and enabled bundles may add declarative Skills and MCP servers through the existing engines. Other component kinds are inventory-only.
Workflow
- Pick a Ghosty-owned location:
- User bundle:
~/.ghosty/plugins/<plugin-name>/ - Workspace bundle:
<workspace>/.ghosty/plugins/<plugin-name>/
- User bundle:
- Normalize the bundle name to lowercase hyphen-case.
- Create
plugin.toml:
schema_version = 1
[plugin]
name = "my-plugin"
version = "0.1.0"
description = "What this bundle provides"
[skills]
path = "skills"
- Put each Skill under
skills/<skill-name>/SKILL.md. Ghosty exposes it asmy-plugin:<skill-name>, never as an unqualified command. - Add
[mcp_servers.<name>]only when the bundle needs an existing MCP engine. Keep stdio commands and paths inside the bundle. Map local environment values only as exact${SOURCE_ENV}references. For remote MCP, use HTTPS (or loopback HTTP), forbid URL user information/query/fragment, use only environment-backed headers or bearer tokens, and declare the exact normalized endpoint host set in[capabilities].network_hosts. Never place credentials in the manifest. - Declare commands, agents, hooks, LSP, native extensions, filesystem roots, or lifecycle mutation only when inventorying future work. Ghosty shows them as inactive and still activates reviewed Skills and MCP from the same bundle. A bundle that only declares those unsupported surfaces cannot be enabled.
- Validate and review without executing bundle content:
/plugin validate <plugin-name>/plugin show <plugin-name>/plugin enable <plugin-name>to open the content/capability review- run the exact
/plugin trust ...confirmation shown, then enable again
- Verify
/skills inspectreports plugin provenance and/plugin listreports the expected trust and activation state. Trust stages the reviewed content but does not activate it; enablement rebuilds the current workspace's Skill/MCP catalogue immediately.
Every user and workspace bundle starts untrusted and disabled. Do not add a marketplace, downloader, updater, compatibility scan, executable extension runtime, or automatic trust flow; those surfaces are outside v0.9.1.
04 同仓库更多 Skills
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
gh-find-prs
Survey open GhostyCode PRs and triage each for mergeability and disposition against the real landing branch.
gh-file-issue
Use when filing a new GhostyCode GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-credit-harvest
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.
gh-compile-issues
Triage N GitHub issues into a coverage matrix: fetch each, check current code, classify already-done/quick-fix/design/defer with cited evidence.
gh-close-issues
Close resolved GhostyCode issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.