gitea-api
Skill4 starsChanged 5 months agoMITView on GitHub
Use when working with the Gitea REST API — authentication, token management, repository/issue/PR CRUD, package management, admin operations, and general API automation with curl.
- Sends data out
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ferocknew/claude_code_public_skillstheir own version, first seen Jul 26, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ferocknew/claude_code_public_skills★ 9same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository74 other files it gives its agents.
- AGENTS.mdAGENTS.md
- atlasSkill
- cert-managerSkill
- cilium-gatewaySkill
- cilium-networkSkill
- cnpgSkill
- dragonflySkill
- external-dnsSkill
- external-secretsSkill
- flaggerSkill
- fluxSkill
- gitea-registrySkill
- gitea-runnerSkill
- giteaSkill
- gitea-teaSkill
- gitea-webhooksSkill
- harbor-apiSkill
- harbor-helmSkill
- harborSkill
- harbor-terraformSkill
- helm-chartSkill
- helm-opsSkill
- helmSkill
- higress-helmSkill
- higress-operatorSkill
- higressSkill
- kserve-helmSkill
- kserve-operatorSkill
- kserveSkill
- kubeflow-pipelinesSkill
- kubeflowSkill
- kubeflow-trainerSkill
- kubeflow-training-operatorSkill
- mariadb-helmSkill
- mariadb-operatorSkill
- mariadbSkill
- netbird-cliSkill
- netbird-operatorSkill
- netbird-serverSkill
- netbirdSkill
- netbird-terraformSkill
- nextcloud-apiSkill
- nextcloud-helmSkill
- nextcloudSkill
- nvidia-device-pluginSkill
- rook-ceph-operatorSkill
- rook-cephSkill
- rook-ceph-toolboxSkill
- sealed-secretsSkill
- stakater-reloaderSkill
- tailscaleSkill
- tailscale-talosSkill
- talosconfigSkill
- talosctlSkill
- talosSkill
- talos-terraformSkill
- tekton-operatorSkill
- tekton-pacSkill
- tekton-pipelinesSkill
- tektonSkill
- The first 60 shown.
The file
Files
Gitea REST API (v1.26)
Base: https://gitea.example.com/api/v1. Swagger: https://gitea.example.com/api/swagger. OpenAPI spec: https://gitea.example.com/swagger.v1.json.
Authentication
| Method | Header / Param | Use Case |
| Token | Authorization: token <token> | API tokens from Settings > Applications |
| Basic Auth | -u username:password | Creating tokens (POST /users/:name/tokens) |
| OAuth2 Bearer | Authorization: bearer <token> | OAuth2 access tokens |
| URL param | ?token=<token> | Simple scripts |
| SSH signatures | Signature header with SSH key | mTLS-style auth via SSH |
2FA: add header X-Gitea-OTP: 123456 with Basic Auth.
Token Scopes
"scopes": ["all"] or fine-grained: ["repo", "write:repository", "read:user", "read:organization"]. Create via UI or POST /api/v1/users/{username}/tokens.
Key Endpoints
Users & Auth
| Method | Endpoint | Purpose |
| GET | /user | Current user info |
| GET | /users/{username} | Get user |
| POST | /users/{username}/tokens | Create API token (Basic Auth required) |
Repositories
| Method | Endpoint | Purpose |
| GET | /repos/{owner}/{repo} | Get repository |
| POST | /repos/{owner}/{repo} | Create repository |
| POST | /repos/{owner}/{repo}/mirrors | Sync mirror |
Issues & Pull Requests
| Method | Endpoint | Purpose |
| POST | /repos/{owner}/{repo}/issues | Create issue |
| GET | /repos/{owner}/{repo}/issues | List issues (filters: state, labels, created_by) |
| POST | /repos/{owner}/{repo}/pulls | Create pull request |
| GET | /repos/{owner}/{repo}/pulls | List PRs |
Organizations
| Method | Endpoint | Purpose |
| GET | /orgs/{org} | Get organization |
| POST | /orgs/{org}/teams | Create team |
Admin
| Method | Endpoint | Purpose |
| GET | /admin/users | List users (supports sorting/filtering) |
| POST | /admin/users | Create user |
| POST | /admin/hooks | Create system/default webhook |
| GET | /admin/hooks?type=system|default | List admin webhooks |
Packages
| Method | Endpoint | Purpose |
| GET | /packages/{owner} | List packages |
| DELETE | /packages/{owner}/{type}/{name}/{version} | Delete package version |
Examples
# Create an issue
curl -X POST https://git.example.com/api/v1/repos/myorg/myrepo/issues \
-H "Authorization: token <token>" \
-H "Content-Type: application/json" \
-d '{"title": "Bug", "body": "Description", "labels": [1, 2]}'
# List PRs with filters
curl "https://git.example.com/api/v1/repos/myorg/myrepo/pulls?state=open&sort=recentupdate" \
-H "Authorization: token <token>"
# Create API token (Basic Auth required)
curl -X POST https://git.example.com/api/v1/users/myuser/tokens \
-u myuser:mypassword \
-H "Content-Type: application/json" \
-d '{"name": "ci-token", "scopes": ["repo", "write:repository"]}'
# Delete a package version
curl -X DELETE "https://git.example.com/api/v1/packages/myorg/container/myapp/1.0.0" \
-H "Authorization: token <token>"Common Mistakes
- 2FA users — must pass
X-Gitea-OTPheader with Basic Auth when creating tokens - Token as query param —
?token=...works but logs expose it. Prefer header. - Package delete needs all segments — owner, type, name, version. Missing one = 404.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

