Menú
Check system status — repos, services, containers, APIs. Use when you need to verify system health or diagnose issues.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | system-check |
| description | Check system status — repos, services, containers, APIs. Use when you need to verify system health or diagnose issues. |
Run diagnostics on your system components. Adapt the commands to your infrastructure.
curl -s --max-time 5 "http://${DND_VPS_IP:-localhost}:${DND_VPS_PORT:-3002}/api/status" \
-H "X-Auth-Token: ${DND_API_TOKEN}"
# Check if your main service is running
systemctl is-active ${DND_SERVICE_NAME:-my-service} 2>/dev/null || echo "Service not found"
docker ps --filter "name=${DND_CONTAINER_NAME:-my-container}" --format "{{.Names}}: {{.Status}}"
docker logs ${DND_CONTAINER_NAME:-my-container} --tail 20 2>&1
Configure these in your .env or shell profile:
DND_VPS_IP — your server IP (default: localhost)DND_VPS_PORT — API port (default: 3002)DND_API_TOKEN — authentication tokenDND_CONTAINER_NAME — Docker container nameDND_SERVICE_NAME — systemd service name$ARGUMENTS
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.