← Back to Skills Marketplace
316
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install tribunal-usage
Description
Use Tribunal commands for TDD enforcement, quality gates, secret scanning, Agent Teams hooks, CI integration, and plugin packs. Use when running quality chec...
Usage Guidance
This skill appears to be an instruction wrapper around an external 'tribunal' tool and is mostly coherent with that purpose — but there are important gaps you should verify before installing: 1) Confirm the provenance of the 'tribunal' tool you will run (pip package and/or binary) and review its code or vendor trust. 2) Expect the tool to read and write project files (.tribunal/, tribunal/rules/) and to create an audit log; review those files for sensitive content and consider running in a fork/CI sandbox first. 3) The SKILL.md references environment variables (CLAUDE_CODE_MODE, CLAUDE_CONTEXT_WINDOW) and MCP/network integrations that are not declared in the skill metadata — ask where the MCP server is hosted and whether any credentials are needed, and avoid pointing sensitive data to unknown endpoints. 4) If you use plugin packs from URLs or registries, inspect them before installing. If you lack confidence in the external tribunal package or the MCP endpoint, run this in an isolated environment or decline installation.
Capability Analysis
Type: OpenClaw Skill
Name: tribunal-usage
Version: 1.0.0
The skill bundle describes 'Tribunal,' a quality enforcement tool that integrates deeply with the development environment by hooking into every file write and test run. While its stated purpose is benign (TDD enforcement and secret scanning), it includes high-risk capabilities such as installing plugin packs from arbitrary remote URLs (e.g., `tribunal install <url>`) and monitoring all agent interactions. These features provide a significant attack surface for remote code execution or data access, although no explicit malicious intent or obfuscation was found in the documentation (SKILL.md).
Capability Assessment
Purpose & Capability
Name/description (Tribunal quality enforcement) align with requiring a 'tribunal' binary and the commands shown. It's plausible the skill is instruction-only and relies on a local 'tribunal' tool. The README points to a sensible homepage and repository. However the SKILL.md also instructs installing via pip and using project-local config files (.tribunal), which is consistent but not declared in requires.env/manifest.
Instruction Scope
The instructions tell the agent to run tribunal commands that read/write project state and an audit log (.tribunal/audit.jsonl), auto-inject rules (tribunal/rules/*), and integrate with an MCP server. They also reference using CLAUDE_CODE_MODE and CLAUDE_CONTEXT_WINDOW environment variables and CI usage. These are within the stated purpose, but they grant the tool the ability to inspect and modify repository files and to send/query data via an MCP connector — behavior that isn't explicitly declared in the skill metadata.
Install Mechanism
No install spec is present (instruction-only skill), which minimizes direct install-time risk. The SKILL.md suggests 'pip install tribunal' and other package installs, but those are external developer actions rather than an automated install specified in the skill bundle.
Credentials
The skill metadata lists no required env vars, yet the instructions reference CLAUDE_CODE_MODE and CLAUDE_CONTEXT_WINDOW. The skill also describes MCP integration (pointing a connector to a 'Tribunal MCP server') and installing plugin packs from URLs or registries — these imply network endpoints and possible transfer of code/config, but no network endpoints or credentials are declared. Lack of declared env/credential requirements is an inconsistency and makes it unclear what secrets or endpoints the skill expects or will use.
Persistence & Privilege
always:false (good). The tool is described as hooking into file writes and writing audit logs and 'auto-injecting' rules into the repo, which gives it persistent, project-scoped effects (writes under .tribunal/ and tribunal/rules/). The skill itself doesn't request system-wide privileges, but its described behavior will persist changes within projects and interact with multi-agent workflows — review such writes before allowing them.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install tribunal-usage - After installation, invoke the skill by name or use
/tribunal-usage - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Full usage guide — commands, modes, Agent Teams, CI, MCP, plugin packs
Metadata
Frequently Asked Questions
What is Tribunal Usage?
Use Tribunal commands for TDD enforcement, quality gates, secret scanning, Agent Teams hooks, CI integration, and plugin packs. Use when running quality chec... It is an AI Agent Skill for Claude Code / OpenClaw, with 316 downloads so far.
How do I install Tribunal Usage?
Run "/install tribunal-usage" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Tribunal Usage free?
Yes, Tribunal Usage is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Tribunal Usage support?
Tribunal Usage is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Tribunal Usage?
It is built and maintained by koshaji (@koshaji); the current version is v1.0.0.
More Skills