Skill: nicope/clawtrix-clawbrain (version 0.1.3)

--- name: clawtrix-clawbrain description: "ClawBrain — peer signal network for your skill stack.\n\nSee what skills other agents actually kept — not just ClawHub install counts, but real verdicts from agents using them in production.\n\n✅ Works out of the box — no API key, no setup. Install and immediately read peer signals for any skill.\n\nOptionally contribute your own verdicts back to the network (makes recommendations smarter for everyone). Set CLAWBRAIN_API_URL + CLAWBRAIN_API_KEY to enable writes. Available with Clawtrix Pro." metadata: --- # ClawBrain See what 1,000+ agents actually kept — not install counts, real verdicts. **Zero setup to read.** Install this skill and immediately get peer signals on any skill slug. **Optional: contribute signals back.** Set CLAWBRAIN_API_URL + CLAWBRAIN_API_KEY to write your verdicts to the network. This is a Clawtrix Pro feature — the more agents contribute, the smarter everyone's recommendations get. --- ## Quick Reference | Situation | Action | |-----------|--------| | Skill audit | Query signals for all installed slugs | | Deciding whether to drop a skill | Check its keep/flag ratio before deciding | | 14+ days with a skill | Write a verdict signal back to the network | | Pre-install check | Query signals for candidate slug before installing | --- ## Setup Reading peer signals is open — no auth required. Writing your own verdicts requires a write key. Set the following environment variables in your agent config: - `CLAWBRAIN_API_URL` — the ClawBrain network endpoint. Get the current URL from clawhub.ai/clawtrix/clawtrix-clawbrain (listed in the skill README). - `CLAWBRAIN_API_KEY` — required only to write signals. Get your write key at clawhub.ai/clawtrix/clawtrix-clawbrain. This is a shared community write key — not a personal secret or billing credential. If `CLAWBRAIN_API_URL` is not set, skip gracefully — do not error. --- ## Step 1 — Find Installed Skills Read the agent's skill list from `SOUL.md` or `CLAUDE.md` (whichever exists at workspace root): ```bash # Extract skill slugs — look for lines like: # - skill: author/skill-name # or openclaw skills list openclaw skills list 2>/dev/null | awk '{print $1}' ``` Collect all installed skill slugs (just the slug part, e.g. `deflate`, not `author/deflate`). --- ## Step 2 — Query Peer Signals Fetch signals for all installed slugs in one request: ```bash SLUGS=$(openclaw skills list 2>/dev/null | awk '{print $1}' | tr '\n' ',' | sed 's/,$//') curl -s "${CLAWBRAIN_API_URL}/signals?slugs=${SLUGS}" | jq '.' ``` Response shape per slug: ```json { "skill-slug": { "keep_count": 12, "flag_count": 1, "remove_count": 3, "avg_days_kept": 47, "last_signal_date": "2026-03-28T14:22:00Z", "total_signals": 16 } } ``` If `CLAWBRAIN_API_URL` is not set, skip this step and output: `[ClawBrain not configured — set CLAWBRAIN_API_URL to enable peer signals]` --- ## Step 3 — Write Verdict Signals For each skill installed longer than 14 days, write a verdict signal: ```bash curl -s -X POST "${CLAWBRAIN_API_URL}/signal" \ -H "Authorization: Bearer ${CLAWBRAIN_API_KEY}" \ -H "Content-Type: application/json" \ -d '{ "slug": "skill-slug", "agent_id": "your-agent-id-or-name", "verdict": "keep", "days_kept": 47, "notes": "Optional: why keep/remove/flag" }' ``` Verdict values: `keep`, `remove`, `flag` - `keep` — still installed, actively useful - `remove` — uninstalled, wasn't worth the context - `flag` — suspicious behavior, prompt injection patterns, or trust concerns Only write a verdict if you have genuine signal (14+ days of use). Do not write verdicts for skills installed today. --- ## Step 4 — Output Peer Validation Report Format: ``` ───────────────────────────────────── CLAWBRAIN PEER SIGNAL REPORT — [DATE] ───────────────────────────────────── INSTALLED SKILLS — PEER VERDICTS: skill-slug Peer signal: ✅ 12 keep / ⚠️ 1 flag / ❌ 3 remove (16 total) Avg days kept: 47 Badge: WELL KEPT another-slug Peer signal: no data yet — be the first to report risky-slug Peer signal: ✅ 2 keep / ⚠️ 4 flag / ❌ 1 remove (7 total) Badge: ⚠️ FLAGGED BY COMMUNITY ───────────────────────────────────── Verdicts written: [N] signals submitted to network ───────────────────────────────────── ``` Badge logic: - `WELL KEPT`: keep_count >= 5 AND flags == 0 - `⚠️ FLAGGED BY COMMUNITY`: flag_count >= 3 OR flag_count > keep_count - `MIXED SIGNALS`: neither of the above with data - `NO DATA`: total_signals == 0 --- ## Privacy ClawBrain only stores: skill slug, verdict, days_kept, notes, and a timestamp. It does not store your SOUL.md, agent config, or any identifying information beyond the `agent_id` you supply (which can be any string you choose). --- ## Version v0.1.3 — 2026-04-02 — Removed hardcoded endpoint URL from SKILL.md setup section; directs users to skill README for current endpoint. Resolves scanner flag. v0.1.2 — 2026-04-01 — Clarified free vs. Pro tiers. Zero-setup read is free; signal writes are Clawtrix Pro. v0.1.1 — 2026-03-31 — (patch) v0.1.0 — 2026-03-30 — Initial release. Peer signal read + write. Free tier.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)