Weft Frontend
WeaveMindAI/weft
Read when the user wants a page, app or site for the program, and before dispatching the frontend-builder: the verified scaffold commands, the default stack (pnpm, SvelteKit, PostgreSQL, BetterAuth…
Select proportional Enterprise validation and diagnose exact CI runs, distinguishing product, harness, infrastructure, and credential failures.
Install Enterprise Testing
$ npx skills add openclaw/openclaw-enterprise --skill enterprise-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openclaw/openclaw-enterprise enterprise-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openclaw/openclaw-enterprise.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/enterprise-testing .claude/skills/enterprise-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "enterprise-testing" agent skill from https://github.com/openclaw/openclaw-enterprise/tree/main/.agents/skills/enterprise-testing into .claude/skills/enterprise-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "enterprise-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openclaw/openclaw-enterprise/tree/main/.agents/skills/enterprise-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openclaw/openclaw-enterprise --skill enterprise-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openclaw/openclaw-enterprise enterprise-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw-enterprise.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/enterprise-testing .agents/skills/enterprise-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "enterprise-testing" agent skill from https://github.com/openclaw/openclaw-enterprise/tree/main/.agents/skills/enterprise-testing into .agents/skills/enterprise-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "enterprise-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openclaw/openclaw-enterprise --skill enterprise-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openclaw/openclaw-enterprise enterprise-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw-enterprise.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/enterprise-testing .cursor/skills/enterprise-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "enterprise-testing" agent skill from https://github.com/openclaw/openclaw-enterprise/tree/main/.agents/skills/enterprise-testing into .cursor/skills/enterprise-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "enterprise-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openclaw/openclaw-enterprise.git --path .agents/skills/enterprise-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openclaw/openclaw-enterprise --skill enterprise-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openclaw/openclaw-enterprise enterprise-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw-enterprise.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/enterprise-testing .gemini/skills/enterprise-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "enterprise-testing" agent skill from https://github.com/openclaw/openclaw-enterprise/tree/main/.agents/skills/enterprise-testing into .gemini/skills/enterprise-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "enterprise-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openclaw/openclaw-enterprise enterprise-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openclaw/openclaw-enterprise --skill enterprise-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openclaw/openclaw-enterprise.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/enterprise-testing .github/skills/enterprise-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "enterprise-testing" agent skill from https://github.com/openclaw/openclaw-enterprise/tree/main/.agents/skills/enterprise-testing into .github/skills/enterprise-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "enterprise-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openclaw/openclaw-enterprise --skill enterprise-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openclaw/openclaw-enterprise enterprise-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw-enterprise.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/enterprise-testing .opencode/skills/enterprise-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "enterprise-testing" agent skill from https://github.com/openclaw/openclaw-enterprise/tree/main/.agents/skills/enterprise-testing into .opencode/skills/enterprise-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "enterprise-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
enterprise-testing- GitHub stars
- 359
- Token cost
- ~1.6k tokens
- SKILL.md length
- 641 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
Select proportional Enterprise validation and diagnose exact CI runs, distinguishing product, harness, infrastructure, and credential failures.
- Databases work in your project
- SKILL.md covers Select proof, Real-runtime boundaries, Diagnose CI and Provenance
- Calls pnpm, gh and node
What it does
Enterprise Testing is an agent skill from openclaw/openclaw-enterprise. Select proportional Enterprise validation and diagnose exact CI runs, distinguishing product, harness, infrastructure, and credential failures.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Databases. It works with PostgreSQL, pnpm and Docker. The repository describes itself as: The Enterprise-grade Control Plane for modern agentic workloads. The licence is MIT.
When your agent uses it
- Databases work in your project
Example prompts
- “/enterprise-testing”
Requirements
- Node.js
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit 96faf10. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpmghnodenpmgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, gh, npm and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Enterprise Testing loads about 1.6k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 641 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from openclaw/openclaw-enterprise at commit 96faf10, republished under its MIT licence (© openclaw). 641 words, ~1,646 tokens.
Download SKILL.mdSave it as
.claude/skills/enterprise-testing/SKILL.md (or your agent's skills folder).- name
- enterprise-testing
- description
- Select proportional Enterprise validation and diagnose exact CI runs, distinguishing product, harness, infrastructure, and credential failures.
Enterprise Testing
Prove the changed contract with the smallest meaningful check, complete required checks, then stop. Broaden or repeat for new changes, failures, or unresolved risks. Use test-audit when authoring or reviewing tests; do not create tests that merely mirror a reversible documentation or style edit.
Read the touched scope's AGENTS.md and the selected
testing guide. Run commands from the repository
root. Use Node.js 24 or newer and repository-pinned pnpm with matching installed
dependencies. Do not install or reconcile dependencies as a verification side
effect. Report missing prerequisites; dependency-independent checks prove only
their own scope. Never run npm run precommit.
Select proof
| Changed contract | Starting proof and owner |
|---|---|
| Domain or Driver behavior | node --test tests/conformance/<name>.test.mjs; broaden to pnpm test:conformance when relevant. |
| API or controller behavior | node --test tests/integration/<name>.test.mjs; broaden to pnpm test:integration. See local checks. |
| PostgreSQL persistence | pnpm test:postgres after the database prerequisites; use the actual database for persisted invariants. |
| Docker runtime | pnpm docker:test with explicit selectors, images, and credentials from Docker testing. |
| Kubernetes | Select the exact fixture or runtime file from Kubernetes testing, with its disposable cluster and database prerequisites. |
| Console UI | pnpm test:console-browser with the prepared browser described in browser testing. |
| Types, package boundaries, generated API | pnpm typecheck (also the current build command); pnpm openapi:check for API changes. |
| Documentation or skills | pnpm docs:check, relevant links, and git diff --check; no runtime tests solely for prose changes. |
| CI or test selection | node scripts/ci/run-tests.mjs audit; inspect CI ownership, and use actionlint for workflow edits when available. |
Run pnpm check:workspace and applicable pnpm format:check with the installed
graph. The root formatter does not include .agents/skills/**/*.md; inspect
adapted skill Markdown separately. Keep the vendored autoreview directory unchanged.
Use the local checks guide for formatting and
generated-artifact procedures. Resolve <name> to existing owner/sibling tests;
do not run placeholder commands. When all conformance and integration contracts
need proof, pnpm test selects both; browser and credentialed coverage still
depend on their documented selection and prerequisites.
Real-runtime boundaries
Use only owned disposable resources and authorized credentials. Scope selection variables to the chosen process; preserve shared dependencies, services, databases, kubeconfig, and unrelated clusters. Do not run untrusted contributor tooling against a credentialed local environment; use an approved isolated CI environment. Setup and credentialed execution need their existing authorization.
Follow repository integration requirements and each suite's guide for images, model selection, database roles, credential placement, networking, and cleanup. Do not bypass missing credentials, disable isolation, or substitute a fake for requested runtime proof. Selected required cluster/runtime cases must pass without skips. Fixture or in-memory success does not prove genuine gateway, Codex WebSocket, model execution, or production deployment. A green PR aggregate does not prove manual credentialed lanes ran.
Show full SKILL.md (201 more words)Show less
Diagnose CI
gh pr view <pr> --json headRefOid,statusCheckRollup
gh run view <run-id> --json status,conclusion,headSha,url,jobs
gh run view <run-id> --job <job-id> --logBind evidence to the PR head, actual run SHA, run ID, and job ID. A pull-request run may test a merge commit: record that relation rather than assuming its SHA equals the branch head. Inspect the latest attempt for that source; confirm whether a newer run superseded a cancellation. Fetch relevant leaf logs and result artifacts, not just the rollup status. Use CI result accounting and coverage to interpret selected lanes and skips.
- Product: supported behavior fails with valid setup; reproduce narrowly, repair the owning implementation, and rerun that proof.
- Harness: selection, setup, assertions, or result accounting are wrong; repair the harness without weakening required outcomes.
- Infrastructure: provisioning, image availability, networking, or capacity fails; retain evidence and retry the affected job only when justified.
- Credentials: approved credentials, access, or protected-environment approval is missing; report the gap without exposing values or substituting mock proof.
Do not infer a category solely from a check name. State uncertainty when logs are unavailable. Route unrelated failures with evidence instead of expanding the task; never rerun a broad workflow merely to erase a failure. Report commands, source/run/job identity, pass/fail/skip counts, proof limits, and remaining blockers.
Provenance
Adapted from OpenClaw; see source and intentional adaptations.
© openclaw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/enterprise-testing of openclaw/openclaw-enterprise.
Open the folder on GitHubat commit 96faf10
Compare with similar skills
Enterprise Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Enterprise Testing this skillopenclaw/openclaw-enterprise | 359 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Weft FrontendWeaveMindAI/weft | 2k | — | ~8k | Automated safety check: Notes | Custom licence | |
| Iron Proxy Gateway for NanoClawnanocoai/nanoclaw | 31k | — | ~4.6k | Automated safety check: Notes | MIT | |
| How To Communicatedatabasus/databasus | 8.8k | — | ~3.9k | Automated safety check: Pass | MIT | |
| SQL Database Support for pRESTprest/prest | 4.6k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Rhctlsaidake/rhctl | 106 | — | ~4k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Iron Proxy Gateway for NanoClaw
nanocoai/nanoclaw
Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.
How To Communicate
databasus/databasus
Communicate clearly in every response, progress update and agent-authored document.
SQL Database Support for pREST
prest/prest
Guides classifying, gap-analyzing and scaffolding support for a new SQL database in pREST, from Postgres-compatible variants to entirely new dialects.
Rhctl
saidake/rhctl
Run and author rhctl CLI workflows and remote environment scripts under scripts/ (PostgreSQL, JetStream, Docker, Redis, MongoDB, AWS LocalStack, execute/upload/patch).
Veloxdb Scalable Performance
veloxbase/veloxdb
Guides scalability and performance work for VeloxDB's Tauri + Rust PostgreSQL backend and React + TanStack frontend.
More from openclaw/openclaw-enterprise
All 9 skills in this repoLocal Dev
openclaw/openclaw-enterprise
Develop OpenClaw Enterprise changes with proportional verification and source-backed flow documentation for non-trivial behavior.
Technical Writing
openclaw/openclaw-enterprise
Write, organize, name, edit, or review Enterprise developer documentation, specifications, and technical instructions; ground claims in current source and finish with a plain-language cleanup.
Test Audit
openclaw/openclaw-enterprise
Gate new or changed Enterprise tests and audit existing tests for observable behavior, credible regressions, duplicate coverage, and test-only production seams.
Mermaid Diagrams
openclaw/openclaw-enterprise
Create or refine readable Mermaid diagrams for changes, architecture, lifecycles, and dependencies in Markdown documents and PR descriptions.
Design Review
openclaw/openclaw-enterprise
Assess designs, public interfaces, state ownership, readability, and refactor proposals when the task calls for design review or structural simplification; not for unrelated routine edits.
Deslop
openclaw/openclaw-enterprise
Clean only the current Enterprise diff before autoreview, preserving behavior, security boundaries, required TODOs, and useful test-intent comments.
Related
Works with
Categories
Questions about Enterprise Testing
What does Enterprise Testing do?
Select proportional Enterprise validation and diagnose exact CI runs, distinguishing product, harness, infrastructure, and credential failures. Enterprise Testing is an agent skill from openclaw/openclaw-enterprise. Select proportional Enterprise validation and diagnose exact CI runs, distinguishing product, harness, infrastructure, and credential failures.
When should I use Enterprise Testing?
Enterprise Testing fits situations like: databases work in your project.
How do I install Enterprise Testing in Claude Code?
Run `npx skills add openclaw/openclaw-enterprise --skill enterprise-testing -a claude-code`. Or copy the skill folder (.agents/skills/enterprise-testing in openclaw/openclaw-enterprise) into .claude/skills/enterprise-testing in your project. Claude Code loads it when a task matches its description.
How do I install Enterprise Testing in Codex?
Run `npx skills add openclaw/openclaw-enterprise --skill enterprise-testing -a codex`. Or copy the skill folder (.agents/skills/enterprise-testing in openclaw/openclaw-enterprise) into .agents/skills/enterprise-testing in your project. Codex loads it when a task matches its description.
Can I use Enterprise Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openclaw/openclaw-enterprise --skill enterprise-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/enterprise-testing, .gemini/skills/enterprise-testing, .github/skills/enterprise-testing and .opencode/skills/enterprise-testing in your project.
What does Enterprise Testing need to run?
Going by SKILL.md and its folder, Enterprise Testing needs the command-line tools its instructions call (pnpm, gh, node, npm and git). Our summary lists: Node.js; Docker.
Does Enterprise Testing access the network?
SKILL.md contains no URLs. Its commands use gh, npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Enterprise Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Enterprise Testing use?
Enterprise Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Enterprise Testing use?
About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Enterprise Testing?
Skills that share tags, products or a category with Enterprise Testing: Weft Frontend (WeaveMindAI/weft, 2k stars), Iron Proxy Gateway for NanoClaw (nanocoai/nanoclaw, 31k stars), How To Communicate (databasus/databasus, 8.8k stars) and SQL Database Support for pREST (prest/prest, 4.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Enterprise Testing?
openclaw (a GitHub organization) maintains it in openclaw/openclaw-enterprise, which has 359 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.
Source: openclaw/openclaw-enterprise on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.