Official skills

Splice ships a small set of official skills in the @splice namespace. Each one demonstrates a different kind of capability and a different permission profile. Sources: skills/<name>/.

The last three use the capability broker: they hold no keys and open no sockets; the host answers with real provider data.

Not included: @splice/process. See permissions.md.

Tool names use hyphens (get-repo), because tool names follow the manifest rule ^[a-z][a-z0-9-]{0,63}$. The MCP names are splice_<package>_<tool>, e.g. splice_github_get-repo.

Install

splice add @splice/json                               # no permissions: no consent needed
splice info @splice/http                              # review the permissions first
splice add @splice/http --accept-permissions
splice add @splice/files --accept-permissions
splice add @splice/github --accept-permissions

SDK:

import { Splice } from "@spliceloom/sdk";
const splice = new Splice({ project: "./agent" });
await splice.init();
await splice.add("@splice/json");
await splice.add("@splice/http", { acceptPermissions: true });   // after showing them to a human

Discover tools

Tool descriptors come straight from each package's manifest.json (no hand-written schemas):

const tools = await splice.tools("@splice/json");      // or splice.tools() for everything
// [{ name: "json.parse", qualifiedName: "@splice/json.parse", mcpName: "splice_json_parse",
//    inputSchema, outputSchema, permissions, annotations, timeoutMs, ... }, ...]

MCP clients see the same tools through splice mcp (stdio) or splice mcp --http; see MCP discovery.

Run tools

splice run json.parse text='{"hello":"world"}'
splice run http.get url=https://api.github.com/repos/spliceloom/splice-artifacts
splice run files.write path=notes/a.md content="# A"
splice run github.search-repositories query="mcp language:typescript" sort=stars

const result = await splice.run("@splice/json.parse", { text: '{"hello":"world"}' });
// { ok: true, output: { value: { hello: "world" }, type: "object" }, ... }

const skill = await splice.load("@splice/json");
await skill.run("pick", { value: result.output.value, paths: ["hello"] });

Tool failures never throw: they return { ok: false, error: { code, message } }. Runtime codes (INVALID_INPUT, PERMISSION_DENIED, TIMEOUT, …) come from the sandbox; skill-specific errors are TOOL_ERROR with a message that starts with the skill's own code, e.g. INVALID_JSON: at position 6 (line 1, column 7): … or PATH_OUTSIDE_SANDBOX: …. Each SKILL.md lists its codes.

MCP discovery

For every installed tool, tools/list returns:

Each package's SKILL.md is an MCP resource (splice://packages/@splice/json/SKILL.md). Tool errors — invalid input, permission denials, skill errors — are isError: true results with the code at the start of the text.

Package layout

Every official package uses the normal package format (spec.md) plus two folders:

skills/http/
  manifest.json      # identity, runtime.minNodeVersion, permissions, tools with input/output schemas
  SKILL.md           # when to use it, tools, errors, limits, security boundaries
  tools/*.ts         # one entry per tool (default export)
  lib/*.ts           # shared code imported by tools
  examples/*.json    # { tool, input, output? } — validated against the schemas by the tests
  tests/*.test.ts    # self-contained unit tests (node --test tests/*.test.ts)

examples/ and tests/ are published inside the artifact, so anyone can inspect and run them. The Splice repository additionally runs every official package in the real sandbox, through the SDK, through MCP and through a local registry (packages/cli/src/official-skills.test.ts).

Versions

0.1.1 of @splice/json (nesting limit) and @splice/files (Windows path rules, hard links, descriptor re-check) are Phase 8 security fixes; @splice/http and @splice/github stay at 0.1.0 because their protections are enforced by the runtime. See security.md.

Official packages start at 0.1.0 and follow semver. Published versions are immutable; a fix is a new version (0.1.1), picked up by splice update within the project's range (lifecycle.md).