Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · AI
Rule Creation
Auto-triggers Context Engineering compliance and Lobster enforcement when proposing, creating, or formalizing rules, policies, processes, or behavioral const...
skill openclawclawhub Free
Auto-triggers Context Engineering compliance and Lobster enforcement when proposing, creating, or formalizing rules, policies, processes, or behavioral const...
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, package.json, scripts/check-lobster-available.js, scripts/create-lobster-workflow.js, scripts/evaluate-enforcement-need.js
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.1.0
Provenance
- Publisher
- levineam
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Description
Auto-triggers Context Engineering compliance and Lobster enforcement evaluation when proposing, creating, or formalizing new rules, policies, processes, workflows, or behavioral constraints. Context Engineering is the practice of wiring rules into your AI's context so they're reliably followed — not just hoped for via prompting. Credit: Muratcan Koylan (@koylanai) Use this skill any time you are: Declaring a new rule (e.g. "From now on, always X") Formalizing a policy (e.g. "The policy for Y is Z") Creating a behavioral constraint (e.g. "Never do X without doing Y first") Proposing a process or workflow Updating governance documents (TOOLS.md, CRITICAL-RULES.md, CONSTITUTION.md, etc.)
When This Skill Matches
Trigger phrases: "Add this rule…" "Create a policy…" "From now on…" "The rule is…" "New constraint…" "Formalize that…" "Wire this rule…" "Make it a HARD rule…" Any governance/policy update request
Mandatory Workflow
When this skill triggers, always execute the following steps in order. Do NOT ask permission — CE-PROCESS compliance means wire first, report after.
Step 1: Identify the Rule
Extract: Rule name — short slug (e.g. no-bare-spawns, external-message-gate) Rule description — plain language statement of what the rule requires Rule type — HARD (non-negotiable, always enforced) or soft (guideline, use judgment)
Step 2: Evaluate Enforcement Need (CR-012 Criteria)
Run scripts/evaluate-enforcement-need.js or apply manually: A rule needs Lobster enforcement if ANY of the following are true: CriterionExamplesHigh-stakesSends external messages, spends money, deletes data, publishes public content, deploys to productionPattern of violationsA similar rule was already stated but broken or ignoredMulti-step sequenceRequires multiple ordered steps (do A, then B, then C)External / public actionAffects things outside the user's local files Scoring: 0 criteria matched → needsEnforcement: false (wire to TOOLS.md only) 1+ criteria matched → needsEnforcement: true (create Lobster workflow + wire)
Step 3: Lobster Availability Preflight
Before creating any workflow, verify Lobster is actually enabled: Run scripts/check-lobster-available.js or check manually: openclaw plugins list | grep -i lobster OutputMeaningActionlobster … loaded✅ AvailableProceed to Step 3alobster … disabled❌ UnavailableUse fallback (below)No lobster row❌ Not installedUse fallback (below) Fallback when Lobster is unavailable: Skip workflow creation entirely Proceed directly to Step 4 (wire to docs) — no Lobster reference in the entry Report: ⚠️ Enforcement: unavailable (Lobster not enabled) Include hint: Run: openclaw plugins enable lobster to activate Never claim enforcement is wired when Lobster is disabled.
Step 3a: Create Lobster Workflow (enforcement needed AND Lobster available)
If needsEnforcement: true and Lobster preflight passed: Copy templates/lobster-workflow.template.lobster Fill in: name, description, steps specific to rule enforcement Save to workflows/<rule-name>.lobster Note the workflow path for wiring
Step 4: Wire to Docs
Run scripts/wire-rule-to-docs.js or manually append to the appropriate file: Routing: Operational rules → TOOLS.md Identity/persona constraints → SOUL.md or agents/identity.md Hard system rules → CRITICAL-RULES.md (if exists) or AGENTS.md Project-specific rules → relevant project board or agents/projects.md Entry format (from templates/tools-md-entry.template.md): ## <Rule Name> (<HARD|soft>) <Rule description> [If Lobster enforcement]: **Enforced by:** `workflows/<rule-name>.lobster`
Step 5: Report What Was Done
Your response must include: ✅ Rule wired: <Rule Name> 📄 Location: <file where it was added> 🔒 Enforcement: <Lobster workflow path OR "TOOLS.md entry only"> 📋 Type: <HARD|soft> Never say: ❌ "Want me to add this to TOOLS.md?" ❌ "Should I wire this through CE?" ❌ "Is this CE compliant?" Always say: ✅ "Added <rule> to <file>. Enforcement: <status>."
Script Reference
ScriptPurposescripts/check-lobster-available.jsPreflight: verify Lobster plugin is enabled in this OpenClaw instancescripts/evaluate-enforcement-need.jsEvaluate CR-012 criteria against rule descriptionscripts/wire-rule-to-docs.jsAppend rule entry to TOOLS.md or specified target filescripts/report-rule-creation.jsGenerate user-facing summary of what was created
Workflow Reference
WorkflowPurposeworkflows/create-rule.lobsterFull end-to-end rule creation pipeline
Context Engineering Auto-Trigger (HARD)
This skill embodies the Context Engineering Auto-Trigger principle: "When proposing any new rule, behavioral constraint, or policy change: Wire it first. Add the rule to the appropriate file BEFORE responding. Never ask permission to formalize a rule." The act of recognizing a rule IS the trigger. Wire immediately. Report after.
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Scripts2 Docs1 Config
- SKILL.md
- README.md
- scripts/check-lobster-available.js
- scripts/create-lobster-workflow.js
- scripts/evaluate-enforcement-need.js
- package.json