ariffazil/APEX-humility-godel
skills/APEX-humility-godel/SKILL.md
Self-critique and epistemic humility protocol before SEAL-grade or high-confidence claims. Meta-critique, confidence bands, explicit unknowns. F2, F7 enforced. BIJAKSANA: XML-tagged for Claude, numbered steps for Codex, imperative for Hermes.
$ install --global
skillsauthnpx skillsauth add ariffazil/openclaw-workspace APEX-humility-godelInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Aug 8, 2026, 3:48 AM227.4s2 files scanned
SKILL.md
- id:
- APEX-humility-godel
- name:
- APEX-humility-godel
- owner:
- 888-APEX
- risk_tier:
- low
- version:
- 2.0.0
- description:
- >
- BIJAKSANA:
- XML-tagged for Claude, numbered steps for Codex, imperative for Hermes.
- floor_scope:
- [F02, F07]
- claude:
- Use <confidence-band>, <unknowns>, <meta-critique> tags. Recall prior calibration from extended context.
- codex:
- Step 1: state claim. Step 2: assign confidence. Step 3: list unknowns. Step 4: attack claim. Step 5: adjust.
- hermes:
- State claim. How sure? What you don't know. Attack it. Adjust. Seal or hold.
- autonomy_tier:
- T1
APEX-humility-godel
<cognitive-note model="claude">XML-tagged confidence analysis. Use extended recall to check calibration against prior claims.</cognitive-note> <cognitive-note model="codex">5-step humility protocol. Each step must complete before next. Log reasoning at each step.</cognitive-note> <cognitive-note model="hermes">5 steps. Claim → Confidence → Unknowns → Attack → Adjust. Fast.</cognitive-note>
Protocol
Step 1: State the Claim
<claim format="codex-schema"> ```json { "claim": "precise statement", "domain": "geoscience|engineering|governance|etc", "stakes": "high|medium|low", "reversibility": "reversible|irreversible" } ``` </claim>Step 2: Assign Confidence Band
<confidence-band> - Point estimate: 0.0 - 1.0 - Band width: ±X (how uncertain is the estimate itself?) - Calibration check: How often have I been right at this confidence level? - F7 constraint: Ω₀ ∈ [0.03, 0.05]. No fake certainty. </confidence-band>Step 3: List Explicit Unknowns
<unknowns> What I do NOT know that could invalidate this claim: 1. Missing data sources 2. Unverified assumptions 3. Domain boundaries I cannot cross 4. Contradictory evidence I chose to discount </unknowns>Step 4: Attack the Claim (Meta-Critique)
<meta-critique> - What would a skeptic say? - What evidence would falsify this? - Am I anchored to a prior belief? - Is this claim's confidence inflated by social pressure? </meta-critique>Step 5: Adjust and Verdict
<verdict> - If attack succeeds: reduce confidence, add caveats, or withdraw claim - If attack fails: maintain confidence with documented defense - Output: adjusted confidence band + remaining unknowns + verdict - **Verdict must use the canonical closed 6-value taxonomy** from `arifOS/runtime/verdict.py`: `OBSERVE_ONLY` | `SEAL` | `SABAR` | `VOID` | `HOLD` | `888_HOLD` - Authority band must use the canonical 4-band taxonomy from `arifOS/runtime/session_standing.py`: `OBSERVE_ONLY` | `LIMITED_MUTATE` | `FULL` | `SOVEREIGN` - Legacy fields (`verdict_code`, `canonical_verdict`, `reasoning_verdict`, `nine_signal`) are DEPRECATED post-KSR Epoch 1+2; use `effective_verdict` + `reason_code` + `next_action` instead. </verdict>Floors
- F2 TRUTH: Confidence must be grounded in evidence, not hope.
- F7 HUMILITY: Ω₀ ∈ [0.03, 0.05]. Explicit unknowns required.
Related Skills
ariffazil/openclaw
testing
VerifiedTrustedCommunity
OpenClaw edge agent bridge — operational triage, doctor, restart, and A2A bridge routing for the federation edge (Telegram surface). USE WHEN: "openclaw unhealthy", "gateway down", "edge bot not responding", "a2a bridge disconnected", "watchdog tripped", "openclaw doctor", "openclaw restart". NOT for token/security audit — use FORGE-telegram-audit.
2SKILL.mdUpdated Aug 8, 2026
ariffazil/MiniMax Image Generation
tools
VerifiedTrustedCommunity
Generate images, videos, TTS, voice clone, and music via MiniMax MCP server. Use when user asks to "draw", "generate image", "create picture", "make a photo", "text to image", "image generation".
2SKILL.mdUpdated Aug 8, 2026
ariffazil/arifos-constitutional-judge
testing
VerifiedTrustedCommunity
Single load-bearing constitutional-judgment skill. Routes all F1–F13, verdict, hold, seal, scope, authority and floor-check calls through the live arif_judge surface. Replaces 7 overlapping predecessors (arifos-constitutional-judge, arifos-constitutional-judge, arifos-constitutional-judge, arifos-constitutional-judge, arifos-constitutional-judge, arifos-constitutional-judge, arifos-constitutional-judge).
2SKILL.mdUpdated Aug 8, 2026
ariffazil/FORGE-lsp-pre-edit-gate
development
VerifiedTrustedCommunity
MANDATORY LSP grounding gate BEFORE any code mutation on .ts, .py, .js, .tsx, .jsx files. Forces the agent to read real-time compiler diagnostics and structural project context before editing — eliminating blind guesses and anchoring every mutation in F2 (TRUTH). Routes through arifOS kernel (:8088) for centralized gate logic.
2SKILL.mdUpdated Aug 8, 2026