Scope

Reviewed local session and memory evidence under C:\Users\SAguiar\.codex, active local Codex skills under C:\Users\SAguiar\.codex\skills, visible project SKILL.md files under C:\Users\SAguiar\Documents\Projects, visible Claude scheduled skill prompts under C:\Users\SAguiar\Documents\Claude\Scheduled, and related SAIL Knowledge Base pages.

Sources confirmed

• SAIL Knowledge Base database page and data source: collection://13d5d9db-4588-41bc-afa9-45ce9e23e56c
• Skills scheduled mirror sync page: Session Export — skills-scheduled-mirror-sync (2026-05-12)
• Automation post-run QA scheduler collision standard: Session Export: automation-post-run-qa scheduler collision standard - 2026-05-13
• File-organizer shared backup index page: Session Export: Server-host shared backup file-organizer index (2026-04-28)
• Litify Skills Stack index: Litify Skills Stack — Index (11 skills)
• Google Ads Safe Access Preflight page: Google Ads Safe Access Preflight (2026-05-11)
• SEO Workflow Hardening page: SEO Workflow Hardening 2026-04-24 - QA + Remote Scaffold

Recommended skill work

1. Create or promote a sail-kb-session-export / notion-session-export skill for Codex. This should fetch the SAIL KB schema, use the minimal-safe property set first, retry compactly on validation failures, write local fallback markdown when Notion fails, and include A/B/C/D pending approvals.
2. Promote scheduler-collision-checker into an installed Codex skill. The utility already exists under C:\Users\SAguiar\Documents\Codex\scheduler-collision-checker; wrapping it as a skill would make it easier for future agents to check Codex, Windows Task Scheduler, Claude mirrors, and cloud workflow schedules before editing automations.
3. Create a cloud-migration-preflight skill. It should turn recurring local workflows into remote-ready packages with .env.example, vault mapping, smoke tests, output-root fallback, GitHub Actions/worktree readiness, and retrieval tests.
4. Create a credential-vault-auditor skill. Purpose: detect inline secrets and stale token instructions in scheduled skill prompts and project files, move secrets to the approved vault location, and leave sanitized references. Do not print secrets in chat or Notion.
5. Mirror the Litify skill stack into the active Codex Windows skill root, or create a Windows bridge skill. The Notion index points to a Mac-style /Users/.../Projects/Skills location, while this Codex session only exposes the Windows .codex and .agents skill roots. Future Litify work should not rely on agents manually discovering the old path.
6. Promote WordPress/SEO deploy QA skills into Codex: wp-content-deployer, pre-publish-qa, playwright-visual-qa, and sa-template-reference. They appear in scheduled Claude workflows and project folders but were not active Codex skills in this session. seo-competitive-execution is useful, but it does not replace the deploy/visual QA skill stack.
7. Split the shared-drive workflow into small installed skills or explicit file-organizer modes: shared-drive-indexing, shared-drive-root-cleanup, and shared-drive-rollback-executor. The current file-organizer skill is strong, but repeated work shows future agents need clearer read-only versus live-change lanes.
8. Enhance google-ads-safe-access, rather than creating a replacement. Add a required overlap check against Claude scheduled Google Ads tasks, tracker-sheet health, auth-remediation checklist, and explicit confirmation that LSA accounts remain untouched.

Do not prioritize