sync — community atlas-session-lifecycle, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Ideal for Claude Code Agents requiring efficient session lifecycle management with persistent memory and file editing capabilities. Session lifecycle management for Claude Code — persistent memory, soul purpose, reconcile, harvest, archive

anombyte93 anombyte93
[0]
[0]
Updated: 3/5/2026

Agent Capability Analysis

The sync skill by anombyte93 is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance.

Ideal Agent Persona

Ideal for Claude Code Agents requiring efficient session lifecycle management with persistent memory and file editing capabilities.

Core Value

Empowers agents to perform rapid file synchronization, utilizing direct file reads and edits, while prioritizing speed over perfection and maintaining a timestamp entry for every file, all within the main thread and without relying on MCP tools or subagents.

Capabilities Granted for sync

Editing files silently without user prompts
Printing summaries of synchronized data
Archiving files with updated timestamps

! Prerequisites & Limits

  • No support for subagents or MCP tools
  • Requires direct file system access
  • Operates solely in the main thread
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

sync

Install sync, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly

Sync

Zero questions. Edit files. Print summary. Done.

Rules

  1. No questions — never ask the user anything. Just save.
  2. No subagents — run entirely in the main thread.
  3. No MCP tools — direct file reads and edits only (faster).
  4. No narration — don't announce steps. Just do them.
  5. Touch every file — even if only adding a timestamp entry.
  6. Speed over perfection — a rough sync beats no sync.

Execute

Use the current time formatted as HH:MM DD/MM/YY for the checkpoint header.

1. Edit session-context/CLAUDE-activeContext.md

Append a new section at the end:

markdown
1## [SYNC] {time} 2 3**Accomplished:** 4- {bullet list of what was done this session} 5 6**In progress:** 7- {what's currently being worked on} 8 9**Next steps:** 10- {what comes next} 11 12**Blockers:** 13- {any blockers, or "None"}

2. Edit session-context/CLAUDE-decisions.md

Append new decisions made this session. If none, append:

markdown
1## {time} 2No new decisions this session.

3. Edit session-context/CLAUDE-patterns.md

Append new patterns discovered. If none, append:

markdown
1## {time} 2No new patterns this session.

4. Edit session-context/CLAUDE-troubleshooting.md

Append new issues and solutions. If none, append:

markdown
1## {time} 2No new issues this session.

5. Update MEMORY.md

Update the auto-memory file at the project memory path with any new learnings from this session. If nothing new, skip this file (memory should stay concise).

6. Print summary

Print exactly one block:

Synced. {N} files updated.
- Active context: {1-line summary of what was captured}
- Decisions: {count new or "no new"}
- Patterns: {count new or "no new"}
- Troubleshooting: {count new or "no new"}
- Memory: {updated or "no changes"}

/sync --full (Capability Inventory)

Extended sync that includes capability inventory generation.

Execute

  1. Run standard sync flow (Steps 1-5 above).
  2. Call session_capability_inventory(project_dir, force_refresh=True) — bypasses cache and regenerates inventory even if git unchanged.
  3. If needs_generation == True: the MCP tool will generate the inventory.
  4. Read CLAUDE-capability-inventory.md if it exists.

Print the standard sync block above, plus:

Capability Inventory: {status}
- MCP Tools: {count}
- Test Coverage: {percentage}
- Critical Untested: {count}
- Inventory: {path}

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is sync?

Ideal for Claude Code Agents requiring efficient session lifecycle management with persistent memory and file editing capabilities. Session lifecycle management for Claude Code — persistent memory, soul purpose, reconcile, harvest, archive

How do I install sync?

Run the command: npx killer-skills add anombyte93/atlas-session-lifecycle/sync. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for sync?

Key use cases include: Editing files silently without user prompts, Printing summaries of synchronized data, Archiving files with updated timestamps.

Which IDEs are compatible with sync?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for sync?

No support for subagents or MCP tools. Requires direct file system access. Operates solely in the main thread.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add anombyte93/atlas-session-lifecycle/sync. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use sync immediately in the current project.

Related Skills

Looking for an alternative to sync or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

149.6k
0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

138.4k
0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI