Contributing

Particularly welcome:

• New skill packs that ship opt-in through configure-skills
• New MCP tools that fit the read-mostly, key-gated model
• Linux and Windows hardening, with install notes
• Documentation improvements and more use-case examples
• Translations and regional compliance hints
• New hosts: see what a host needs

Open an issue first for architectural changes. Kevin's contract with the markdown home is intentional and worth preserving.

The dev loop

Fork the repo, clone your fork, and register it as a local marketplace on your host: the Developers tab of Install walks through it, along with branching, opening a pull request to upstream, and keeping your fork current. Then, from the fork:

cd ~/Developer/agent-kevin/mcp-server
bun src/server.ts        # boot check: the banner reports the tool count
bun run typecheck && bun test

Skill-body edits go live on the next session; new skills or hooks need a full relaunch.

Adding a skill: skills/<name>/SKILL.md with frontmatter; grant its MCP tools in the init skill's permission list; use mktemp for scratch files, since $TMPDIR is per-user, not per-session.

Adding an MCP tool: defineTool in mcp-server/src/tools/, register it in the module list, add its mcp__plugin_agent-kevin_kevin__<tool> permission.

PR conventions: focused changes, update docs when counts change, no unjustified dependencies, typecheck passes. Full detail in CONTRIBUTING.md.

License

Apache 2.0. agent-kevin is © AgentLayer. Third-party skill libraries installed through configure-skills are not bundled; each carries its own license, so review the terms before relying on one commercially.