I mentioned in the Red Sensei thread that @hiiamboris had made a Claude "Skill file", giving guidance on the API endpoints and throttling. Basically teaching an AI how to collaborate with its "coworkers", e.g.:
# Red/Sensei Search Skill
Search Red knowledge base.
## Endpoint
```
POST https://ask.lang.red/search
GET https://ask.lang.red/search?query=<question>
```
`query` mandatory. Never call `/search` bare.
## Request
| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| `query` | string | yes | — | Question text |
| `type` | string | no | `combined` | `semantic`, `fulltext`, `combined` |
| `scopes` | string[] | no | all | `docs`, `design`, `code`, `discussions`, `issues` |
| `count` | integer | no | 10 | 1-50 |
### GET example
```
GET https://ask.lang.red/search?query=how+to+define+a+function+in+Red&type=combined&scopes=docs,code&count=10
```
Encode spaces as `+`.
I'm curious as to how much better or worse this would make your experience.
The guidance on how to deal with "budgeting" (in this case, API throttling) are particularly poignant.
We're glimpsing a future, where accounting moves from something that's a department up way at the top of a software organization... to something that is intimately woven into programming itself.
