CLIO Darshan AGENTS.md changelog

file

published → removed

https://raw.githubusercontent.com/iowarp/clio-kit/HEAD/AGENTS.md

− # Working on CLIO Kit− CLIO Kit is a meta-marketplace for scientific computing. Start with− [setup.md](setup.md) for installation, [docs/README.md](docs/README.md) for− human guides, and [docs/authoring.md](docs/authoring.md) to define a plugin,− MCP server, skill or hook. Detailed contribution rules are in− [CONTRIBUTING.md](CONTRIBUTING.md).− ## Repository map− - `src/clio_kit/`: launcher, runtime isolation, skills and marketplace commands.− - `mcp-servers/<name>/`: independent server packages, descriptors, locks and tests.− - `skills/`: portable skill collections, including adapted Clio Coder skills.− - `plugins/`: workflow packages, shared components and native client adapters.− - `community/entries/`: external plugin and marketplace TOML entries.− - `.clio-kit/catalogue.json`: generated shared package catalogue.− - `.claude-plugin/`: native Claude export and federation snapshot.− - `docs/`: documentation source shared by GitHub and Docusaurus.− - `website/`: website configuration, components and static assets.− ## Choose the contribution route− Use the product distinction consistently: MCPs, skills, agents and hooks are− components; plugins bundle components for a workflow. Native Claude Code wrappers− are installation packages and must not inflate workflow-plugin counts. The− catalogue derives maintained types from contents and dependencies; do not guess− external component types from package names.− For repository-owned component packages, add a named folder under `plugins/`,− `skills/`, `agents/` or `hooks/`, with `.claude-plugin/plugin.json` and the needed− components. Website start/build and CI sync both catalogues automatically;− discovery needs no central TOML entry or manual generator commands. CI syncs the− catalogues before the root suite; do the same locally with− `clio-kit marketplace sync --root .`, which is also what native client testing− before a build needs.− Validate the package, then run `scripts/verify_local_components.py --output`− with a new temporary directory for native installation and usage checks.− For external plugins, run `clio-kit plugin init my-plugin`, edit the generated− components, then `clio-kit plugin validate my-plugin`. Add `--hook` to scaffold− a read-only SessionStart command hook. Follow the authoring guide for MCP− configuration, skill metadata and evaluation scenarios. Generate a community− entry with `clio-kit plugin submit my-plugin --repo owner/name`; `--open-pr`− performs the separate public submission action.− For a maintained server, add it under `mcp-servers/` with its runtime descriptor,− lock file and tests, and register it in `mcp-server-versions.toml`. Python, Node− and Go have different build prerequisites; use the contributor guide's runtime

file

absent → published

https://raw.githubusercontent.com/iowarp/clio-kit/HEAD/AGENTS.md

+ # Working on CLIO Kit+ CLIO Kit is a meta-marketplace for scientific computing. Start with+ [setup.md](setup.md) for installation, [docs/README.md](docs/README.md) for+ human guides, and [docs/authoring.md](docs/authoring.md) to define a plugin,+ MCP server, skill or hook. Detailed contribution rules are in+ [CONTRIBUTING.md](CONTRIBUTING.md).+ ## Repository map+ - `src/clio_kit/`: launcher, runtime isolation, skills and marketplace commands.+ - `mcp-servers/<name>/`: independent server packages, descriptors, locks and tests.+ - `skills/`: portable skill collections, including adapted Clio Coder skills.+ - `plugins/`: workflow packages, shared components and native client adapters.+ - `community/entries/`: external plugin and marketplace TOML entries.+ - `.clio-kit/catalogue.json`: generated shared package catalogue.+ - `.claude-plugin/`: native Claude export and federation snapshot.+ - `docs/`: documentation source shared by GitHub and Docusaurus.+ - `website/`: website configuration, components and static assets.+ ## Choose the contribution route+ Use the product distinction consistently: MCPs, skills, agents and hooks are+ components; plugins bundle components for a workflow. Native Claude Code wrappers+ are installation packages and must not inflate workflow-plugin counts. The+ catalogue derives maintained types from contents and dependencies; do not guess+ external component types from package names.+ For repository-owned component packages, add a named folder under `plugins/`,+ `skills/`, `agents/` or `hooks/`, with `.claude-plugin/plugin.json` and the needed+ components. Website start/build and CI sync both catalogues automatically;+ discovery needs no central TOML entry or manual generator commands. CI syncs the+ catalogues before the root suite; do the same locally with+ `clio-kit marketplace sync --root .`, which is also what native client testing+ before a build needs.+ Validate the package, then run `scripts/verify_local_components.py --output`+ with a new temporary directory for native installation and usage checks.+ For external plugins, run `clio-kit plugin init my-plugin`, edit the generated+ components, then `clio-kit plugin validate my-plugin`. Add `--hook` to scaffold+ a read-only SessionStart command hook. Follow the authoring guide for MCP+ configuration, skill metadata and evaluation scenarios. Generate a community+ entry with `clio-kit plugin submit my-plugin --repo owner/name`; `--open-pr`+ performs the separate public submission action.+ For a maintained server, add it under `mcp-servers/` with its runtime descriptor,+ lock file and tests, and register it in `mcp-server-versions.toml`. Python, Node+ and Go have different build prerequisites; use the contributor guide's runtime