autonomous-sync
Skill35 starsChanged 4 months agoMITView on GitHub
Use this skill when the user wants to keep their Aicoo agent updated automatically, set up scheduled syncs, configure triggers for knowledge updates, use CRON jobs, /loop commands, file watchers, or hooks to push changes to Aicoo. Triggers on: 'auto sync', 'keep updated', 'schedule', 'CRON', 'loop', 'trigger', 'watch files', 'auto update', 'periodic sync', 'hook', 'autonomous'.
- Reads credentials
- Sends data out
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- aicooSkill
- build-memorySkill
- check-messagesSkill
- compile-identitySkill
- connect-local-agentSkill
- context-syncSkill
- daily-briefSkill
- discoverSkill
- examine-sandboxSkill
- group-chatSkill
- heartbeatSkill
- inbox-monitoringSkill
- invite-teamSkill
- onboardingSkill
- raw-memorySkill
- share-agentSkill
- snapshotsSkill
- squareSkill
- start-aicooSkill
- talk-to-agentSkill
- todosSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Use these endpoints in automation:
- Very specific: line 22
Create new note: POST /api/v1/os/notes
- Distinctive: line 67
After substantial chat sessions:
- Very specific: line 89
If no matching note exists, call POST /os/notes.
- Distinctive: line 101
Search first to avoid duplicates.
- Distinctive: line 103
Prefer patching canonical notes over creating near-duplicates.
- Distinctive: line 104
Use accumulate for larger batches.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Autonomous Sync — Keep Your Agent Updated
Set up automatic triggers to keep Aicoo knowledge current.
Prerequisites
AICOO_API_KEYmust be set- Base URL:
https://www.aicoo.io/api/v1
Sync Contract (post-refactor)
Use these endpoints in automation:
- Search overlap:
POST /api/v1/os/notes/search - Deterministic grep (exact/regex + context):
POST /api/v1/os/notes/grep - Snapshot before edits:
POST /api/v1/os/snapshots/{noteId} - Edit existing note:
PATCH /api/v1/os/notes/{noteId} - Create new note:
POST /api/v1/os/notes - Reorganize with move/copy:
POST /api/v1/os/notes/{id}/move,POST /api/v1/os/notes/{id}/copy - Bulk updates:
POST /api/v1/accumulate
Strategy 1: Rule-Based (/loop or cron)
Claude Code /loop
/loop 30m sync new decisions and project updates to Aicoo: search existing notes, snapshot before major edits, patch existing notes or create new ones.Cron example
# daily at 9:00
0 9 * * * /path/to/aicoo-sync.sh >> /tmp/aicoo-sync.log 2>&1Strategy 2: Event-Driven (hooks)
Claude hooks
Add to .claude/settings.json:
{
"hooks": {
"PostToolUse": [
{
"matcher": "Write|Edit",
"hooks": [
{
"type": "command",
"command": "./aicoo-skills/scripts/sync-detector.sh"
}
]
}
]
}
}Strategy 3: Conversation-Driven
After substantial chat sessions:
# 1) search
curl -s -X POST "$PULSE_BASE/os/notes/search" \
-H "Authorization: Bearer $AICOO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"database migration strategy"}' | jq .
# 2) snapshot before overwrite
curl -s -X POST "$PULSE_BASE/os/snapshots/42" \
-H "Authorization: Bearer $AICOO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"label":"Pre-update"}' | jq .
# 3) patch
curl -s -X PATCH "$PULSE_BASE/os/notes/42" \
-H "Authorization: Bearer $AICOO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"content":"# Updated content..."}' | jq .If no matching note exists, call POST /os/notes.
What to Sync
- decisions
- preferences
- project updates
- meeting outcomes
- policy/constraint changes
Safety Rules
- Search first to avoid duplicates.
- Snapshot before high-impact edits.
- Prefer patching canonical notes over creating near-duplicates.
- Use accumulate for larger batches.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

