# Intelligence Sync

> Sync intelligence to enabled adapters

- Skill: `ainova-systems/intelligence-sync` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ainova-systems/intelligence-sync`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ainova-systems/intelligence-sync/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ainova-systems (https://skillmd.com/u/ainova-systems)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ainova-systems/intelligence-sync

---


# Sync intelligence

1. Run `intelligence sync` (or `intelligence sync <adapter>` when one adapter
   was requested). For Intelligence projects, this command first aligns project schema/content
   with the installed CLI and restores a missing package store strictly from
   `intelligence.lock`.
2. Require final `IS_STATUS=ok`; relay per-adapter counts and any integrity,
   model-drift or unsynced-source warnings.
3. In CI, a required tracked project upgrade is intentionally refused. Report
   the instruction to run `intelligence init --apply` locally, review and
   commit its diff; never bypass the gate. A frozen restore refusal means the
   manifest and lock disagree or the locked commit cannot be verified/restored—report it without
   hand-copying package content.
4. On a probable Intelligence defect, first ask whether to collect a sanitized
   issue draft; collect nothing before approval and never use telemetry. Include
   only approved CLI/version, expected/actual behavior, and safe error details—
   no confidential or project-specific data. Show the draft and obtain separate
   approval before filing. If declined, ask whether the opt-out is for this
   session, a user/gitignored dev-project profile, or a shared team policy; save
   it only with separate approval. Put team policy in a project-owned rule, and
   never invent a profile path or infer the intended scope.