[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MN8KYDZ9526PQZ5PTX4G27":3,"skill-same:01M6MN8KYDZ9526PQZ5PTX4G27":67},{"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":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6MN8KYDZ9526PQZ5PTX4G27","orgx-initiative-ops",null,"Use when Codex is working on a repo or task that is scoped to an OrgX initiative, workstream, milestone, task, blocker, or decision and needs to use OrgX MCP as the source of truth.","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-initiative-ops\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"ops","orgx initiative ops","MCP","codex","decision","repo","use","task","milestone","as","workstream","source","scoped","when","2026-11-10 10:12:30",false,"---\nname: orgx-initiative-ops\ndescription: Use when Codex is working on a repo or task that is scoped to an OrgX initiative, workstream, milestone, task, blocker, or decision and needs to use OrgX MCP as the source of truth.\n---\n\n# OrgX Initiative Ops\n\nUse this skill when the task is tied to OrgX execution state rather than just local code.\n\nThe bundled MCP connection requests the explicit `commander` runtime\nprofile. Use only tools actually exposed in that connection. A missing\ntool may need connection refresh or a coordinated plugin\u002Fserver update. Report\nthat tracking limitation and continue independent authorized repo work; never\ninvent an alias or weaken an autonomous run's signed schema policy.\n\n## Workflow\n\n1. Orient when OrgX state is relevant:\n- Read the relevant workspace or initiative summary before changing OrgX state\n  or relying on its status. Reuse context already read in this session when it\n  is sufficient; local edits do not require a new OrgX read.\n- For broad status\u002Freporting questions, prefer `get_operator_chronicle` first\n  when available; it is the canonical decision, artifact, PR, goal, gap, and\n  priority readout.\n- If the hosted OrgX MCP bootstrap advertises `get_operator_chronicle` but the\n  active AI client session has a stale callable tool list, immediately use\n  `orgx_recommend` only when that name is actually callable,\n  with `mode: \"morning_brief\"`, and report\n  the returned `chronicle.reportingNarrative.briefMarkdown`. Do not wait for the client to\n  reconnect before answering the operator.\n- If an initiative, workstream, task, blocker, or decision is named, treat OrgX as the source of truth for current status.\n\n2. Reuse existing context before creating new structure:\n- Query OrgX memory or list the relevant entities first.\n- Only scaffold new work when no matching initiative structure already exists.\n\n3. Work against the current slice:\n- Prefer updating the current task or workstream instead of creating parallel duplicate work.\n- Keep your local implementation aligned with the active OrgX entity state.\n\n4. Report concrete progress:\n- Use OrgX progress\u002Factivity tools for real execution milestones.\n- Register useful artifacts within the authorized tracking scope. Batch related\n  evidence at a meaningful milestone instead of writing on every file edit.\n- Missing IDs or unavailable reporting tools do not block implementation,\n  verification, PR updates, or an otherwise authorized merge. Report pending\n  tracking separately from the actual work outcome.\n\n5. Surface decisions explicitly:\n- Request a decision only when an unresolved choice needs human authority.\n  Resolve routine implementation choices within the user's scope, and honor\n  approval already given instead of requesting it again.\n- Do not bury blockers in prose.\n- Only a person settles a decision. `orgx_decide` with `action: \"approve\"` or\n  `\"reject\"` never approves or rejects anything: it returns the decision's\n  `review_url` in OrgX. Give the person that link and report only the dependent\n  work as waiting on them. Continue independent work, and never say a decision\n  was approved or rejected unless OrgX shows it settled.\n\n6. Close the loop:\n- Launching or spawning work starts it; it does not finish it. Report it as\n  started, keep the returned run ID, and check it with `orgx_command_status`\n  (`kind: \"run\"`, or `kind: \"decision\"` for a decision) before claiming any\n  outcome. When `next_poll_after_ms` is a number, check again after that many\n  milliseconds; `null` means the state is final. Use `orgx_inspect` for\n  anything without a run, decision or command ID.\n- When a task is truly done, verify it first.\n- Then update completion state in OrgX if the current task is known.\n\n## Quality bar\n\n- Never assume OrgX entity state from memory alone.\n- Never mark work complete without verification.\n- Prefer one verified task completion over broad unverified status claims.\n- If a write's outcome is unclear, reconcile the returned command or run first.\n  Retry only if that operation documents replay support, with identical input\n  and the same idempotency key; never send it through another tool name.\n- Use `source_client=codex` whenever the tool supports client attribution.\n","# OrgX Initiative Ops\n\nUse this skill when the task is tied to OrgX execution state rather than just local code.\n\nThe bundled MCP connection requests the explicit `commander` runtime\nprofile. Use only tools actually exposed in that connection. A missing\ntool may need connection refresh or a coordinated plugin\u002Fserver update. Report\nthat tracking limitation and continue independent authorized repo work; never\ninvent an alias or weaken an autonomous run's signed schema policy.\n\n## Workflow\n\n1. Orient when OrgX state is relevant:\n- Read the relevant workspace or initiative summary before changing OrgX state\n  or relying on its status. Reuse context already read in this session when it\n  is sufficient; local edits do not require a new OrgX read.\n- For broad status\u002Freporting questions, prefer `get_operator_chronicle` first\n  when available; it is the canonical decision, artifact, PR, goal, gap, and\n  priority readout.\n- If the hosted OrgX MCP bootstrap advertises `get_operator_chronicle` but the\n  active AI client session has a stale callable tool list, immediately use\n  `orgx_recommend` only when that name is actually callable,\n  with `mode: \"morning_brief\"`, and report\n  the returned `chronicle.reportingNarrative.briefMarkdown`. Do not wait for the client to\n  reconnect before answering the operator.\n- If an initiative, workstream, task, blocker, or decision is named, treat OrgX as the source of truth for current status.\n\n2. Reuse existing context before creating new structure:\n- Query OrgX memory or list the relevant entities first.\n- Only scaffold new work when no matching initiative structure already exists.\n\n3. Work against the current slice:\n- Prefer updating the current task or workstream instead of creating parallel duplicate work.\n- Keep your local implementation aligned with the active OrgX entity state.\n\n4. Report concrete progress:\n- Use OrgX progress\u002Factivity tools for real execution milestones.\n- Register useful artifacts within the authorized tracking scope. Batch related\n  evidence at a meaningful milestone instead of writing on every file edit.\n- Missing IDs or unavailable reporting tools do not block implementation,\n  verification, PR updates, or an otherwise authorized merge. Report pending\n  tracking separately from the actual work outcome.\n\n5. Surface decisions explicitly:\n- Request a decision only when an unresolved choice needs human authority.\n  Resolve routine implementation choices within the user's scope, and honor\n  approval already given instead of requesting it again.\n- Do not bury blockers in prose.\n- Only a person settles a decision. `orgx_decide` with `action: \"approve\"` or\n  `\"reject\"` never approves or rejects anything: it returns the decision's\n  `review_url` in OrgX. Give the person that link and report only the dependent\n  work as waiting on them. Continue independent work, and never say a decision\n  was approved or rejected unless OrgX shows it settled.\n\n6. Close the loop:\n- Launching or spawning work starts it; it does not finish it. Report it as\n  started, keep the returned run ID, and check it with `orgx_command_status`\n  (`kind: \"run\"`, or `kind: \"decision\"` for a decision) before claiming any\n  outcome. When `next_poll_after_ms` is a number, check again after that many\n  milliseconds; `null` means the state is final. Use `orgx_inspect` for\n  anything without a run, decision or command ID.\n- When a task is truly done, verify it first.\n- Then update completion state in OrgX if the current task is known.\n\n## Quality bar\n\n- Never assume OrgX entity state from memory alone.\n- Never mark work complete without verification.\n- Prefer one verified task completion over broad unverified status claims.\n- If a write's outcome is unclear, reconcile the returned command or run first.\n  Retry only if that operation documents replay support, with identical input\n  and the same idempotency key; never send it through another tool name.\n- Use `source_client=codex` whenever the tool supports client attribution.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fuseorgx\u002Forgx-codex-plugin\u002Fskills\u002Forgx-initiative-ops",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill orgx-initiative-ops",{"tool":59,"command":60},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill orgx-initiative-ops",{"tool":62,"command":63},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill orgx-initiative-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fuseorgx\u002Forgx-codex-plugin\u002Fskills\u002Forgx-initiative-ops\u002FSKILL.md",true,[],[68,78,86,94,102,110],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":77},"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":77},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":77},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":77},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":77},"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":77},"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",[],[]]