Autonomous Sync — Keep Your Agent Updated
SkillFiles & storageUse 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'.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Autonomous Sync — Keep Your Agent Updated skill
What this skill tells your AI
The instructions your AI receives, as published by aicoo-team/aicoo-skills in skills/autonomous-sync/SKILL.md and read by ahel’s review.
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>&1
Strategy 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.
Signals
- GitHub stars
- 35
- Forks
- 5
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
autonomous-sync- Source
- github.com/aicoo-team/aicoo-skills