ano-skills

Ano Skills

Claude Code skills for Ano.

Ano is team chat with Claude Code and agents built in. These skills teach Claude Code how to work with Ano: use the ano CLI, read workspace context, send messages, and understand payloads sent from the Ano desktop app.

Install

claude plugin install @ano-chat/skills

Ano Sync — keep a channel current as you work (automatic)

ano-sync turns a teammate's Ano channel into a live "control tower" for your work. The plugin bundles everything, so it's one install + a one-time allow-list — no manual MCP config, no manual hooks:

• the ano MCP server (ano_send_sync_event + ano_get_channel_context),
• a SessionStart hook that auto-reads the channel's state at task start,
• a Stop hook that, when a turn changed files, has the agent post one rich Sync Event before it stops,
• the ano-sync skill (behavior + anti-spam).

It is opt-in per repo and silent everywhere else.

One-time: allow the tools (so there's never an "Allow?" prompt)

Plugins can't grant tool permissions (by design), so add this once to ~/.claude/settings.json (merge into any existing permissions):

{
  "permissions": {
    "allow": [
      "mcp__ano__ano_send_sync_event",
      "mcp__ano__ano_get_channel_context"
    ]
  }
}

Per repo: turn it on

Add to the repo's CLAUDE.md (this is the on switch — remove it to turn off):

## Ano Sync

- channel: #ano-sync-demo <!-- a name is fine — the agent resolves it to the id -->

(or set ANO_SYNC_CHANNEL to a name or id in your env.) Then just work: the agent auto-reads the channel at task start and auto-posts a Sync Event when a turn changed files — no prompting, no accept clicks. Works wherever Claude Code runs (iTerm2, Cursor's terminal, …).

On / off

• Per repo: add/remove the ## Ano Sync block (or ANO_SYNC_CHANNEL).
• Globally: claude plugin disable ano-skills / claude plugin enable ano-skills.

The bundled ano MCP points at production by default (api-us.ano.dev). To target another environment (e.g. staging for dogfooding), set ANO_MCP_URL before launching Claude Code: export ANO_MCP_URL=https://api-staging.ano.dev/mcp.

What Is Included

Nine focused, self-contained skills. Each loads only when its trigger phrases match — so a "send a message" prompt no longer pulls the full CLI surface into context.

Skill	Domain
ano-core	Foundational rules — auth, output modes, exit codes, rate limits, triggered-auth flow.
ano-messages	Send/read/reply/search messages, DMs, group DMs, file attachments, screenshots.
ano-channels	List/admin channels + workspaces + members, send invites.
ano-coworkers	Create / update / test AI teammates (managed or external-webhook).
ano-notifications	DND quiet hours, notification level, email/desktop/mobile push toggles.
ano-tables	List/query/write Ano tables (structured rows / lists / databases).
ano-automations	Build-Before-Talk methodology, 5 trigger types, 5 action tools, third-party OAuth.
ano-realtime	ano connect SSE bridge, OpenClaw agent forwarding, install-as-service.
ano-payloads	Parse <ano_payload> XML blocks from the Ano desktop's Send-to-Shell gesture.

Trigger ownership rules (for future skill edits)

• Verb-led triggers (send/read/search/post/reply/dm/share) → ano-messages
• Object-led naming channels/workspaces/members/invites → ano-channels
• Object-led naming coworkers/teammates → ano-coworkers
• Object-led naming dnd/notification/push/email → ano-notifications
• Object-led naming tables/rows → ano-tables
• Object-led naming automations/triggers/jobs/webhooks/integrations → ano-automations
• Object-led naming bridge/stream/connect → ano-realtime
• Foundational (use ano / ano version / authenticate / smoke / doctor) → ano-core

Resolve overlap on the more-specific term. "Send a webhook" → ano-automations (webhook = automation noun), not ano-messages.

Adding a new trigger — decision flowchart

Use this when the CLI ships a new command (or a new phrasing surfaces) and you need to decide which skill owns it.

Is the phrase verb-led ("send X", "read Y", "search Z")?
└── yes → does the object name a noun OTHER skills own?
          ├── yes → owner skill (e.g. "send a webhook" → ano-automations)
          └── no  → ano-messages