scaffold-plugin
Skill2 starsChanged 16 days agoMITView on GitHub
Create a new Heinzelmännchen plugin repository from the copier template, or update an existing plugin to the latest template. Use when asked to create, scaffold or bootstrap a Heinzelmännchen plugin, or to bring a plugin up to date with Heinzelmännchen's standards.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- TrogonStack/agentskillstheir own version, first seen Oct 11, 2026
- g-bastianelli/nuthousetheir own version, first seen Sep 2, 2026
- farzanmrz/meta-devtheir own version, first seen Jul 6, 2026
- arimxyer/toolchesttheir own version, first seen Jun 12, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- TrogonStack/agentskills★ 11same name
- arimxyer/toolchest★ 1same name
- g-bastianelli/nuthouse★ 1same name
- farzanmrz/meta-dev★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/CLAUDE.mdCLAUDE.md
- starter/CLAUDE.mdCLAUDE.md
- template/CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- add-moduleSkill
- add-operationSkill
- codifySkill
- raise-the-barSkill
- releaseSkill
- reviewSkill
- self-auditSkill
- ship-smallSkill
- write-adrSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read the author guide, including the separate public/private repository paths.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Scaffold a plugin
New plugin
Read the author guide, including the separate public/private repository paths.
- Outside an existing Git repository, run
hz system plugin new heinzel-<name> --defaults --data plugin_name=<name>. The minimal preset is one operation and behavior test; use--preset contributionsonly when settings, views, Today or notifications are useful. cd heinzel-<name> && make setup && make check-fast. Setup initializes Git and creates the owning lock and environment. Follow generated AGENTS.md; CLAUDE.md uses the same instructions.- Edit the owning operation and behavior test. Use public
heinzel/heinzel.kernelcontracts. A model or service is optional. Add ordinary dependencies to the owning pyproject, thenmake lock. make fix,make check-fast,make check,make build,make acceptance;make previewuses isolated state. These commands use installed artifacts and never run the core suite.CORE=<wheel>selects a candidate SDK.- Host in the requested public or private repository, and add topic
heinzel-pluginfor catalog discovery. Private installation uses the installing person'sghlogin.make releasepreviews; after review and merge,make publishselects private GitHub or public PyPI publication. Public PyPI needs the owning trusted publisher; private sources must stay off PyPI. Independent tags are<distribution>/v<version>.
Inside an existing repository, use hz system plugin new plugins/heinzel-<name> --defaults --layout collection
--data plugin_name=<name>, or the host's optional new shortcut with NAME=<name>. Keep all feature files in the new
directory and run the same owning Make commands from there. Root NAME=<owner> shortcuts are optional. Never
create an embedded repository or copy parent workflows.
Update an existing plugin
From a clean owning repository, run uvx copier update --defaults --vcs-ref vX.Y.Z, resolve conflicts, refresh its
lock and run owning checks/build/acceptance. Commit as chore(template): update to heinzel vX.Y.Z. Retained governed
repositories also have the make update-template wrapper. Do not replace owning source or tests with another plugin.
New templates live in starter/; template/ retains the governed layout. make template-test checks both against
installed core/toolkit artifacts, including a new authored operation in each small preset and layout.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

