wednesday docs
Docs/Guides

Skills & MCP servers

Wednesday’s structure is the point, so the operator’s own playbooks and the operator’s own tools belong in it.

Your own skills#

A skill is a folder with a SKILL.md in it: YAML frontmatter with a name and a description, then the instruction a seat receives. Drop the folder in and Wednesday finds it on the next request.

skill homes
~/.wednesday/skills/             # your own skills (all projects)
<project>/.wednesday/skills/     # the project's skills (travel with the repo)

A project skill beats an operator skill with the same name. The directory name is the key; the frontmatter name is free to be prettier.

SKILL.md
---
name: cart-tests
description: How this project verifies the cart and checkout flow
---

Run the cart test group before claiming a change is done:
  npm test -- --runInBand cart

Never edit the fixtures under test/fixtures; they are recorded
from the real checkout service.

Installed packages and the audit#

A .skill file is a zip holding one skill directory. It installs through the same path, and a package that tries to write outside its own folder is refused.

Every installed package goes through the same audit Wednesday uses for a skill it did not write. An instruction-override directive or a hidden instruction refuses the install and names what it found.

run the audit directly
npx tsx factory/verification/skill-audit.ts <skill-dir>
# exits 1 on FAIL

A PASS means no matching malicious shape was found. Descriptive prose that shares attack vocabulary can trip a rule; flags route to human review, never to a silent pass.

MCP servers you attach#

Wednesday can also act as an MCP client. Attached servers are listed in ~/.wednesday/state/mcp.json. Their tools ride a request as mcp__<server>__<tool>, and a call runs on the server that owns it.

~/.wednesday/state/mcp.json
{
  "servers": [
    {
      "name": "github",
      "transport": "stdio",
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "enabled": true
    },
    {
      "name": "remote",
      "transport": "http",
      "url": "https://example.com/mcp",
      "headers": { "Authorization": "Bearer <token>" },
      "enabled": true
    }
  ]
}

A server may speak stdio or Streamable HTTP. A model that is not known to do native tool calls is never offered any attached tool.

Secrets in attached servers#

A server’s env and headers can hold a token. The values are stored on your machine — that is the operator’s own file — but they are never printed. Status shows the key names, not the values, and the redaction pass runs over every receipt as a second line of defence.