Only what needs you reaches you.

Decide once. Every agent knows.

Skein is the decision layer for teams running coding agents. It settles what your team has already decided, and sends the rest to the one person who should decide, so people only see what actually needs them.

Start a team See it in action

claude code · worker PR 57

working

camelCase or snake_case for the new endpoint?

Per D-0001 snake_case for every field

Retry failed URL fetches in the import job?

waiting on @maya

Per D-0027 Three retries with backoff

What do we return on a rate limit?

Per D-0016 429 with Retry-After

cursor · web PR 90

working

How should the list endpoint paginate?

Per D-0003 Cursor pagination, no offsets

Should the import job retry failed fetches?

Per D-0027 Three retries with backoff

codex · recipes-api PR 215

working

Which status code for a name that fails validation?

Per D-0006 422 with code invalid_request

How do I ship the half-finished sharing feature?

Per D-0008 Behind a flag in flags.ts, default off

Skein

D-0016Rate limit responses
D-0008Feature flags
D-0006Validation errors
D-0027Retries for recipe imports

Inbox zero

For you· just askedD-0020

Retry failed recipe URL fetches, and how often?

Context worker PR 57, importing recipes from links

ANo retries; mark the import failed+Simple−Blips lose imports

BThree retries with backoff Skein leans · precedent+Covers blips−Failures take longer

Why B: backs off like the rate-limit rule. Rests on D-0016.

✓

Recorded as D-0027 · a standing rule

“Three retries with backoff”

Now in the record; it closes D-0020.

The web inbox

One inbox for every open question: what's being asked, why, two or three options with their trade-offs, and a lean.

The Skein web inbox: an agent's open question with its context, two or three options with their trade-offs, and Skein's lean, ready to answer in one click.

The same question, as a DM

Skein sends it to the API's owner, not the whole channel, with the options, the agent's context and a lean.

Skein

Skein needs a decision on D-0020: Retry failed recipe URL fetches, and how often? Waiting: an agent working in worker PR 57, importing recipes from links. Why: The agent is adding import-from-link in PR 57 and found no retry rule. A. No retries; mark the import failed. Pro: Simple. Con: Blips lose imports. B. Three retries with backoff. Pro: Covers blips. Con: Failures take longer. Lean: B, from precedent D-0016: backs off like the rate-limit rule. Looks like a standing rule: applies to every import. Reply 'just now' with your answer if it isn't. Reply A, B, or in your own words. Related: D-0016 Rate limit responses

maya

Skein

Recorded as D-0027, answering D-0020 (Should the recipe import job retry failed URL fetches, and how many times?): 'Three retries with backoff' (option B). Reply no in this message's thread if that's not what you meant.

The record

Your record is plain Markdown: every decision, who made it, why, and what it replaced.

The team's record in the web inbox: each decision with who made it and why, the newest replacing an earlier one.

Principles

Your team writes the rules: what Skein may settle alone, who owns what, and the principles behind your calls.

Running in five minutes

Sign in with GitHub and name your team. Skein runs your team's server and keeps your record.
Connect your agents. Paste one line into your repo's .mcp.json.
Invite your team. Questions that need a person show up in the web inbox.

{
  "mcpServers": {
    "skein": {
      "type": "http",
      "url": "https://your-team.skeinai.ca/mcp",
      "headers": {
        "Authorization": "Bearer ${SKEIN_SECRET}"
      }
    }
  }
}

Yours, not ours

Your record

Export or delete it any time, or keep it in your own private repo instead of ours.

Your rules

Skein never changes them without asking.

Your agents

Your agents run on your accounts. Skein never holds your Claude login and never runs your agents. It answers their questions.

Works with what you run

Claude Code, Cursor, Codex, or any agent that speaks MCP. Keep the orchestrator or harness you already use; Skein plugs into it. A blocked agent calls one tool, ask_skein, and gets back an answer with a citation, or the answer of the person who owns the question.