Menu
Knowledge propagation engine. Knows what goes where when something changes. Use after any significant change to ensure all downstream targets are updated.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Business, outreach and public-relations manager for AI projects and technical teams. Use when an agent must turn a collaboration opportunity, partner request, portfolio update, public claim, outreach message, follow-up, sponsorship path or service proposal into a bounded decision, safe communication package and tracked next action without sending or publishing autonomously.
Deploy paper content from configured site_ready files to d-nd.com VPS. Handles md-to-HTML conversion, bilingual merge, figure path resolution, and pages.json update.
Five mechanical gates for any content publish pipeline with CMS + rendering layers. Prevents false security: 'API returned 200' does not mean 'visitor sees clean content'. Use when writing content to a multi-layer serving system (CMS API, static files, prerendered HTML, cached copies).
Multi-node consultation protocol for high-leverage decisions. Dispatches the same question to N independent LLM/agent nodes in isolation, then synthesizes their responses into a summa that exposes convergence (high-confidence claims), dissensus (real uncertainty zones), and emergent points (insights no single node produced). Reduces single-node training bias. Supports recursive escalation for stable-state convergence. Use for decisions that propagate via A14 cascade — seed updates, crystallizations, advisory→mechanical promotions, high-visibility copy, lab result interpretation.
Closure reflection protocol. After a significant work block concludes (feature shipped, session ending, major commit landed, cross-node coordination resolved), runs a 10-question interview that extracts meaning, impact, and next questions — then emits multiple audience-specific artifacts (changelog, external editorial, AI integration docs, memory crystal, backlog seed). Turns implicit maturation into explicit narrative. Use at the end of meaningful work, not after trivial edits.
Pre-commit check for public-facing copy (knowledge base definitions, page content, docs). Detects apologetic hedging — phrases that declare 'degrees of truth' (possible/necessary, current/future, one-of-many/the) and open a dualistic framing the model transcends. Use when drafting or reviewing any copy that describes the model, its transductions, or its tools.
| name | propagator |
| description | Knowledge propagation engine. Knows what goes where when something changes. Use after any significant change to ensure all downstream targets are updated. |
When a change happens in one part of the system, this skill ensures all downstream targets are updated.
# Sync updated skills to the seed repository for distribution
cd "${DND_PROJECT_DIR}" && bash d-nd-seed/scripts/sync_from_thia.sh
After sync: check diff, commit, push, notify other nodes.
# Build and deploy site changes
cd "${DND_PROJECT_DIR}/site" && npm run build
# Deploy via your mechanism (scp, rsync, webhook, CI/CD)
# After pushing to the seed repo, notify other nodes
curl -s -X POST "http://${DND_VPS_IP}:${DND_VPS_PORT:-3002}/api/node-sync" \
-H "Content-Type: application/json" \
-H "X-Auth-Token: ${DND_API_TOKEN}" \
-d '{"from":"'${DND_NODE_ID}'","to":"ALL","type":"info","content":"Seed updated. Run git pull to get latest."}'
# Deploy runtime changes to your server
# Adapt to your infrastructure (Docker, systemd, PM2, etc.)
git pull && docker cp . ${DND_CONTAINER_NAME}:/app/ && docker restart ${DND_CONTAINER_NAME}
After ANY significant change, ask:
Do NOT propagate without verification:
$ARGUMENTS