orgx-runtime-reporting
Use when a Codex execution should report progress, artifacts, blockers, or completion state back to OrgX during a live task.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- orgx-runtime-reporting
- description
- Use when a Codex execution should report progress, artifacts, blockers, or completion state back to OrgX during a live task.
03 SKILL.md 正文
OrgX Runtime Reporting
Use this skill when Codex should keep OrgX updated during execution within the user's authorized tracking scope. Reporting is not a prerequisite for local work, PR updates, or an authorized merge. Reuse prior authorization; do not ask again for each milestone. If reporting is unavailable, keep useful evidence locally, continue independent work, and describe the tracking gap once.
Reporting contract
This plugin requests the explicit commander runtime profile. Verify its
actual callable tools before using a name below. If the inventory mismatches,
refresh the connection or report the mismatch; do not guess an alias. Condensed
orgx_submit_receipt reporting and portable orgx_submit_work_receipt document
import have different schemas and semantics. Migrate the payload before changing
tools. Gateway terminal delivery and passive hook reporting use separate paths.
There are two reporting paths:
- Active path: call OrgX MCP tools during the work when you know the initiative, task, decision, blocker, or artifact context.
- Chronicle readout: for operator reporting, call
get_operator_chroniclefirst when available and presentchronicle.reportingNarrative.briefMarkdownbefore drilling into individual entities. - Stale-client fallback: if bootstrap or docs advertise
get_operator_chroniclebut the current AI client session has not refreshed its callable tool list, callorgx_recommendonly when that name is present in the actual callable list, withmode: "morning_brief", and present the returnedchronicle.reportingNarrative.briefMarkdown. Do not ask the user to reconnect before giving the report. - Passive backstop: Codex runtime hooks installed by
orgx-wizard hooks installrecord compact session events and run summary-only local Work Graph reconciliation onStop.
Do not treat hook presence as a substitute for intentional OrgX writes. Hooks answer whether OrgX was used and can write a local report automatically; MCP calls, or an explicitly opted-in successful Work Graph post, make the work durable in OrgX while the session is still fresh.
Workflow
- Resolve available IDs from args, env, or the current OrgX context:
ORGX_INITIATIVE_IDORGX_WORKSTREAM_IDORGX_TASK_IDORGX_RUN_IDORGX_CORRELATION_ID
- For reporting questions, retrieve the operator chronicle:
- Use
get_operator_chroniclewithperiod: "30d"for broad clarity when it is callable in the current client. - Use
period: "day"orperiod: "week"when the user asks for yesterday or this week. - If
get_operator_chronicleis not callable in the current client, use the existingorgx_recommendfallback when callable, withmode: "morning_brief"and the broadest supported period. Treat the direct tool as preferred, but do not block on client schema refresh. - Lead with
chronicle.reportingNarrative.briefMarkdownfor either reporting tool, then call out gaps and the next action.
- Emit activity at meaningful milestones:
intentexecutionhandoffblockedcompleted
- Register proof of work:
- Register useful evidence at meaningful milestones with a concrete summary; batch related files rather than treating every edit as a separate artifact.
- For a user-requested output attachment, use the existing
orgx_update_workwhen it is callable in the current connection. Inspect the current OrgX work target first. Supply its persistedtype,id,workspace_id, a stableidempotency_key, and oneartifact; omitfieldsfor this call. - The artifact takes
name, registeredartifact_type,locationcontaining exactly oneartifact_urlorexternal_url, optionaldescriptionandpreview_markdown, and optionaloutput_front_door. A local path is not an uploaded durable output. The front door contains a plainanswer, at most three existingdecisionIdreferences withquestion,recommendationandimpact, and producer-reportedchecked/notCheckednotes. - Context state, run cost, evaluator scores and client acceptance come from server records. Do not submit them as producer authority. If OrgX context could not load, say so before the plan and do not assume workspace team, budget, brand or open work.
- Reuse the exact payload and key after an ambiguous attachment failure.
Deliberately revised output gets a new key. Require a stored artifact UUID
in the response, then inspect it with
orgx_inspectand present the canonical output summary and review link. Attachment does not approve or complete work. - A connection without this admitted operation needs a matching MCP deployment and inventory refresh. Keep the output available and report the exact gap; never guess an alias or claim that a local receipt proved attachment.
- Handle blockers structurally:
- If an unresolved choice requires human authority, request a decision with explicit options. Routine implementation choices and actions already authorized do not need a new approval.
- Report the work that depends on a pending human decision as waiting with the
decision's
review_url.orgx_decideapprove/reject only returns that link; never report a decision as approved or rejected yourself. Continue work that does not depend on that decision. - If context is missing, report the exact missing dependency.
- Close execution cleanly:
- When the task is complete and verified, emit completion activity and update entity state if the task ID is available.
- If no OrgX IDs are available:
- Continue the work, but make the final response easy for the hook reconciler to classify: name decisions, artifacts, blockers, next actions, and verification.
- Do not claim OrgX was updated unless an MCP tool or API call actually succeeded.
- Wizard remains the owner of passive capture. Do not add a second plugin capture hook or treat the gateway's terminal receipt outbox as output upload.
- Do not claim delegated or spawned work finished because the spawn call
succeeded: that only means it started. Check it with
orgx_command_status(kind: "run"and the returned run ID) untilnext_poll_after_msisnull.
- Preserve Work Graph continuity:
- When a Work Graph report is generated, include its
work_graph_fingerprintandsignup_hydration.hydration_keyin summaries or artifacts that are safe to store. - Automatic Stop-hook reconciliation writes the latest local report to
~/.config/useorgx/wizard/hooks/reports/latest-work-graph-report.json. - Stop-hook posting requires
ORGX_HOOK_RECONCILE_POST=trueorORGX_WIZARD_HOOK_RECONCILE_POST=trueplusORGX_API_KEY. - Treat the fingerprint as the durable claim key that lets OrgX hydrate pre-signup audit value into a user's future workspace.
- Never derive the fingerprint from secrets or raw transcripts that would need to leave the local machine.
Quality bar
- Never post empty status updates.
- Messages must be evidence-based and specific.
- Include OrgX IDs whenever available.
- Use
source_client=codexonly when the advertised input supports it. - Preserve secrets: never emit tokens, cookies, API keys, or storage state into activity, retro, hook summaries, or final reports.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.