[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MN8SFV1B3PJJQ59N0PC777":3,"skill-same:01M6MN8SFV1B3PJJQ59N0PC777":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6MN8SFV1B3PJJQ59N0PC777","orgx-runtime-reporting",null,"Use when a Codex execution should report progress, artifacts, blockers, or completion state back to OrgX during a live task.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fuseorgx\u002Forgx-codex-plugin\u002Fskills\u002Forgx-runtime-reporting\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"reporting","runtime","orgx runtime reporting","codex","report","artifacts","state","execution","use","task","back","live","progress","when","2026-11-10 10:12:30",false,"---\nname: orgx-runtime-reporting\ndescription: Use when a Codex execution should report progress, artifacts, blockers, or completion state back to OrgX during a live task.\n---\n\n# OrgX Runtime Reporting\n\nUse this skill when Codex should keep OrgX updated during execution within the\nuser's authorized tracking scope. Reporting is not a prerequisite for local\nwork, PR updates, or an authorized merge. Reuse prior authorization; do not ask\nagain for each milestone. If reporting is unavailable, keep useful evidence\nlocally, continue independent work, and describe the tracking gap once.\n\n## Reporting contract\n\nThis plugin requests the explicit `commander` runtime profile. Verify its\nactual callable tools before using a name below. If the inventory mismatches,\nrefresh the connection or report the mismatch; do not guess an alias. Condensed\n`orgx_submit_receipt` reporting and portable `orgx_submit_work_receipt` document\nimport have different schemas and semantics. Migrate the payload before changing\ntools. Gateway terminal delivery and passive hook reporting use separate paths.\n\nThere are two reporting paths:\n\n- **Active path:** call OrgX MCP tools during the work when you know the\n  initiative, task, decision, blocker, or artifact context.\n- **Chronicle readout:** for operator reporting, call\n  `get_operator_chronicle` first when available and present\n  `chronicle.reportingNarrative.briefMarkdown` before drilling into individual entities.\n- **Stale-client fallback:** if bootstrap or docs advertise\n  `get_operator_chronicle` but the current AI client session has not refreshed\n  its callable tool list, call `orgx_recommend` only when\n  that name is present in the actual callable list, with `mode: \"morning_brief\"`,\n  and present the returned\n  `chronicle.reportingNarrative.briefMarkdown`. Do not ask the user to reconnect before\n  giving the report.\n- **Passive backstop:** Codex runtime hooks installed by `orgx-wizard hooks\n  install` record compact session events and run summary-only local Work Graph\n  reconciliation on `Stop`.\n\nDo not treat hook presence as a substitute for intentional OrgX writes. Hooks\nanswer whether OrgX was used and can write a local report automatically; MCP\ncalls, or an explicitly opted-in successful Work Graph post, make the work\ndurable in OrgX while the session is still fresh.\n\n## Workflow\n\n1. Resolve available IDs from args, env, or the current OrgX context:\n- `ORGX_INITIATIVE_ID`\n- `ORGX_WORKSTREAM_ID`\n- `ORGX_TASK_ID`\n- `ORGX_RUN_ID`\n- `ORGX_CORRELATION_ID`\n\n2. For reporting questions, retrieve the operator chronicle:\n- Use `get_operator_chronicle` with `period: \"30d\"` for broad clarity when it\n  is callable in the current client.\n- Use `period: \"day\"` or `period: \"week\"` when the user asks for yesterday or\n  this week.\n- If `get_operator_chronicle` is not callable in the current client, use the\n  existing `orgx_recommend` fallback when callable, with\n  `mode: \"morning_brief\"` and the broadest supported period. Treat the direct\n  tool as preferred, but do not block on client schema refresh.\n- Lead with `chronicle.reportingNarrative.briefMarkdown` for either reporting\n  tool, then call out\n  gaps and the next action.\n\n3. Emit activity at meaningful milestones:\n- `intent`\n- `execution`\n- `handoff`\n- `blocked`\n- `completed`\n\n4. Register proof of work:\n- Register useful evidence at meaningful milestones with a concrete summary;\n  batch related files rather than treating every edit as a separate artifact.\n- For a user-requested output attachment, use the existing `orgx_update_work`\n  when it is callable in the current connection. Inspect the current OrgX work\n  target first. Supply its persisted `type`, `id`, `workspace_id`, a stable\n  `idempotency_key`, and one `artifact`; omit `fields` for this call.\n- The artifact takes `name`, registered `artifact_type`, `location` containing\n  exactly one `artifact_url` or `external_url`, optional `description` and\n  `preview_markdown`, and optional `output_front_door`. A local path is not an\n  uploaded durable output. The front door contains a plain `answer`, at most\n  three existing `decisionId` references with `question`, `recommendation` and\n  `impact`, and producer-reported `checked` \u002F `notChecked` notes.\n- Context state, run cost, evaluator scores and client acceptance come from\n  server records. Do not submit them as producer authority. If OrgX context\n  could not load, say so before the plan and do not assume workspace team,\n  budget, brand or open work.\n- Reuse the exact payload and key after an ambiguous attachment failure.\n  Deliberately revised output gets a new key. Require a stored artifact UUID\n  in the response, then inspect it with `orgx_inspect` and present the canonical\n  output summary and review link. Attachment does not approve or complete work.\n- A connection without this admitted operation needs a matching MCP deployment\n  and inventory refresh. Keep the output available and report the exact gap;\n  never guess an alias or claim that a local receipt proved attachment.\n\n5. Handle blockers structurally:\n- If an unresolved choice requires human authority, request a decision with\n  explicit options. Routine implementation choices and actions already\n  authorized do not need a new approval.\n- Report the work that depends on a pending human decision as waiting with the\n  decision's `review_url`. `orgx_decide` approve\u002Freject only returns that link;\n  never report a decision as approved or rejected yourself. Continue work that\n  does not depend on that decision.\n- If context is missing, report the exact missing dependency.\n\n6. Close execution cleanly:\n- When the task is complete and verified, emit completion activity and update entity state if the task ID is available.\n\n7. If no OrgX IDs are available:\n- Continue the work, but make the final response easy for the hook reconciler to\n  classify: name decisions, artifacts, blockers, next actions, and verification.\n- Do not claim OrgX was updated unless an MCP tool or API call actually\n  succeeded.\n- Wizard remains the owner of passive capture. Do not add a second plugin\n  capture hook or treat the gateway's terminal receipt outbox as output upload.\n- Do not claim delegated or spawned work finished because the spawn call\n  succeeded: that only means it started. Check it with `orgx_command_status`\n  (`kind: \"run\"` and the returned run ID) until `next_poll_after_ms` is `null`.\n\n8. Preserve Work Graph continuity:\n- When a Work Graph report is generated, include its `work_graph_fingerprint`\n  and `signup_hydration.hydration_key` in summaries or artifacts that are safe\n  to store.\n- Automatic Stop-hook reconciliation writes the latest local report to\n  `~\u002F.config\u002Fuseorgx\u002Fwizard\u002Fhooks\u002Freports\u002Flatest-work-graph-report.json`.\n- Stop-hook posting requires `ORGX_HOOK_RECONCILE_POST=true` or\n  `ORGX_WIZARD_HOOK_RECONCILE_POST=true` plus `ORGX_API_KEY`.\n- Treat the fingerprint as the durable claim key that lets OrgX hydrate\n  pre-signup audit value into a user's future workspace.\n- Never derive the fingerprint from secrets or raw transcripts that would need\n  to leave the local machine.\n\n## Quality bar\n\n- Never post empty status updates.\n- Messages must be evidence-based and specific.\n- Include OrgX IDs whenever available.\n- Use `source_client=codex` only when the advertised input supports it.\n- Preserve secrets: never emit tokens, cookies, API keys, or storage state into\n  activity, retro, hook summaries, or final reports.\n","# OrgX Runtime Reporting\n\nUse this skill when Codex should keep OrgX updated during execution within the\nuser's authorized tracking scope. Reporting is not a prerequisite for local\nwork, PR updates, or an authorized merge. Reuse prior authorization; do not ask\nagain for each milestone. If reporting is unavailable, keep useful evidence\nlocally, continue independent work, and describe the tracking gap once.\n\n## Reporting contract\n\nThis plugin requests the explicit `commander` runtime profile. Verify its\nactual callable tools before using a name below. If the inventory mismatches,\nrefresh the connection or report the mismatch; do not guess an alias. Condensed\n`orgx_submit_receipt` reporting and portable `orgx_submit_work_receipt` document\nimport have different schemas and semantics. Migrate the payload before changing\ntools. Gateway terminal delivery and passive hook reporting use separate paths.\n\nThere are two reporting paths:\n\n- **Active path:** call OrgX MCP tools during the work when you know the\n  initiative, task, decision, blocker, or artifact context.\n- **Chronicle readout:** for operator reporting, call\n  `get_operator_chronicle` first when available and present\n  `chronicle.reportingNarrative.briefMarkdown` before drilling into individual entities.\n- **Stale-client fallback:** if bootstrap or docs advertise\n  `get_operator_chronicle` but the current AI client session has not refreshed\n  its callable tool list, call `orgx_recommend` only when\n  that name is present in the actual callable list, with `mode: \"morning_brief\"`,\n  and present the returned\n  `chronicle.reportingNarrative.briefMarkdown`. Do not ask the user to reconnect before\n  giving the report.\n- **Passive backstop:** Codex runtime hooks installed by `orgx-wizard hooks\n  install` record compact session events and run summary-only local Work Graph\n  reconciliation on `Stop`.\n\nDo not treat hook presence as a substitute for intentional OrgX writes. Hooks\nanswer whether OrgX was used and can write a local report automatically; MCP\ncalls, or an explicitly opted-in successful Work Graph post, make the work\ndurable in OrgX while the session is still fresh.\n\n## Workflow\n\n1. Resolve available IDs from args, env, or the current OrgX context:\n- `ORGX_INITIATIVE_ID`\n- `ORGX_WORKSTREAM_ID`\n- `ORGX_TASK_ID`\n- `ORGX_RUN_ID`\n- `ORGX_CORRELATION_ID`\n\n2. For reporting questions, retrieve the operator chronicle:\n- Use `get_operator_chronicle` with `period: \"30d\"` for broad clarity when it\n  is callable in the current client.\n- Use `period: \"day\"` or `period: \"week\"` when the user asks for yesterday or\n  this week.\n- If `get_operator_chronicle` is not callable in the current client, use the\n  existing `orgx_recommend` fallback when callable, with\n  `mode: \"morning_brief\"` and the broadest supported period. Treat the direct\n  tool as preferred, but do not block on client schema refresh.\n- Lead with `chronicle.reportingNarrative.briefMarkdown` for either reporting\n  tool, then call out\n  gaps and the next action.\n\n3. Emit activity at meaningful milestones:\n- `intent`\n- `execution`\n- `handoff`\n- `blocked`\n- `completed`\n\n4. Register proof of work:\n- Register useful evidence at meaningful milestones with a concrete summary;\n  batch related files rather than treating every edit as a separate artifact.\n- For a user-requested output attachment, use the existing `orgx_update_work`\n  when it is callable in the current connection. Inspect the current OrgX work\n  target first. Supply its persisted `type`, `id`, `workspace_id`, a stable\n  `idempotency_key`, and one `artifact`; omit `fields` for this call.\n- The artifact takes `name`, registered `artifact_type`, `location` containing\n  exactly one `artifact_url` or `external_url`, optional `description` and\n  `preview_markdown`, and optional `output_front_door`. A local path is not an\n  uploaded durable output. The front door contains a plain `answer`, at most\n  three existing `decisionId` references with `question`, `recommendation` and\n  `impact`, and producer-reported `checked` \u002F `notChecked` notes.\n- Context state, run cost, evaluator scores and client acceptance come from\n  server records. Do not submit them as producer authority. If OrgX context\n  could not load, say so before the plan and do not assume workspace team,\n  budget, brand or open work.\n- Reuse the exact payload and key after an ambiguous attachment failure.\n  Deliberately revised output gets a new key. Require a stored artifact UUID\n  in the response, then inspect it with `orgx_inspect` and present the canonical\n  output summary and review link. Attachment does not approve or complete work.\n- A connection without this admitted operation needs a matching MCP deployment\n  and inventory refresh. Keep the output available and report the exact gap;\n  never guess an alias or claim that a local receipt proved attachment.\n\n5. Handle blockers structurally:\n- If an unresolved choice requires human authority, request a decision with\n  explicit options. Routine implementation choices and actions already\n  authorized do not need a new approval.\n- Report the work that depends on a pending human decision as waiting with the\n  decision's `review_url`. `orgx_decide` approve\u002Freject only returns that link;\n  never report a decision as approved or rejected yourself. Continue work that\n  does not depend on that decision.\n- If context is missing, report the exact missing dependency.\n\n6. Close execution cleanly:\n- When the task is complete and verified, emit completion activity and update entity state if the task ID is available.\n\n7. If no OrgX IDs are available:\n- Continue the work, but make the final response easy for the hook reconciler to\n  classify: name decisions, artifacts, blockers, next actions, and verification.\n- Do not claim OrgX was updated unless an MCP tool or API call actually\n  succeeded.\n- Wizard remains the owner of passive capture. Do not add a second plugin\n  capture hook or treat the gateway's terminal receipt outbox as output upload.\n- Do not claim delegated or spawned work finished because the spawn call\n  succeeded: that only means it started. Check it with `orgx_command_status`\n  (`kind: \"run\"` and the returned run ID) until `next_poll_after_ms` is `null`.\n\n8. Preserve Work Graph continuity:\n- When a Work Graph report is generated, include its `work_graph_fingerprint`\n  and `signup_hydration.hydration_key` in summaries or artifacts that are safe\n  to store.\n- Automatic Stop-hook reconciliation writes the latest local report to\n  `~\u002F.config\u002Fuseorgx\u002Fwizard\u002Fhooks\u002Freports\u002Flatest-work-graph-report.json`.\n- Stop-hook posting requires `ORGX_HOOK_RECONCILE_POST=true` or\n  `ORGX_WIZARD_HOOK_RECONCILE_POST=true` plus `ORGX_API_KEY`.\n- Treat the fingerprint as the durable claim key that lets OrgX hydrate\n  pre-signup audit value into a user's future workspace.\n- Never derive the fingerprint from secrets or raw transcripts that would need\n  to leave the local machine.\n\n## Quality bar\n\n- Never post empty status updates.\n- Messages must be evidence-based and specific.\n- Include OrgX IDs whenever available.\n- Use `source_client=codex` only when the advertised input supports it.\n- Preserve secrets: never emit tokens, cookies, API keys, or storage state into\n  activity, retro, hook summaries, or final reports.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fuseorgx\u002Forgx-codex-plugin\u002Fskills\u002Forgx-runtime-reporting",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill orgx-runtime-reporting",{"tool":54,"command":55},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill orgx-runtime-reporting",{"tool":57,"command":58},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill orgx-runtime-reporting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fuseorgx\u002Forgx-codex-plugin\u002Fskills\u002Forgx-runtime-reporting\u002FSKILL.md",true,[],[63,73,81,89,97,105],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":72},"01M7DV332YQMGD8WTRJ9DZQXTB","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.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":72},"01M7DV2YGHCZVBEB1AHYB6CGHE","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.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":72},"01M7DV2TQN1H11ME2SAF9MXN7V","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.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":72},"01M7DV2NE452NEA8TXATKSNAJH","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.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":72},"01M7DV2HENRBR2KSCVM064WH0Y","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.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":72},"01M7DV2CADR5R7RQFFYPNAGR9Y","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.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]