skills.rest
sanskarbasnet
sanskarbasnetCOMMUNITY
Explore all skills by this author →
GitHub

sync

Run fstack-brain sync to display live agent status, intents, handoffs, and recent decisions.

1|Updated May 4, 2026
Search Tags:#sync#claude-code#handoffs#intents#teammates#mult-agent#brain-digest
One-click install
npx skills add https://github.com/sanskarbasnet/fstack --skill sync-sanskarbasnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/sanskarbasnet/fstack/tree/main/sync
Command: npx skills add https://github.com/sanskarbasnet/fstack --skill sync-sanskarbasnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull the latest fstack brain digest — what other agents are doing right now, active intents, open handoffs addressed to you, and recent decisions. Auto-fires at SessionStart via hook. Use manually whenever you want a fresh snapshot.

Core Features & Use Cases

  • Runs fstack-brain sync and shows the digest:
  • Other agents currently live (heartbeat within 5 min)
  • Other agents' open intents on this repo
  • Handoffs addressed to you (or to anyone, unclaimed)
  • The 5 most recent decisions logged in this repo This is the cheapest possible "morning standup." It costs one DB round-trip and gives you everything you need to not collide with the other agent.

Quick Start

Run the fstack-brain sync command to display the latest digest.

Frequently Asked Questions about sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a real-time brain digest of teammate activity in a multi-agent coding environment?▼

You can track teammate agent activity by pulling a brain digest that aggregates live agent status, open intents, and handoffs. This snapshot costs a single database round-trip and summarizes the five most recent decisions logged in your repository.

What is the best way to prevent coding conflicts with other agents working on the same repository?▼

Preventing conflicts requires pulling a brain digest to view other agents' open intents and live heartbeats. By checking active handoffs addressed to you and recent decisions, you can stay aware of potential collisions before making changes to the shared repository.

How do I check for open handoffs addressed to my agent in a collaborative coding session?▼

Checking for open handoffs involves pulling the latest brain digest, which explicitly lists unclaimed handoffs and those addressed to your current session. This ensures you receive pending tasks and context from other agents working on the same repository.

Does the agent brain digest automatically update when a new collaborative coding session starts?▼

The brain digest automatically updates by firing a sync command at SessionStart via a configured hook. This ensures you immediately see live agent status, open intents, and recent decisions without needing to manually trigger the digest at the beginning of your work.

Can I see what intents other agents have on my repository without performing a heavy database query?▼

Viewing other agents' open intents requires only a single database round-trip to pull the brain digest. This efficient operation aggregates live agent status, unclaimed handoffs, and the five most recent decisions, providing a quick snapshot without heavy database queries.

Related Skills

Explore More Software Engineering Skills→
potpie-aipotpie-ai
5.6k

potpie-repo-baseline

Analyze a local repository to capture its purpose, features, services, and dependencies.

Official
Advanced
SethyPagnaSethyPagna

kanban-worker

Clarify ambiguous kanban worker handoffs, retries, and completion decisions.

Community
Advanced
jscott3201jscott3201
2

agent-bridge

Coordinate multiple agents to prevent conflicting edits on shared project files.

Community
Advanced
anthropicsanthropics
23.4k

standup

Aggregate commits, PRs, and ticket updates into daily standup reports.

Official
Intermediate