[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MKADP0Y5RPN5BT38MJKA0T":3,"skill-same:01M6MKADP0Y5RPN5BT38MJKA0T":75},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":68},"01M6MKADP0Y5RPN5BT38MJKA0T","skill-intake",null,"Move incoming issues and pull requests through triage states until each is actionable or closed — use when the queue has piled up or a report arrives unsorted","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\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-intake\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,38,39],"intake","skill intake","triage","pull requests","report","issues","pull","use","up","queue","actionable","move","states","requests","true","when","2026-11-10 10:12:30",false,"---\nname: skill-intake\ndescription: \"Move incoming issues and pull requests through triage states until each is actionable or closed — use when the queue has piled up or a report arrives unsorted\"\ndisable-model-invocation: true\n---\n\n> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# Intake\n\nWork the incoming queue. Each item moves through a small set of states until it\nis either actionable by someone who did not write it, or closed with a reason.\n\n**A pull request is an issue with attached code.** Same states, same moves, with\nthe deltas noted below. Resolving a bare `#42` means checking both.\n\nAdapted from `triage` in\n[mattpocock\u002Fskills](https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills) (MIT), cut down to the\nstates this repo can actually represent and retargeted at `gh` and `bd`.\n\n## When To Use\n\n- Open issues or PRs have accumulated and nobody knows which are real.\n- A new report arrives and needs sorting before anyone works it.\n- An issue has been sitting because it is not clear what it is asking for.\n- Before planning, to establish what is actually in the queue.\n\n## When Not To Use\n\n- To do the work an item describes. Triage decides what happens to it, not how.\n- For local, private notes. That is `skill-issues` and `.octo\u002FISSUES.md`.\n- To review a PR's code quality. That is `skill-code-review` or\n  `skill-staged-review`; intake decides whether the PR should be reviewed at all.\n\n## Inputs\n\nAn issue or PR reference, or nothing — with nothing, take the queue in order.\n`gh issue list` and `gh pr list` for the public surface; `bd ready` and\n`bd blocked` for tracked work.\n\n## Workflow\n\n### 1. Categorise\n\nWhat kind of thing is it: a bug, an enhancement, a question, or noise. For a PR,\nalso: does it correspond to an existing issue, or arrive unannounced?\n\nDo not skip this because the title looks obvious. Titles are written by people\nwho already know what they meant.\n\n### 2. Verify\n\nThe step that earns the whole skill. For a bug: **reproduce it, or establish that\nyou cannot.** For a PR: check the claim it makes is the change it contains.\n\nAn unverified bug report is a hypothesis. Filing it as fact wastes whoever picks\nit up. If reproduction needs something you do not have — credentials, a dataset,\na platform — that is `needs-info`, not `verified`.\n\n### 3. Assign a state\n\n- **`needs-triage`** — arrived, not yet sorted. The entry state.\n- **`needs-info`** — blocked on the reporter. Say exactly what is missing; \"more\n  detail\" is not a request anyone can act on.\n- **`verified`** — reproduced or confirmed, ready to be worked.\n- **`needs-decision`** — real, but what to do is a judgement call the maintainer\n  has not made. Do not resolve these by inference. Escalate, or run\n  `skill-pressure-test` with the maintainer.\n- **`closed`** — not a bug, out of scope, duplicate, or fixed. Always with a\n  reason, and for out-of-scope, why.\n\n### 4. Write the brief\n\nFor anything reaching `verified`, write what someone picking it up needs and\nwould otherwise have to rediscover: where the relevant code is, what you already\nruled out, and how to tell when it is fixed. This is the difference between an\nitem that gets worked and one that gets re-triaged.\n\nFor a PR, add: whether it has tests, whether CI is green, and whether it conflicts\nwith anything in flight.\n\n### 5. Record it\n\nFor public comment text, stream the completed note through the outbound gate:\n\n```bash\nprintf '%s\\n' \"$TRIAGE_NOTE\" | \\\n  \"${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}\u002F.claude-octopus\u002Fplugin}}\u002Fscripts\u002Fsafe-gh-comment.sh\" \\\n    --repo OWNER\u002FREPO issue-comment ISSUE_NUMBER -\n```\n\nUse `gh issue edit --add-label` only for the label mutation. Use `bd update` for\ntracked work. If `bd` writes are blocked by pending migrations, say so and do\nnot run the migration — see `skill-work-slicing` for that constraint.\n\n## Provider Or Data Priority\n\n1. The repository — reproduce against the actual code.\n2. CI logs and run history for anything claiming a failure.\n3. The reporter, for what only they can supply.\n4. Never assume the report is accurate because it is detailed.\n\n## Stop Or Checkpoint Rules\n\n- Stop before closing anything a human filed deliberately, unless it is a clear\n  duplicate. Closing is the one move that is rude to get wrong.\n- Stop before `needs-decision` items and surface them rather than guessing.\n- Do not merge or push as part of triage, even for a PR that looks ready.\n- One item at a time. Batch-labelling a queue without reading it is how real\n  reports end up buried under a label.\n\n## Output Contract\n\nPer item:\n\n1. **Reference and category.**\n2. **State assigned, and why.**\n3. **Verification result** — reproduced, could not reproduce, or not attempted\n   with the reason.\n4. **Brief** — for verified items only.\n5. **Action taken** — labels, comments, or the exact commands not run and why.\n\nThen a queue summary: counts by state, and which items are now takeable.\n\n## Verification\n\n- Every `verified` item was actually reproduced, or says explicitly that it was\n  not and why.\n- Every `needs-info` names the specific missing thing.\n- Every closure carries a reason.\n- Nothing was merged, pushed, or fixed during triage.\n","> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# Intake\n\nWork the incoming queue. Each item moves through a small set of states until it\nis either actionable by someone who did not write it, or closed with a reason.\n\n**A pull request is an issue with attached code.** Same states, same moves, with\nthe deltas noted below. Resolving a bare `#42` means checking both.\n\nAdapted from `triage` in\n[mattpocock\u002Fskills](https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills) (MIT), cut down to the\nstates this repo can actually represent and retargeted at `gh` and `bd`.\n\n## When To Use\n\n- Open issues or PRs have accumulated and nobody knows which are real.\n- A new report arrives and needs sorting before anyone works it.\n- An issue has been sitting because it is not clear what it is asking for.\n- Before planning, to establish what is actually in the queue.\n\n## When Not To Use\n\n- To do the work an item describes. Triage decides what happens to it, not how.\n- For local, private notes. That is `skill-issues` and `.octo\u002FISSUES.md`.\n- To review a PR's code quality. That is `skill-code-review` or\n  `skill-staged-review`; intake decides whether the PR should be reviewed at all.\n\n## Inputs\n\nAn issue or PR reference, or nothing — with nothing, take the queue in order.\n`gh issue list` and `gh pr list` for the public surface; `bd ready` and\n`bd blocked` for tracked work.\n\n## Workflow\n\n### 1. Categorise\n\nWhat kind of thing is it: a bug, an enhancement, a question, or noise. For a PR,\nalso: does it correspond to an existing issue, or arrive unannounced?\n\nDo not skip this because the title looks obvious. Titles are written by people\nwho already know what they meant.\n\n### 2. Verify\n\nThe step that earns the whole skill. For a bug: **reproduce it, or establish that\nyou cannot.** For a PR: check the claim it makes is the change it contains.\n\nAn unverified bug report is a hypothesis. Filing it as fact wastes whoever picks\nit up. If reproduction needs something you do not have — credentials, a dataset,\na platform — that is `needs-info`, not `verified`.\n\n### 3. Assign a state\n\n- **`needs-triage`** — arrived, not yet sorted. The entry state.\n- **`needs-info`** — blocked on the reporter. Say exactly what is missing; \"more\n  detail\" is not a request anyone can act on.\n- **`verified`** — reproduced or confirmed, ready to be worked.\n- **`needs-decision`** — real, but what to do is a judgement call the maintainer\n  has not made. Do not resolve these by inference. Escalate, or run\n  `skill-pressure-test` with the maintainer.\n- **`closed`** — not a bug, out of scope, duplicate, or fixed. Always with a\n  reason, and for out-of-scope, why.\n\n### 4. Write the brief\n\nFor anything reaching `verified`, write what someone picking it up needs and\nwould otherwise have to rediscover: where the relevant code is, what you already\nruled out, and how to tell when it is fixed. This is the difference between an\nitem that gets worked and one that gets re-triaged.\n\nFor a PR, add: whether it has tests, whether CI is green, and whether it conflicts\nwith anything in flight.\n\n### 5. Record it\n\nFor public comment text, stream the completed note through the outbound gate:\n\n```bash\nprintf '%s\\n' \"$TRIAGE_NOTE\" | \\\n  \"${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}\u002F.claude-octopus\u002Fplugin}}\u002Fscripts\u002Fsafe-gh-comment.sh\" \\\n    --repo OWNER\u002FREPO issue-comment ISSUE_NUMBER -\n```\n\nUse `gh issue edit --add-label` only for the label mutation. Use `bd update` for\ntracked work. If `bd` writes are blocked by pending migrations, say so and do\nnot run the migration — see `skill-work-slicing` for that constraint.\n\n## Provider Or Data Priority\n\n1. The repository — reproduce against the actual code.\n2. CI logs and run history for anything claiming a failure.\n3. The reporter, for what only they can supply.\n4. Never assume the report is accurate because it is detailed.\n\n## Stop Or Checkpoint Rules\n\n- Stop before closing anything a human filed deliberately, unless it is a clear\n  duplicate. Closing is the one move that is rude to get wrong.\n- Stop before `needs-decision` items and surface them rather than guessing.\n- Do not merge or push as part of triage, even for a PR that looks ready.\n- One item at a time. Batch-labelling a queue without reading it is how real\n  reports end up buried under a label.\n\n## Output Contract\n\nPer item:\n\n1. **Reference and category.**\n2. **State assigned, and why.**\n3. **Verification result** — reproduced, could not reproduce, or not attempted\n   with the reason.\n4. **Brief** — for verified items only.\n5. **Action taken** — labels, comments, or the exact commands not run and why.\n\nThen a queue summary: counts by state, and which items are now takeable.\n\n## Verification\n\n- Every `verified` item was actually reproduced, or says explicitly that it was\n  not and why.\n- Every `needs-info` names the specific missing thing.\n- Every closure carries a reason.\n- Nothing was merged, pushed, or fixed during triage.\n",{"name":5,"description":7,"disable-model-invocation":45},true,"main","f620abaff09061f8c8b1f1559dca3fdd031a32e5","plugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-intake",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":57,"prompt":67,"zipAvailable":45},[58,61,64],{"tool":59,"command":60},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-intake",{"tool":62,"command":63},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-intake",{"tool":65,"command":66},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-intake","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-intake\u002FSKILL.md",[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"agents\u002Fopenai.yaml","REFERENCE","参考文档",159,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-intake\u002Fagents\u002Fopenai.yaml",[76,86,94,102,110,118],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":85},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":85},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":85},"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":85},"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":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":85},"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",[],[]]