devbook-config
v1.0.0Owns a repository's .devbook/config.json and explains the stack that reads it. `setup` writes the engine-owned keys — bindings, extensions, policy, gates — before anything is installed, then hands every component its own install skill; `update` moves the whole configured stack forward in one run, fanning out to every adopted component’s own install skill and skipping what this machine has not installed or this checkout has not enabled, migrations included; `guide` answers a question about this marketplace from what is on disk — what devbook, the delivery engine, the bridges, the surfaces, and the fan-out lane are and how they fit, which version of each plugin is installed against the newest published, and which are enabled; `adoption` reports where the .ai adoption record no longer matches what is installed and hands the write to flow-ai. All four are backed by a read-only report that names the file behind every fact. Declares no dependency, devbook included: it is named for the folder it writes into, not for a plugin it needs, and one it names but cannot find is reported as not installed.
By Job SchepersLicense: MIT0 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 4 skill or MCP entries
- Source updated
- Sep 14, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install devbook-config for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install devbook-config@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/JSdotNet/ai-agent-stackClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/devbook-config/.
Plugin files
├── .claude-plugin/plugin.json├── skills/adoption/SKILL.md├── skills/guide/SKILL.md├── skills/setup/SKILL.md└── skills/update/SKILL.md
Included Skills4
Check whether a repository's .ai adoption record still describes the stack it actually has — which plugins are installed and enabled, which flows and schedules the copies on disk ship, and what the stack config wires — then hand every edit to flow-ai. Reports drift; never writes a chapter and never rates one. Use when: the adoption record has gone stale after an upgrade, a plugin was added or removed, or you are reviewing how this repository works with AI. Triggers on: "refresh the adoption record", "is my .ai still accurate", "update .devbook/ai", "which plugins are missing from the adoption map", "does the ai folder match what is installed".
Answer a question about this marketplace and the plugins in it — what devbook, delivery, the bridges, the surfaces, and the fan-out lane are and how they fit together, which version of a plugin is installed against the newest one published, which plugins are enabled here, and how this repository has wired its flows, roles, gates, and policy. Reads only; it never installs or reconciles anything. Use when: asking how the stack works, comparing installed against newest, checking what is enabled, or reading a repository's flow wiring. Triggers on: "what is devbook", "explain the delivery engine", "how do the plugins fit together", "which version am I on", "is there a newer version", "which plugins are enabled", "how are my flows set up", "what does this repo bind", "which gates are on".
Set a repository up for this marketplace for the first time — decide which plugins it will actually use, write the engine-owned keys of .devbook/config.json (bindings, extensions, policy, gates), validate them against the schema, and then hand each component its own install skill to materialize what it installs. Writes the engine keys only, never another component's stamp. Use when: adopting the stack in a repository, wiring flows for the first time, or creating the stack config. Triggers on: "set up the stack here", "adopt the delivery engine", "create the stack config", "create .devbook/config.json", "wire up my flows", "onboard this repo".
Move a repository's whole configured stack forward in one run — refresh the catalog, report which installed plugins are behind, then fan out to every adopted component's own install skill so outstanding migrations run and stale files are re-materialized, and re-validate the engine-owned keys of .devbook/config.json and its local overlay. Skips what this machine has not installed and what this checkout has not enabled, without ever dropping a stamp. Use when: upgrading the stack, a plugin is out of date, a migration is outstanding, or the config no longer validates after an upgrade. Triggers on: "update the stack", "upgrade the stack", "update everything", "am I on the latest", "update my plugins", "run outstanding migrations", "the config stopped validating", "the stack config is still in .github".
Plugin manifests1
{
"name": "devbook-config",
"version": "1.0.0",
"description": "Owns a repository's .devbook/config.json and explains the stack that reads it. `setup` writes the engine-owned keys — bindings, extensions, policy, gates — before anything is installed, then hands every component its own install skill; `update` moves the whole configured stack forward in one run, fanning out to every adopted component’s own install skill and skipping what this machine has not installed or this checkout has not enabled, migrations included; `guide` answers a question about this marketplace from what is on disk — what devbook, the delivery engine, the bridges, the surfaces, and the fan-out lane are and how they fit, which version of each plugin is installed against the newest published, and which are enabled; `adoption` reports where the .ai adoption record no longer matches what is installed and hands the write to flow-ai. All four are backed by a read-only report that names the file behind every fact. Declares no dependency, devbook included: it is named for the folder it writes into, not for a plugin it needs, and one it names but cannot find is reported as not installed.",
"author": {
"name": "Job Schepers"
},
"license": "MIT",
"keywords": [
"config",
"setup",
"marketplace",
"plugins",
"versions",
"devbook",
"delivery",
"onboarding",
"upgrade",
"guide"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[devbook-config on Agent Plugins Marketplace](https://pluginsmp.com/plugins/devbook-config)