naudachu
f18a633185
The plugin required `tea`, Gitea's own CLI, for everything that is not an issue: releases, pull requests, milestones, branches, actions, webhooks. That put a second binary, a second set of logins nothing here could see, and 400 lines documenting somebody else's flags outside anything this repository can test. One command over the transport that already existed removes all three. Transport: `post` — the hand-rolled request the SDK cannot express, written for the dependency endpoint — is generalized to an exported `Do`, and `post` is three lines on top of it. Same http.Client, so the same RoundTripper files the body under .kettle/payload/, the same `token …` header authenticates it, and a non-2xx is the same *APIError. It does not paginate, does not reformat the answer, and names no domain concept, so the layering test is untouched. The endpoint rule is `tea api`'s, so an endpoint table written for that tool still works — with one restriction it did not have: a full URL must be on this instance. Every request carries the project's token in a header, and a URL on another host would hand the token to whatever was typed. Command: `kettle api <endpoint>` in a new `api` group, so the generator writes plugins/kettle/skills/api/SKILL.md — group, directory and /kettle:api are one word. No --repo and no --login, for the reason no sync command has them: a cross-repository address is an address, and another instance is KETTLE_URL. `-X DELETE` needs `--yes`; a flag typed on purpose is an operator's decision. Scopes: a token minted for issues carries write:issue and answers 403 on the first request outside issues, naming no scope. Gitea cannot be asked what a token may do — its own token listing needs a password — so `auth add --scopes` records it, `auth list` and `config` show it, and a 403 says which category it is likely to be. Documentation only; nothing is checked against it. skills/use — the tea reference, 239 lines of it — becomes skills/api: what to ask for, which endpoints paginate, and how to write a body. Every mention of `tea` as a requirement is gone from the manifests, the READMEs, the runner and the four other skills; what survives is the back-compat with the old plugin, which is a decision and not a debt. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
5.9 KiB
name, description
| name | description |
|---|---|
| auth | Give `kettle` a Gitea credential and choose which login this project runs under — `kettle auth list/add/remove` manages the machine-wide token file, `kettle init --login <name>` pins one of those names into `.kettle/config.yaml`. Load when a sync command reports no login, a 401, or an unknown login name, or when the user asks to switch the account this project's issues are pushed under. The OPERATOR picks the login; you never type a token. |
/kettle:auth — the credential a project runs under
Two files, and the split is the whole design.
| where | what is in it | who writes it |
|---|---|---|
~/.config/kettle/logins.yaml |
the tokens, one file per machine, mode 0600, outside every working tree | kettle auth add |
<project>/.kettle/config.yaml |
the name of one of those logins, and the tracker repo | kettle init --login … --repo … |
A name is worth nothing on its own, which is what makes it safe to keep in a
file inside a repository. A token in a working tree ends up in a commit
eventually, and a secret that has ever been pushed has to be rotated.
$KETTLE_CONFIG_HOME or $XDG_CONFIG_HOME move the machine file;
KETTLE_LOGIN, KETTLE_URL and KETTLE_TOKEN override it outright, which is
how CI runs with no token on disk.
There is no login pinned in .claude/settings.local.json any more, and no hook
that rewrites a --login argument. That mechanism is gone with the Python
scripts; nothing here reads Claude's settings. If you find a GITEA_LOGIN in a
settings file, it is dead weight from the old plugin.
The one hard rule: the operator chooses, and holds the token
- Never pick a login. Not from memory, not from the repo URL, not from a
previous session. Present the choice with
AskUserQuestion— name, url and user out ofkettle auth list— and let the operator answer. Exactly one login on the machine is the only case where you may propose, and you still confirm. - Never type, echo, paste or read a token.
kettle auth addtakes it on stdin precisely so it does not land in shell history; a token that goes through a model's context is a token in a transcript. Adding a login is the operator's own terminal, not a Bash call you make for them.
Steps
-
See what this machine holds. It never prints a token, and there is no flag to make it:
kettle auth list -
Nothing there — stop and hand the operator the command to run themselves:
kettle auth add --name noodles --url https://git.example.com --user naudachu < token.txt pass show gitea/token | kettle auth add --name noodles --url https://git.example.com--useris documentation only.kettle auth remove <name>forgets one. -
Pin the choice into the project. Ask
kettle configfirst and only proceed if it answers with a project —kettle initin a directory that is not one would create a project there, which is the one statement that is never yours to make (/kettle:init):kettle config kettle init --login noodlesiniton an initialized project printsalready initialized — nothing to doand rewrites only the settings it was given, so the repo pinned earlier stays. -
Confirm with
kettle config. Tell the operator which login is pinned and which file it went in. It is live immediately — nothing caches it, no restart.
login noodles
url https://git.example.com
token (set)
repo claude-skills/marketplace
When it goes wrong
| what you see | what it means |
|---|---|
no login "X" in …/logins.yaml — known: … |
the project pins a name this machine does not hold. Either add it (step 2) or pin one that is there |
no .kettle/ found — searched up from … |
not a project. /kettle:init, and it is the operator's to run |
401 / 403 from a sync command |
report it verbatim. Do not try another login, and do not edit or remove one to route around it — that is somebody's identity, not a setting |
token none in kettle config |
a name is pinned but no credential answers to it |
Scopes: what the token is allowed to do
Gitea mints a token with scopes, spelled <read|write>:<category>. A token made
for issues carries write:issue — and that is enough for everything
/kettle:issue and /kettle:sync do, and not enough for anything
/kettle:api reaches: releases, pull requests, branches, tags and actions all
sit under repository.
| doing | needs |
|---|---|
| pull, push, comment, close, evict | write:issue |
kettle labels |
write:issue |
kettle api on releases, PRs, tags, branches, actions |
write:repository too |
| reading any of those without writing | the read: half is enough |
kettle auth add --scopes write:issue,write:repository writes that down beside
the login. It is a note and nothing else — nothing is checked against it and
nothing is refused because of it. It is worth writing down because the instance
will not answer the question: Gitea's own token listing needs a password rather
than a token, so a token cannot be asked what it may do. kettle auth list and
kettle config show what was recorded; (not recorded) means nobody wrote it
down, never "none".
A 403 from a sync command or from kettle api is usually this and says so.
Minting a new token is the operator's job in the web UI — the same flow as step
2 above, with both scopes ticked this time. Never remove or re-point a login to
route around a 403.
No kettle on PATH? command not found: kettle is the whole story. Stop and
tell the operator to install it: cd cli && go build -o ~/.local/bin/kettle ./cmd/kettle in the marketplace repository (go.mod requires go 1.26), or
go install git.noodles.cam/claude-skills/marketplace/cli/cmd/kettle@latest.
The full flag table for auth, config and init is the generated block in
/kettle:project.