Triage a lead pipeline and say who needs action today: replied means send the scheduling link, link sent 24h ago without a booking means nudge, awaiting reply means check inbound, going cold means follow up, booked means close out. Ranked and draft-first, so the owner edits before anything goes out. Triggers: "/pipeline", "work my leads", "who is stuck in the funnel".
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
🧒 When reporting to a non-technical operator: end with a child-simple "In plain words" recap in their language. NEVER inside lead messages. 📖 Operates under the
bibleskill — outreach codex_Bible-Outreach-MOC. Outbound = send-direct (the operator 2026-06-16 — they edit the sent message after); NO mass auto-blast (pace + personalize per lead). Money / commitments / credentials → escalate.
python "$IMPORTS_ROOT/build_pipeline_dashboard.py" → open $OBSIDIAN_VAULT/_Dashboards/Pipeline-Dashboard.html: a kanban by stage (🔥 replied → ⏰ nudge → ⏳ booked → 👀 waiting → ✅ done) + ready drafts (click = copy). View only, it sends nothing. The text walkthrough below is for the actions themselves (send-direct, the operator edits after the fact).
Read $IMPORTS_ROOT/tg_followups.json (the watcher's live state). Each pending[] lead: lead, chat_id, username, pitch_sent, calendly_sent, replied, booked, booking_confirmed, + a check instruction. Plus calendly_sent_at (for the 24h nudge) and booking_nudge_rule.
Deeper history per lead: 04-Projects\crypto\Platinum-CRM\_Platinum-CRM-MOC.md + its lead cards, or /ask --leads "<name>".
replied set, calendly_sent:false) → draft calendly_text to that chat. Warm NOW = top priority.calendly_sent:true, no booking_confirmed, calendly_sent_at >24h ago) → draft booking_nudge_text (leads forget to book — standing rule).pitch_sent:true, no replied) → run the lead's check: read recent messages of chat_id (Telegram MCP; see telegram-howto) for a NEW inbound (sender ≠ Tony) after our pitch. If replied → it becomes case 1.pending. Never re-pitch.tg_followups.json (calendly_sent, booking_confirmed, booking_nudge_sent…) so state stays true.tg_followups.json is empty/stale → say so; offer to rebuild from recent Telegram via telegram-lead-outreach ("find + capture").Like this skill? It is part of 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.