getting-started · diff
git:20260902.51907d6 to git:20260908.2b7f821
19 added, 20 removed. Audit A to A.
---
name: getting-started
- description: Explains what this plugin provides and how to extend it with new Skills.
+ description: Explain this plugin’s current Skills or help add a new Skill to its source.
---
# Getting started
- ## When to use
-
- Use this Skill when someone asks what this plugin can do, or how to add a new
- capability to it.
-
- ## What this plugin provides
-
- This plugin currently ships one Skill — this one. It was scaffolded from the
- `minimal` template of `create-agent-bundle`, which is the smallest complete
- agent-bundle project: one config, one Skill, and a delivery gate.
+ Inspect the plugin's current Skills before describing it: use `src/skills/` in
+ the source project, the installed `skills/` directory for Claude, Codex, Cursor,
+ or portable, and `.amp/plugins/<plugin>/skills/` for Amp. Capabilities may have
+ changed since scaffolding. The minimal template starts with this Skill, one
+ config, and a delivery check.
## How to add a Skill
1. Create `src/skills/<skill-id>/SKILL.md` with `name` and `description`
- frontmatter. The `name` must match the directory name.
- 2. Add supporting material under `references/` (read-only context) and
- `assets/` (files the agent fills in or copies).
+ frontmatter. The `name` must match the directory name; describe the specific
+ task that should activate it, without attracting unrelated requests.
+ 2. Keep useful shared instructions in `SKILL.md`. Add substantial conditional
+ detail under `references/` only when needed, linking it with a clear read
+ condition. Use `assets/` for templates or files the agent fills in or copies
+ into its deliverable; a short Skill needs neither directory.
3. Leave `agent-bundle.config.ts` unchanged unless overriding the conventional
Skill layout.
- 4. Run the project's `check` script: it validates the config, builds every
- host artifact, and runs the tests.
-
- ## Final report requirements
+ 4. After adding or changing a Skill, run the project's `check` script: it
+ validates the config, builds every host artifact, type-checks, and runs the
+ tests.
- When answering with this Skill, name the Skills the plugin currently ships
- and cite the exact files a new Skill needs.
+ Keep the workflow within the request and preserve existing authorization.
+ Avoid mandatory plans, audits, or approval pauses for simple informational
+ questions. Report the current capabilities or completed edit and validation,
+ including any concrete limitation.