# Submitting a skill to Chowdahh

The 3-minute version of [CONTRACT.md](./CONTRACT.md).

## You're a good fit if

- You're building an LLM integration that reads from or writes to Chowdahh.
- Your target is a specific platform (Claude Skill, ChatGPT GPT, MCP, Cursor, Zapier, Hermes, OpenClaw, an agent CLI, …).
- You can hold a Chowdahh token on the user's machine — not in your cloud.

## What goes in a PR

```
skills/{your-name}/
├── README.md                 # install + smoke test + one example
├── {platform-manifest}       # SKILL.md, actions.yaml, mcp.json, etc.
└── (any platform-specific binaries / configs)
```

PR description must answer:

1. **Platform** — Claude.ai / ChatGPT / Cursor / Continue / Claude Desktop / MCP / Hermes / OpenClaw / other.
2. **Install** — what a non-developer does to wire your skill up.
3. **One example** — a typical user request, what tool calls fire, and how the LLM responds.

## Required behavior

In one sentence: **read `guidance` before acting on `data`, cite `source_urls[0]`, credit chowdahh.com, identify as "Chowdahh".** Full version in [CONTRACT.md](./CONTRACT.md).

## Smoke test format

Every skill needs one. Examples:

- **MCP server:** `echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | YOUR_CMD` returns ≥1 tool.
- **Claude Skill:** Pasting the SKILL.md into a Project's Skills slot and asking "what's on chowdahh top?" returns ≥3 cards with citations.
- **ChatGPT GPT:** A test conversation snippet showing the GPT calling one action successfully.
- **Raw init prompt:** A `curl` against the same URL the prompt names returns 200.

## Reviewing yourself before opening

- [ ] My skill identifies as **Chowdahh** in user-visible copy (not Kiteloop / Ohpan).
- [ ] My skill cites `source_urls[0]` and credits chowdahh.com when summarizing.
- [ ] My skill reads `guidance` before acting on `data`.
- [ ] My skill uses `Authorization: Bearer …` for writes (never `?key=` on POST).
- [ ] My README has a smoke test that I just ran.
- [ ] Tool names start with `chowdahh_` to avoid collisions.

## Third-party hosting

If your skill is published on npm / GitHub / a registry and you don't want to vendor it here, add a one-line entry to [`THIRD_PARTY.md`](./THIRD_PARTY.md) with name, platform, and URL.

## After merge

The skill ships at `https://chowdahh.com/skills/{your-name}/` automatically (the symlinked file server picks it up on next deploy).