KS
Killer-Skills

sync — how to use sync for Claude Code how to use sync for Claude Code, sync setup guide for AI agents, what is sync in session management, sync vs other session management tools, sync install for developers, sync alternative for lifecycle management, sync best practices for AI agents, sync tutorial for beginners, sync implementation for Claude Code

v1.0.0
GitHub

About this Skill

Ideal for agents like Claude Code requiring session lifecycle management with persistent memory and automated file editing Sync is a session lifecycle management skill for Claude Code, enabling persistent memory and automated file edits with features like timestamp entries and direct file reads.

Features

Direct file reads and edits for faster performance
Automated timestamp entry addition to all files
No narration or announcements, just direct execution
Runs entirely in the main thread without subagents
Uses current time formatted as HH:MM DD/MM/Y for logging
Touches every file, even if only for timestamp updates

# Core Topics

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

Quality Score

Top 5%
33
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
Cursor IDE Windsurf IDE VS Code IDE
> npx killer-skills add anombyte93/atlas-session-lifecycle/sync

Agent Capability Analysis

The sync MCP Server by anombyte93 is an open-source Categories.community integration for Claude and other AI agents, enabling seamless task automation and capability expansion. Optimized for how to use sync for Claude Code, sync setup guide for AI agents, what is sync in session management.

Ideal Agent Persona

Ideal for agents like Claude Code requiring session lifecycle management with persistent memory and automated file editing

Core Value

Empowers agents to manage sessions efficiently with direct file reads and edits, providing a faster and more reliable syncing process using timestamp entries, all while prioritizing speed over perfection

Capabilities Granted for sync MCP Server

Automating session lifecycle management
Editing files silently without user interaction
Printing summaries of sync operations

! Prerequisites & Limits

  • No support for subagents
  • No compatibility with MCP tools
  • Requires running entirely in the main thread
Project
SKILL.md
2.4 KB
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8

# Tags

[No tags]
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 summary

Print the standard sync block above, plus:

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

Related Skills

Looking for an alternative to sync or building a Categories.community AI Agent? Explore these related open-source MCP Servers.

View All

widget-generator

Logo of f
f

widget-generator is an open-source AI agent skill for creating widget plugins that are injected into prompt feeds on prompts.chat. It supports two rendering modes: standard prompt widgets using default PromptCard styling and custom render widgets built as full React components.

149.6k
0
Design

chat-sdk

Logo of lobehub
lobehub

chat-sdk is a unified TypeScript SDK for building chat bots across multiple platforms, providing a single interface for deploying bot logic.

73.0k
0
Communication

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
Communication

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
Communication