[{"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",1554,"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",468,"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-11 02:22:54",{"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,94,119,148,168,182],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":38},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[75,76,77,78,79,80,81,82,83,84,85,37,86,87,88,89,90,91,92,93],"search","deja search","error","ready","never","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":38},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[101,102,103,104,80,105,106,107,108,109,110,111,112,89,113,114,115,116,117,118],"reflect","deja reflect","brew","remember","project rules","project","session","end","reflection","Rules","decisions","review","with","record","github","next","https","node",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":132,"publishedAt":38},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[125,128,131],{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[121,133,134,135,136,137,106,138,81,139,140,26,141,37,142,143,144,145,146,147],"Video","short-form","standalone","PDF","viral","tiktok","short","social","song","URL","image","mcp server","schedule","api","publish",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":38},"01M71569ZM2X3H5RBFK8PVKMK2","review-study","Review a QuestionPunk survey before launch for wording, answer choices, branching, and missing settings. Use for check my survey or review this draft before publishing.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fquestionpunk\u002Fcodex-plugin\u002Fskills\u002Freview-study\u002FSKILL.md",[],[155,156,112,157,158,159,160,161,30,162,163,164,165,166,167],"study","review study","for","answer","missing","survey","publishing","check","draft","settings","launch","my","branching",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":38},"01M71567GV0C35YQBY0DPGR86B","manage-study","Find QuestionPunk studies, check status, publish an explicitly requested draft, or retrieve its participant link. Use for find my survey, publish this study, or how many people responded.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fquestionpunk\u002Fcodex-plugin\u002Fskills\u002Fmanage-study\u002FSKILL.md",[],[175,155,176,157,160,30,177,162,163,147,178,179,180,181,166],"manage study","manage","people","how","find","link","status",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":38},"01M71565A8TCA01AZQZRGRYMFZ","create-study","Create a saved QuestionPunk survey draft from a research brief or edit specified questions. Use for requests such as make a customer feedback survey or shorten my onboarding study.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fquestionpunk\u002Fcodex-plugin\u002Fskills\u002Fcreate-study\u002FSKILL.md",[],[189,155,190,191,33,192,157,193,160,194,30,195,196,163,197,198,199,200,201,166],"create study","create","brief","feedback","customer feedback","research brief","shorten","saved","research","requests","customer","questions","edit"]