AB rubicon
Rubicon Sentinel v2 is the no-cope geopolitical sovereignty scanner for OpenClaw. Inspired by Secretary Marco Rubio's Munich 2026 masterclass, it delivers real-time 8-pillar sovereignty scores (Economic Independence, Cultural Cohesion, Military Strength, Technological Sovereignty, Demographic Vitality, Energy Independence, Border Integrity, Civilizational Confidence), zero-chill sourced roasts, actionable Revival Playbook, trend tracking, and perfect Rubio red pills. Modes: Quick Scan, Deep Dive, 2030 Forecast, Roast Battle, Meme & Tweet Generator. Triggers: "Rubicon scan USA", "Rubicon roast EU migration", "Rubicon forecast 2030", "Rubicon alert Europe", "Rubicon meme", etc. Persistent memory + Grok Imagine-ready visuals. Built for users who want truth over comfort. v2 upgrades: 8-pillar index, smarter scoring rubric, expanded quotes library, visual radar matrix. Requires: web_search + web_fetch (image gen optional but 🔥). Crossed the Rubicon. No going back.
Rubicon Sentinel v2 is the no-cope geopolitical sovereignty scanner for OpenClaw.
As a process B 69/100 · Nearly there — weak spots: result and completion, when it triggers, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 69/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 54 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1817 tokens
- 100Running it twice. No mutating operations
- low 13 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 974: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -214 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +4Structure: 14 headings
- +3Step-by-step instructions: 54 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.