← Back to Skills Marketplace
427
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install gitea-workflow-dispatch
Description
Trigger Gitea/Forgejo workflow_dispatch via API.
README (SKILL.md)
Gitea Workflow Dispatch
Trigger Gitea/Forgejo workflow_dispatch via API.
Environment Variables
GITEA_URL- Gitea API URL (e.g.,http://8.137.50.76:10000)GITEA_TOKEN- Gitea API token
Usage
node -e "
const dispatch = require('~/.openclaw/skills/gitea-workflow-dispatch/index.js');
dispatch({
owner: 'gg',
repo: 'web3-mini-game',
workflow: 'deploy-vercel.yml',
ref: 'master'
}).then(r => console.log(r.status, r.ok)).catch(console.error);
"
Inputs
| Field | Type | Required | Description |
|---|---|---|---|
| owner | string | ✅ | Repository owner |
| repo | string | ✅ | Repository name |
| workflow | string | ✅ | Workflow file name |
| ref | string | ❌ | Git ref (default: master) |
| inputs | object | ❌ | Workflow inputs |
| dryRun | boolean | ❌ | Test without sending |
Usage Guidance
This skill appears to do what it says (trigger a Gitea/Forgejo workflow) and only needs GITEA_URL and GITEA_TOKEN. However, index.js uses spawn('curl', ...) even though the metadata and SKILL.md only list 'node' as a required binary — you should not install or use the skill until that mismatch is resolved. Actionable precautions:
- Ensure the runtime has curl installed and available on PATH, or update the skill to use a Node HTTP library instead of spawning curl.
- Be aware the skill will send your GITEA_TOKEN to whatever GITEA_URL you configure; only use tokens with the minimal required scope and point GITEA_URL at a trusted server.
- Test first with dryRun: true to inspect the request object without transmitting the token.
- Note that the spawned curl process inherits the agent's environment; avoid running the skill in contexts where other sensitive env vars might be present, or sandbox it.
If you do not control or trust the skill source, prefer reviewing or replacing the implementation (e.g., using native Node HTTP calls) before providing a real GITEA_TOKEN.
Capability Analysis
Type: OpenClaw Skill
Name: gitea-workflow-dispatch
Version: 0.1.2
The skill is designed to trigger Gitea/Forgejo workflow_dispatch via API, which is a legitimate automation task. It uses `node:child_process.spawn` to execute `curl` for making the API request. Input values like `owner`, `repo`, and `workflow` are properly sanitized using `encodeURIComponent` for URL path construction, and the request body is `JSON.stringify`'d. The `spawn` function is used without `shell: true`, which significantly mitigates shell injection risks. Environment variables `GITEA_URL` and `GITEA_TOKEN` are used as expected for authentication and API endpoint definition, without any evidence of exfiltration to unauthorized destinations. The `SKILL.md` file contains no prompt injection attempts or malicious instructions for the AI agent.
Capability Assessment
Purpose & Capability
Name/description, required env vars (GITEA_URL, GITEA_TOKEN), inputs, and index.js behavior align with a Gitea workflow dispatcher. The code constructs the expected Gitea API URL and sends an Authorization header with the provided token, which is proportionate to the stated purpose.
Instruction Scope
SKILL.md and metadata declare only 'node' as a required binary, but index.js spawns the external 'curl' command to perform the HTTP request. The instructions/examples do not mention curl or network behavior beyond the Gitea URL. The skill will execute a child process and inherit the agent's full environment when spawning curl, which is not documented in the SKILL.md.
Install Mechanism
No install spec or remote downloads are present; this is an instruction-only skill with a small included index.js file. Nothing is fetched from arbitrary URLs or installed at runtime by the skill package itself.
Credentials
Only GITEA_URL and GITEA_TOKEN are required and declared as the primary credential — these are appropriate for calling a Gitea API. The code uses the token only to set the Authorization header to the provided GITEA_URL endpoint. No unrelated secrets are requested.
Persistence & Privilege
The skill is not always-enabled and doesn't request elevated/persistent system privileges or modify other skills. It simply runs when invoked.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install gitea-workflow-dispatch - After installation, invoke the skill by name or use
/gitea-workflow-dispatch - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.2
- Added OpenClaw metadata to SKILL.md, specifying requirements and description.
- No changes to functionality or usage.
v0.1.1
- Added skill.json file for improved metadata and configuration.
- Updated _meta.json with latest changes.
- No changes to functionality or usage.
v0.1.0
Initial release of gitea-workflow-dispatch.
- Trigger Gitea/Forgejo workflow_dispatch events via API.
- Supports custom workflow file, git ref, and workflow inputs.
- Includes dry run mode for testing.
- Configuration via GITEA_URL and GITEA_TOKEN environment variables.
Metadata
Frequently Asked Questions
What is Gitea Workflow Dispatch?
Trigger Gitea/Forgejo workflow_dispatch via API. It is an AI Agent Skill for Claude Code / OpenClaw, with 427 downloads so far.
How do I install Gitea Workflow Dispatch?
Run "/install gitea-workflow-dispatch" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Gitea Workflow Dispatch free?
Yes, Gitea Workflow Dispatch is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Gitea Workflow Dispatch support?
Gitea Workflow Dispatch is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Gitea Workflow Dispatch?
It is built and maintained by Tom (@qizhou-guo); the current version is v0.1.2.
More Skills