Skip to main content

Author and Publish a Card

Cards let you package reusable harness intent, skills, MCP definitions, and metadata as a versioned unit. The authoring flow has three states:

  • source: editable files under ~/.agents/drwn/sources/<scope>/<name>/
  • published card: immutable Git-backed releases under ~/.agents/drwn/cards
  • consumed card: a project ref in .agents/drwn/config.json plus a locked resolution in .agents/drwn/card.lock

Create a source:

drwn card new @me/backend --no-git
drwn card source show @me/backend
drwn card source doctor @me/backend

Add local content before publishing:

drwn card source add-skill @me/backend reviewer --from ./skills/reviewer
drwn card source add-mcp @me/backend context7
drwn card source set @me/backend --description "Backend review harness" --version 0.1.0
drwn card source set @me/backend --stability stable --last-validated-with 0.1.0 --test-status-badge https://example.com/status.svg

Publish and inspect the release:

drwn card publish @me/backend
drwn card show @me/backend@0.1.0
drwn card validate @me/backend@0.1.0

Use DRWN_STORE_READONLY=1 when validating a store snapshot. Source inspection and dry runs continue to work, while commands that would mutate source files or publish releases fail before writing.

Agent Workflow Skills​

Use author-harness-card when an agent should drive source authoring, diagnostics, metadata updates, publish, validate, diff, or deprecate flows.

Use share-harness-card after publication when the next step is adding a Git remote, pushing tags, fetching updates, or cloning a shared card.

See Use Darwinian Harness Skills for installation and skill selection.