maksit-gitea-cursor/skills/gitea-repository/SKILL.md

name	description
gitea-repository	Manage Gitea repositories on a self-hosted instance — search, create, fork, files, branches, collaborators, and webhooks. Use when the user mentions Gitea or a custom Gitea URL, or asks to work with repos on their Gitea server.

Gitea repositories

Work against the configured Gitea instance (GITEA_URL), never github.com unless the user asks.

First step

Call gitea_whoami if the instance or user is unknown.

Common tools

• gitea_repo — search, list, get, create, fork, edit, delete, topics, collaborators, hooks
• gitea_contents — read/write files via the Contents API
• gitea_git — branches, tags, commits, compare
• gitea_catalog + gitea_call — any other repository operationId (admin/secret ops stay blocked unless flags are on)

Conventions

• Identity is owner/repo (user or org).
• Pagination: page and limit. Gitea often caps limit at 50.
• File writes (create/update/delete) need content (base64) and a commit message. Updates/deletes need the current file sha.
• Prefer a new branch + pull request over committing to the default branch unless the user asks otherwise.

Examples

User: "list my repos" → gitea_repo action list_mine

User: "show README of org/app" → gitea_contents action get, filepath README.md