Create a node-local skill on a follower machine and prepare its promotion into the shared set through a gate. Use when a new skill idea appears on a peer and should not wait for the hub. Triggers: "/skill-forge <idea>".
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
The implementation of the approved design [[decision-2026-07-14-fleet-skill-autonomy-local-namespace]]:
a peer creates ITS OWN skills locally (poisoning nobody — the blast radius on others is 0),
and they reach the fleet-wide set only through a gate. While named local-* a skill lives here only
(.stignore local-*: not synced, not rolled back by receiveonly, but still loaded by the loader).
The gatekeeper: skill_guard.py in this same folder (0 LLM, stdlib only). Rails from DR26-07-14-MAC-1-01.
/skill-new (create a local skill)local-<slug>, only [a-z0-9-]. Check it:
python ~/.claude/skills/skill-forge/skill_guard.py --check-name local-<slug>~/.claude/skills/local-<slug>/SKILL.md with frontmatter:
name, description (when to invoke it), permissions: [...] (filesystem/shell/network — only what is truly needed),
risk_level (inert / shell-local / shell-networked / secret-touching / always-loaded-core / irreversible — the taxonomy from the external DR),
processes_untrusted_data: true|false, and disable-model-invocation: true for side-effecting or manual-only skills.shell without a real need; a skill with shell requires a mandatory review at promotion time.python ~/.claude/skills/skill-forge/skill_guard.py
(rail 1 collision + rail 3 sync-conflict — you learn at once whether you are shadowing a shared skill)./tt the new skill (run it live → break it → prove it) BEFORE any promotion./skill-promote (local → the fleet-wide set)The gate (approved by the owner): /tt + leak scan + collision check + risk classification + one peer opinion → route it to the writer.
A follower does NOT write the shared set itself (it is receiveonly) — it prepares a bundle and hands it to the single writer.
python ~/.claude/skills/skill-forge/skill_guard.py --leak local-<slug>
gitleaks/trufflehog on top (the /release-slice engine)./tt pass? — no ✅, no promotion.secret-touching / always-loaded-core / irreversible / it triggers Tier-2 →
the owner's gate (an ask in the approval channel); otherwise one peer opinion is enough.bus_send.py <peer> "SKILL-REVIEW: local-<slug> …" ([[peer-opinion-before-fleet-rollout]])._machine-bus/_transit/canon-proposals/ + ping the writer
(today the hub; after migration step 3, the anchor node). The writer strips the local- prefix, commits and syncs it to everyone
([[skills-rollout-all-machines-default]]). ⛔ A follower never strips local- itself — that is the writer's job.🧒 In plain words: this is a workbench for inventing your own tool at home, checking that it breaks nobody else's and hides no secret, and then handing it to the "master smith" who distributes it to everyone.
<!--kit-footer-->Like this skill? It is one of 100 in second-brain-starter-kit: the second brain we built for ourselves and run every day at Palo Alto AI Research Lab. Install the whole set with npx skills add tonydzi/second-brain-starter-kit. Everything is open source and free, so take what you need.
Flagships worth a look on their own: secondop-panel (a second opinion from a panel of external models), claude-memory-tidy (stop your agent's memory from rotting), telegram-mcp-kit (your own Telegram over MCP in about 15 minutes).
Author: Anton Dziatkovskii, Palo Alto AI Research Lab. Telegram @tonydzi - WhatsApp +1 341 222 9178 - X @Tony_Stef_
Engineers: want to test-drive this setup? Message me. I hand out free starter seeds to engineers who test and report back, and custom skill requests are welcome.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Run an autonomous consensus round between agent peers on several machines: they negotiate a decision over a shared channel and execute it without a human relaying messages. Use when multiple machines must agree on a change. Triggers: "/03", "work it out among yourselves", "find consensus". Wakes the human only for irreversible actions or a deadlock.
The English summary is being prepared. Showing the original description.
Recover a session after a hard crash (app died, machine rebooted, context lost mid-work): replay the turn-state ledger for the last requests, files and decisions, run a green/red health ping over the system map, file sync and MCP connectors, then rebuild the previous session history for pickup. Triggers: "/1", "resume after crash", "wake".
The English summary is being prepared. Showing the original description.
Show the operator's day: today's calendar plus what needs them personally (leads due, people awaiting a reply, deadlines), pulled from Calendar and Telegram and ranked. Read-only: sends and commits nothing. Triggers: "/agenda", "what's on today", "my agenda".
The English summary is being prepared. Showing the original description.
Rewrite machine-written text so it reads like a busy human wrote it: cut 50-70%, break the even rhythm, drop AI-tell words and filler, keep facts and protected terms. Use before publishing any post, reply or email drafted by a model. Triggers: /ai-slop, /slop, humanize, anti-slop, make it shorter and alive.
The English summary is being prepared. Showing the original description.
Decision protocol for strategic work: recall the knowledge vault, run a gap analysis, emit a deep-research prompt for external tools, then synthesize the returned reports into a decision memo. Use before any new product, feature, market, pricing, GTM or architecture call, where local recall alone is not enough. Triggers: "/alfa-search-recall-deepresearch", "alpha protocol", "R+DR".
The English summary is being prepared. Showing the original description.
- КРЕДИТ АВТОРУ ИДЕИ: совет из комментария (TG @ClawRus / @ClawInga, комменты под постами Антона в FB, треды и issue на… Триггеры: “/alpha-credit“, “/credit“, “кто нам это посоветовал“, “запиши совет“, “поблагодари советчиков“, “кому мы должны спасибо“, “кредит автору“, “чей это был совет“, “credit the author“
The English summary is being prepared. Showing the original description.