{"id":18976,"plugin_id":"plugins_6a8fe5b3cef48191bf833140a688aa76","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:15:07.579Z","digest":"2f65506ce43b22b4dcef2123ebe520cf4f44d12f5d9f60f681973a56be96ea21","against":null,"payload":{"description":"Pair this Codex App or CLI installation with Trinity capture","included_files":[],"name":"trinity-connect","skill_md_contents":"---\nname: trinity-connect\ndescription: Pair this Codex App or CLI installation with Trinity capture\n---\n\nConnect this Codex installation with the short-lived pairing code the user provided.\n\n1. Resolve `<pluginRoot>` from this skill's installed path. This file is at\n   `<pluginRoot>/skills/trinity-connect/SKILL.md`; confirm that\n   `<pluginRoot>/dist/codex-connect.js` exists before continuing.\n2. Ask to run the next command outside the Codex sandbox. It needs network access to\n   exchange the code and writes the device credential under `~/.codex`; never print\n   the pairing code.\n3. Run `node \"<pluginRoot>/dist/codex-connect.js\" <pairing-code>`.\n4. Run `node \"<pluginRoot>/dist/codex-connect.js\" --status` separately. If it is\n   pending, wait one second and retry up to five times while this plugin's\n   PostToolUse hook promotes the credential into its own data directory.\n5. Report the final status output as-is. When connected, tell the user to start a\n   new Codex task so capture begins at SessionStart.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}