Edited the litify-integration-ops skill (your request), using skill-creator as the method and the SAIL Knowledge Base as the grounding source, reading entries newest-first. The old skill treated Dialpad as a current integration and hardcoded absolute Mac paths, both of which are now wrong.
main)One atomic commit to samaguiar1982-cpu/sail-projects-root, three files:
Skills/litify-integration-ops/SKILL.md rewritten.Skills/SKILL-INDEX.md index entry updated to match.Skills/LITIFY-SKILLS.md router row updated to match.Commit: 28fc61f418201654af348c61ffe3a0017b1ac9cb
Rollback (prior commit): 275545e6e60f9f0cdc06ddbe046ea0c0b38900cd
migrate-dialpad-call-summaries-to-litify-notes.mjs (2026-05-30). Now documented as historical-only with the explicit rule: do not delete legacy Dialpad / SMS Magic / iframe records (per the RingCentral KC guide).SAIL_Call_Log__c is the firm-built RingCentral/RingSense log (full field list captured, including Platform__c, Direction__c, Intake__c, Matter__c, Summary__c, Score__c, Related_Task_ID__c; no Agent__c/User__c). litify_pm__lit_Note__c holds RingSense and migrated summaries (CreatedDate createable-not-updateable, idempotent via External_Id__c). CallRail_Call_Log__c is marketing/attribution, linked to Intake only at row-creation time with no retro backfill (2026-05-28 GLS root cause). Knowledge__c holds staff guides.InefficientFilter gotcha noted./Users/... absolute paths; replaced with Notion KB + litify-live-recon grounding so the skill does not break when files move.litify-metadata-builder, which does not exist. Now routes to litify-flow-builder, litify-live-recon, and litify-knowledge-center.YAML frontmatter parses cleanly (caught and fixed an unquoted-colon bug before commit). Zero em/en dashes in the files I authored. No absolute paths remain. Live readback from main matches the intended content byte-for-byte.
The task is complete and verified. I stopped before propagating the change to other surfaces (the read-only Cowork /mnt/skills/user mirror and any other skill repos) because that depends on how your skill-sync direction is wired, and I did not want to step on another agent's mirror job.
The canonical copy of this skill lives at sail-projects-root/Skills/litify-integration-ops/SKILL.md (not sail-skills, which carries a different 17-skill set). If a sync normally runs repo -> Cowork, this change will propagate on the next run and nothing else is needed. If sync runs the other direction, the repo edit could be overwritten by the unchanged Cowork copy, so the same edit may need to be applied at the source. The exact 3-file diff and downloadable copies were delivered inline in the chat. A natural follow-on is a quick audit of the other litify-* skills for the same two issues (stale Dialpad-as-current framing and hardcoded /Users paths), since they likely share the pattern.