Read the system-architect map: a deterministic catalog of everything the setup is made of (vault, import scripts, scheduled tasks, MCP servers, SQLite databases, hooks, skills, dashboards), what is healthy and what fell off. Consult it before changing shared infrastructure and re-scan after. Triggers: "/arch", "/arch broken", "/arch scan", "what broke in the system".
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
One place that knows what the system is made of, what is healthy, what fell over — and tests it. Deterministic, 0 tokens, READ-ONLY. This is RECALL for the infrastructure layer: look BEFORE changing shared infrastructure, rescan AFTER.
Engine: $IMPORTS_ROOT/arch/ (git-backed in _imports). The source of truth is system.db (built by the nightly scan at 05:45). Dashboard _Dashboards\System-Health.html, MOC 00-System\_System-MOC.md, auto-inventory 00-System\System-Automations.md (replaces the manual [[automation-inventory]]).
# status (default) — health summary + score
python "$IMPORTS_ROOT/arch/arch_status.py"
# only what is broken / red
python "$IMPORTS_ROOT/arch/arch_status.py" broken
# dead code — scripts wired to nothing
python "$IMPORTS_ROOT/arch/arch_status.py" dead
/arch → arch_status.py (status)./arch broken → arch_status.py broken./arch dead → arch_status.py dead./arch scan (force a fresh scan, AFTER an infrastructure change) → rebuild the catalog:
cd /d $IMPORTS_ROOT/arch
python sys_scan.py && python sys_coverage.py && python build_system_docs.py && python build_arch_map.py && python sys_check.py
run_architect.cmd pipeline minus the final vault_backup.py. The full nightly run = run_architect.cmd, scheduled task "System Architect Nightly" at 05:45.)_imports script, an MCP, a DB, a hook, a skill, a pipeline) → /arch / /arch broken: what exists and what depends on it — will I break a neighbour?/arch scan, so the map does not fall behind reality.result!=0 on a task does not always mean "broken" (a benign lock collision happens — check the source). Never delete an active/critical asset before understanding its dependencies.RED.flag is written only on critical/daily failures (SRE style: alert on the symptom). The phase-5 routine system-architect-red-alert (06:21) pings Telegram Saved Messages when red and stays silent when green.Memory [[system-architect]] · decision decision-architect-system-platform · the Bible rule "check the map before changing the system" (for human assistants and LLMs alike). Related: [[verify-existing-before-proposing]], [[automation-inventory]], [[vault-data-architecture]].
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.