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
| Skill | Purpose |
|---|---|
sneat | Operate contacts, lists, calendar and spaces via sneat-cli; interpret natural language through the conversational runtime (sneat convo). |
| WB skill set | Use every public WB command through compact skills, then compose safe code changes and dependency campaigns with minimal duplicate CI. Canonical source lives in sneat-dev/wb; this repository only indexes it. |
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, pathskills/sneat - WB:
sneat-dev/wb, Codex plugin manifest at.codex-plugin/plugin.json, canonical skills atai/skills
Claude-specific marketplace and plugin manifests are distribution metadata; they do not contain a second copy of any skill.
Design notes
- Skills follow the same layout as SpecStudio skills:
skills/<name>/SKILL.mdwith 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.