sneat-ai

AI skills for Sneat.app.

These skills are thin integrations that expose Sneat capabilities to external AI agents (Claude Code, future ChatGPT integrations, coding and reasoning agents) by invoking sneat-cli. They contain no business logic — everything goes through the CLI into the Typed Sneat Actions and application facades:

Claude Code / AI Agent
        │
        ▼
  Sneat AI Skill        (this repo — skills/<name>/SKILL.md)
        │
        ▼
    sneat-cli
        │
        ▼
Typed Sneat Actions     (conversational runtime action specification)
        │
        ▼
Application Facades
        │
        ▼
  DALgo Datastore

Skills

Installation (Claude Code)

Add the Sneat AI marketplace once, then install either plugin:

/plugin marketplace add sneat-co/sneat-ai
/plugin install sneat@sneat-ai
/plugin install wb@sneat-ai

Claude namespaces the skills as /sneat:sneat, /wb:wb-worktrees, /wb:wb-deps, and so on. Git-backed versions intentionally follow repository commits, so users receive updates without duplicated version metadata.

For local development, validate the marketplace and its local sneat plugin:

claude plugin validate .

The sneat plugin requires the sneat CLI on PATH (go build ./cmd/sneat in sneat-cli). The wb plugin requires a current wb CLI on PATH.

Installation (Codex and Agent Skills clients)

Both published skills use the portable Agent Skills SKILL.md format. Codex and other compatible clients can install the canonical source directly:

• Sneat: sneat-co/sneat-ai, path skills/sneat
• WB: sneat-dev/wb, Codex plugin manifest at .codex-plugin/plugin.json, canonical skills at ai/skills

Claude-specific marketplace and plugin manifests are distribution metadata; they do not contain a second copy of any skill.

Repository scope rule

This repository is skills only. It MUST NOT contain CLI, backend or frontend code. What lives here:

• skills/<name>/SKILL.md and their reference files (prompts, examples, schemas rendered for the model);
• plugin/marketplace manifests (.claude-plugin/) — distribution metadata;
• small agent-harness scripts strictly needed to install or validate the skills (e.g. a claude plugin validate helper).

Everything else has a home elsewhere:

A skill that needs a capability the CLI does not have reports the gap; it never re-implements it here.

Design notes

• Skills follow the same layout as SpecStudio skills: skills/<name>/SKILL.md with YAML frontmatter (name, description).
• Skills must stay thin: reuse the Typed Action Specification (sneat convo actions --json), the CLI, and the application facades.
• Future skills (candidates, not commitments): per-extension skills (sneat-lists, sneat-calendar) scoped like extension-specific bots; an MCP server generated from the same action specification.

{
  "name": "sneat-ai",
  "description": "Agent skills published by Sneat and Sneat Developer Platform projects",
  "owner": {
    "name": "Sneat.co"
  },
  "plugins": [
    {
      "name": "sneat",
      "source": "./",
      "description": "Operate Sneat.app through the sneat CLI"
    },
    {
      "name": "wb",
      "source": {
        "source": "github",
        "repo": "sneat-dev/wb"
      },
      "description": "Operate repository fleets through compact WB command and workflow skills"
    }
  ]
}