gitea

What This Skill Does

The Gitea skill provides a powerful interface for interacting with Gitea instances directly from your OpenClaw environment using the official tea CLI. This skill serves as a bridge, allowing your AI agent to manage development workflows, query repository data, and interact with CI/CD pipelines without ever leaving the terminal environment. Whether you need to list pull requests, audit issues, or inspect action secrets and variables, this skill provides structured access to these remote resources.

Installation

To integrate this skill into your environment, execute the following command within your terminal:

clawhub install openclaw/skills/skills/razzeee/gitea-2

Ensure that the tea CLI binary is installed and accessible in your system PATH. After installation, you must configure your instance credentials using the tea login add command to link your specific Gitea server URL and authentication token.

Use Cases

This skill is designed for software engineers and DevOps professionals who want to automate their git-centric workflows. Use it to:

• Automate triage: Quickly list and summarize open issues or PRs for a specific repository.
• CI/CD Management: Retrieve repository secrets or environment variables for troubleshooting build pipelines.
• Data Aggregation: Perform complex API queries against your Gitea instance to extract specific metadata about PR states, reviewers, or labels.
• Multi-instance support: Switch between personal Gitea accounts or internal company instances seamlessly using the --login flag.

Example Prompts

1. "Check the current status of PR #55 in the openclaw/skills repository and tell me who the author is."
2. "List all open issues for the project located at my-org/my-project using my work login."
3. "Can you fetch the list of CI secrets available for the repository owner/repo?"

Tips & Limitations

• Dependencies: Ensure jq is installed on your system if you intend to filter the JSON output from tea api commands.
• Permissions: The AI agent's capability is limited by the scope of the token provided during tea login. Ensure your token has the necessary permissions (read/write) for the actions you wish to perform.
• Security: Treat your login tokens with care. Do not expose them in logs or prompts. For complex queries, prefer tea api over standard subcommands to get granular control over the data returned.