Use this skill whenever the user needs to operate a self-managed GitLab or self-hosted Gitea CI/CD server — a one-shot overview, server version and token identity, projects with storage statistics, pipelines/runs with jobs and trace tails, the runner fleet, merge/pull requests, branches, protection rules and releases, artifact inventories, four flagship RCAs (pipeline failures, runner health & queue, artifact/storage bloat, stale work), and governed writes (retry/cancel a pipeline, pause/resume a runner, delete ar…
Identity and source
Publisher attributionwei zhouregistry owner unverified by skillvetai
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
Status
completed
Coverage
full text content
Files
6 / 6 inspected as text
Checked
9/13/2026, 4:48:02 AM
Scanner
0.1.3
Policy
1.0.3
2 inferred permission indicators
network access — automatically inferred
filesystem write — automatically inferred
2 dependency and API indicators
api: clawhub.ai
api: github.com
External clawhub result: suspicious
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
Evidence checked
9/12/2026, 2:18:27 PM
Release binding
Matches this record
skillspector: suspicious
llm: suspicious
Recorded files
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
- Documentation updated in SKILL.md: clarified OpenClaw installation instructions and other minor improvements. - skill-card.md file removed. - No functional or code changes; this is a documentation and packaging update only.
Release security diff
mediumCompared fixed releases 0.10.0 and 0.10.2; 0 finding and 0 permission indicators were added.
Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.
Change reasons and limitations
content hash changed
Observed release history
These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.