Rewrote the litify-knowledge-center skill to remove drift risk. The prior version hardcoded five absolute /Users/samaguiar/... paths as the definitive source for its architecture docs, migration assessments, rollout packages, and Python scripts. Those paths fail the moment files move, and they fail for any agent running in a fresh Cowork container or on another device.
Verified during the rewrite:
samaguiar1982-cpu/sail-litify exists (default branch main, private).docs/ and force-app/ sit at the repo root, with no Litify_AI_Integration_Project wrapper folder.knowledge-center-* docs the old skill pointed to are not in sail-litify/docs/ on GitHub (only one HANDOFF file is there). So the old skill had no network fallback at all.The new skill:
litify-operator-core instead of duplicating paths.$SAIL_LITIFY_REPO env var, then the conventional local checkout (probed, not assumed), then the GitHub remote. It never quits on a missing path.Knowledge__c grounding via litify-live-recon.github-direct-commit plus the three-mode handoff.Delivered as an installable .skill file plus a plain SKILL.md copy (links were provided in the chat).
Work complete. The rewrite shipped and passed QA. The remaining items are decisions for Sam, not blockers.
.skill. It preserves the exact litify-knowledge-center name, so it replaces the current read-only copy cleanly.