Delva OS — Security skill for Claude Code

Delva OS

A marketplace of skills. The core one builds you an AI operating system: a `CLAUDE.md` your agent reads first every session, a real knowledge directory behind it, and a voice file so anything written as you actually sounds like you. The rest do specific jobs, one plugin each.

Install

Add the marketplace once:

/plugin marketplace add Delva-app/delva-os

Then install the core, plus whichever job skills you're set up with:

/plugin install delva-os@delva-os                    # the core — everyone gets this
/plugin install proposal-from-transcript@delva-os
/plugin install build-prototype@delva-os
/plugin install meta-campaign-builder@delva-os

Restart Claude Code, or run `/plugin` to confirm they're enabled. Skills work in every project once installed.

To pick up later updates: `/plugin marketplace update delva-os`. Each plugin updates on its own, so a new version of one skill never disturbs the others.

If you'd rather not use the plugin system, copy the skill folders under `plugins/*/skills/` into `.claude/skills/` in your project. Same result, but per project and without updates.

Structure

One plugin per skill, one marketplace for all of them.

plugins/
  delva-os/                    # the core three — build-my-os, build-my-voice, os-audit
  proposal-from-transcript/
  build-prototype/
  meta-campaign-builder/

The core plugin is fixed and shared by everyone. Everything else is installed per person, so you only carry what you actually use and you only update what you actually want to change.

Adding a skill means adding a directory under `plugins/` (with a `.claude-plugin/plugin.json` and `skills//SKILL.md`) and one entry in `.claude-plugin/marketplace.json`. Nobody's existing install changes until they install it.

Customizing

Plugin files are replaced wholesale on every update — edits made inside an installed plugin are lost. Two ways to keep a change:

• Your inputs (brand, pricing, templates) live in