narco-check
Narco-check is a memory integrity audit skill that runs after two consecutive task failures or nightly at 3 AM to detect system state corruption. It uses Claude Opus 4.6 to validate workspace files, system commands, and endpoint health through a structured 5-4-3-2-1 grounding protocol, classifying results as CLEAN, DEGRADED, or POISONED to prevent contaminated memory entries from propagating through the agent's decision-making process.
git clone --depth 1 https://github.com/open-gitagent/opengap /tmp/narco-check && cp -r /tmp/narco-check/examples/jason-my-claw-is-the-law-deebee-4567b4/skills/narco-check ~/.claude/skills/narco-checkSKILL.md
# Narco-Check — Memory Integrity Audit
## When This Runs
1. **Failure trigger:** 2 consecutive failures on the same task or tool
2. **End-of-day trigger:** Nightly deep dive audit (~3 AM)
## Audit Model
Must use `openrouter/anthropic/claude-opus-4.6`. Never run narco-check on a tier-0 or tier-1 model.
```bash
openclaw agent --model openrouter/anthropic/claude-opus-4.6 \
--message "$(cat ~/.openclaw/workspace/skills/narco-check/audit-prompt.md)" \
--mode now
```
## 5-4-3-2-1 Grounding Check
Run this first — before reading any logs. Anchors the audit in real system state.
**5 — Run five commands, paste raw output verbatim:**
```bash
date
hostname
df -h /
docker ps --format "table {{.Names}}\t{{.Status}}"
cat ~/.openclaw/workspace/HEARTBEAT.md | head -3
```
**4 — Confirm four workspace files exist, paste first line:**
```bash
head -1 ~/.openclaw/workspace/IDENTITY.md
head -1 ~/.openclaw/workspace/SOUL.md
head -1 ~/.openclaw/workspace/MEMORY.md
head -1 ~/.openclaw/workspace/HEARTBEAT.md
```
**3 — Ping three endpoints, report HTTP codes:**
```bash
curl -s -o /dev/null -w "%{http_code}" http://localhost:18789/health
curl -s -o /dev/null -w "%{http_code}" --max-time 5 https://geniewars.com
curl -s -o /dev/null -w "%{http_code}" --max-time 5 https://siliconchimps.com
```
**2 — Run one Exa search, paste first real result:**
```bash
~/.openclaw/workspace/skills/exa-search/exa.sh "$(date +%Y) advance reader community" 2
```
**1 — State one provable fact:**
```
GROUNDED: [claim] — verified by [command] — output: [exact output]
```
A grounded check with failures is valid. A grounded check with fabricated output is **POISONED**.
## Audit States
- `CLEAN` — no failures, no audit triggered
- `DEGRADED` — issues found, state acceptable, resumed with different approach
- `POISONED` — contaminated entries found, stop and notify Ludo
If POISONED: mark affected MEMORY.md entries `[QUARANTINE YYYY-MM-DD]`, notify Ludo via Slack DM before proceeding.Reviews code diffs and files for security vulnerabilities (OWASP Top 10), error handling, complexity, naming conventions, and performance issues. Use when the user asks to review a PR, pull request, diff, merge request, or code changes.
>
Creates and configures agent.yaml files, writes SOUL.md personality definitions, and sets up agent directory structures with skills, tools, and knowledge. Use when the user wants to configure an agent, create agent.yaml, write SOUL.md, set up agent directory structure, or customize agent settings.
Reviews financial documents (prospectuses, ADVs, marketing materials) for FINRA 2210 compliance, required disclosures, and balanced presentation. Use when reviewing financial statements, audit documents, regulatory filings, or when the user mentions compliance checks, financial audits, or document verification.
Converts agent definitions between frameworks — exports to Claude Code, OpenAI, CrewAI, Lyzr, and GitHub Models formats, and imports from Claude, Cursor, and CrewAI projects. Use when the user wants to convert an agent, migrate to another framework, export to LangChain/AutoGen/CrewAI, or import from existing automation tools.
Guides installation of gitagent and creation of first agent with scaffolding, configuration, and validation. Use when the user is new to gitagent, asks how to get started, wants to install gitagent, set up their first agent, or says 'how do I start?'
Semantic search over ingested documents using RAG (LlamaIndex/ChromaDB or Foundational RAG)
Searches the SkillsMP registry, installs skills locally or globally, creates custom skills with SKILL.md frontmatter, and manages the skill lifecycle. Use when the user wants to find skills, add new capabilities, install a skill, browse available skills, create a custom skill, or manage the skills system.