oceinteg
Skill454 starsChanged 9 days agoMITView on GitHub
Run named OpenClaw Enterprise end-to-end integration scenarios against real supported installations. Use only when explicitly invoked.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- autoreviewSkill
- console-uiSkill
- design-reviewSkill
- deslopSkill
- enterprise-testingSkill
- local-devSkill
- mermaid-diagramsSkill
- oce-cookbookSkill
- pr-walkthroughSkill
- specSkill
- technical-writingSkill
- test-auditSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Use this skill only when the user explicitly invokes oceinteg <scenario> or $oceinteg <scenario>.
- Distinctive: line 11
Follow $enterprise-testing for real-runtime prerequisites, evidence, and failure classification, then read only the selected scenario below.
- Distinctive: line 18
If the scenario is missing or unknown, show the available names and ask which one to run.
- Very specific: line 22
Add future scenarios as references/<scenario>.md and register them here.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
OCE integration scenarios
Use this skill only when the user explicitly invokes oceinteg <scenario> or
$oceinteg <scenario>. Do not activate it for general integration-testing requests.
Follow $enterprise-testing for real-runtime prerequisites, evidence, and failure
classification, then read only the selected scenario below.
| Invocation | Scenario |
oceinteg main | Main acceptance test: fresh installation, both runtime presets, repository permissions, Slack, Linear approvals, and native UI continuity. |
If the scenario is missing or unknown, show the available names and ask which one to run. Do not substitute another scenario or start infrastructure work. Creating or editing this skill does not run its scenarios.
Add future scenarios as references/<scenario>.md and register them here. Keep
each scenario's inputs, external effects, procedure, assertions, and cleanup in
its own reference. This is an agent workflow, not an installed shell command.
For main, also read Runtime and isolation acceptance
and Supply credentials. These are required parts
of main, not separately invokable scenarios.
Choose one setup reference per selected topology before running main:
| Topology | Setup |
| EKS with Helm OCC | EKS setup |
| Local k3d with Helm OCC | Kubernetes-only setup |
| Local k3d with Compose OCC | Compose and Kubernetes setup |
These references sequence the user-facing guides; those guides own commands and supported configuration. Setup references are not additional invocations.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.