菜单
Publish a previewed Rubicon programming write batch via programming_write_publish using the confirmationToken from the preview step. Use this as stage 4 (final) of the Rubicon programming pipeline, after the coach has explicitly approved the preview.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/joelhooks/rubicon-codex-plugin --skill publish命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Transform raw Programming/Movement Source Sheet rows into Rubicon's programming write operations (create_node, patch_node, create_edge, patch_edge), applying conjugate-method coaching conventions and resolving movement IDs via movement_catalog_search. Use this as stage 2 of the Rubicon programming pipeline, after sheet-read and before preview.
Run a dry run of a Rubicon programming write batch via programming_write_dry_run to get a confirmationToken and a human-readable preview of the change before anything is published. Use this as stage 3 of the Rubicon programming pipeline, after programming-inference and before publish.
Read rows from the coach's Programming Source Sheet and/or Movement Source Sheet using gogcli, resolving the real spreadsheet ID from local plugin data instead of any hardcoded value. Use this as stage 1 of the Rubicon programming pipeline, before programming-inference.
基于 SOC 职业分类
正在显示 SKILL.md
| name | publish |
| description | Publish a previewed Rubicon programming write batch via programming_write_publish using the confirmationToken from the preview step. Use this as stage 4 (final) of the Rubicon programming pipeline, after the coach has explicitly approved the preview. |
Stage 4 of 4 in the Rubicon coach programming pipeline:
sheet-read → programming-inference → preview → publish
Input: the exact same operation batch that was sent to
programming_write_dry_run in preview, plus the confirmationToken that
call returned. Output: the operations are actually written to Rubicon.
Do not run this skill unless:
preview output and explicitly said to proceed
(e.g. "publish it", "looks good, go ahead" — not just silence).confirmationToken from
that specific preview run. If any time has passed, the coach asked for
changes, or you're unsure the batch is identical, go back to
programming-inference → preview and get a fresh token rather than
reusing an old one.programming_write_publish with:
programming_write_dry_run
call, unmodifiedconfirmationToken from that dry runprogramming_write_publish requires the programming:admin OAuth
scope. In practice this is satisfied because the coach's Rubicon account
already holds the coach role — canPublishProgramming checks the
authenticated user's role, not how the OAuth client itself was
provisioned. Ordinary Codex OAuth dynamic client registration + the
coach's own login + consent is sufficient. No special client
provisioning or pre-approval step is needed beyond the coach
authenticating as themselves.confirmationToken. This
plugin does not implement or duplicate that check — it's an existing
hard gate on the Rubicon side. If publish is rejected for a token
mismatch, do not retry with a stale token; restart from
programming-inference with the corrected operations and get a fresh
preview.This is the end of the pipeline for this batch. If the coach has more rows
to bring in (e.g. the next week, or the batch was split because of the
25-operation cap), start a fresh cycle at sheet-read or
programming-inference as appropriate — don't chain another publish off
this same token.