Installs repository-owned procedure skills with per-host wrappers and stamps them in config.json.
npx skills add https://github.com/JSdotNet/devbook --skill init-jsdotnet
Please help me install this Agent Skill. Skill: init Source: https://github.com/JSdotNet/devbook/tree/main/plugins/devbook-procedures/skills/init Command: npx skills add https://github.com/JSdotNet/devbook --skill init-jsdotnet
.agents/skills/ plus a managed SKILL.md wrapper under .claude/skills/ and .github/skills/ carrying the fixed goal and pointer. - Ownership detection: Hashes files already on disk, asks once per procedure whether to keep an unstamped file as the repository's own or replace it with the seed, and never merges a newer seed into a customized file. - Plan-before-write and stamping: Always presents a create/update/skip-customized plan before writing, then records components.devbook-procedures with plugin version, adopted entries, and materialized hashes in .devbook/config.json. - Use Case: A team adopting devbook-procedures runs init once to seed the start and capture skills, keeps their existing customized debug skill untouched, and gets a stamped config entry so future runs go through update instead. ## Quick Start Run devbook-procedures init to seed the start, show, capture, and debug procedure skills into this repository.High-intent search queries and answers about installing and using this skill.
Run devbook-procedures init once. It asks which of the four procedures (start, show, capture, debug) to adopt, writes each as an editable copy under .agents/skills/, and adds a managed wrapper per host under .claude/skills/ and .github/skills/.
The run is refused when components.devbook-procedures already exists in .devbook/config.json. It reports "already initialized, run devbook-procedures:update" and stops without writing anything.
No. Init hashes files on disk and only overwrites a file whose hash matches a release the plugin shipped. A file with an unknown hash is treated as the repository's own, reported, and left untouched.
The copy under .agents/skills/ holds the procedure content and is the repository's to edit. The wrapper under .claude/skills/ and .github/skills/ is managed by the plugin and carries only the fixed goal and a pointer, so it is replaced without asking.
It writes only the components.devbook-procedures entry, recording pluginVersion, the adopted procedures, and materialized entries with the release each file came from and the hash it had when it landed. No other config entry is touched.
ValorVieSend Claude Code event alerts to Telegram or Discord via plugin hooks.
isen-ngCreate a Homebrew cask stub for a new dotnet-sdk version and run the auto_updater.
DarkbluelrCreate auditable proposal.md entries with Why/What/Impact and Debate Packets.
Tehzeeb07Routes Convex backend tasks to bundled capability skills and a served procedure catalog.