Gitea

**Verdict:** A powerful and comprehensive Gitea management skill built on the `tea` CLI, suitable for users who already rely on Gitea and are comfortable with command-line workflows. It offers broad coverage of repository, issue/PR, release, CI/CD, and webhook operations. **Strengths** - Uses the established `tea` CLI, exposing most core Gitea features (repos, issues, PRs, releases, actions, webhooks, branches, labels, milestones, orgs). - Good for automation and scripting thanks to explicit repo/instance flags (`--repo`, `--login`) and multiple output formats (simple, csv, yaml). - Mature and somewhat battle-tested (thousands of downloads) for typical Gitea administration and developer workflows. **Risks / Limitations** - High-impact, destructive operations are exposed (e.g., `tea repos delete --force`, managing secrets, altering webhooks); misuse can lead to data loss, misconfiguration, or credential exposure. - Requires `tea` to be installed and configured in the environment; no guarantees outside a properly set up Gitea/CLI context. - CLI-centric workflow assumes some familiarity with Gitea concepts and command-line flags; not ideal for non-technical users. **Recommended Scenarios** - Teams using Gitea as their primary git hosting and CI/CD platform who want to manage issues, PRs, and releases directly from automated agents or scripts. - DevOps/infra engineers needing to programmatically manage repositories, secrets, and webhooks across multiple projects or organizations. - Power users who prefer CLI tools and want fast, scriptable access to Gitea resources, including custom reporting or integrations based on CSV/YAML output. **Use with Caution When** - Granting agents the ability to run repo-deletion, secret-management, or webhook-creation commands; these should be restricted to trusted contexts and ideally guarded by explicit human review. - Operating against production-critical Gitea instances where misconfigured actions or webhooks can impact CI/CD pipelines or external integrations.