[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DHPCFQAE2NX91PPAPBPF7F":3,"skill-same:01M6DHPCFQAE2NX91PPAPBPF7F":80},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6DHPCFQAE2NX91PPAPBPF7F","argdown-toulmin",null,"The grammar and presentation standard for writing an argument as Chained Toulmin Argdown -- statements, numbered premises, warrants in the inference bar, chaining, relations, `{basis, pointer, source, reason}` metadata, diagnostic tags, granularity, layout, and parser validation. Load before writing, editing, or parsing any Argdown. Not a procedure for reconstructing, evaluating, or reporting an argument.","nicsuzor\u002FacademicOps","nicsuzor","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4496978?v=4","01M6DGWCFNDYP03M4DQAHA6DN1","Nicolas Suzor","01M6DGWCPXG37BMXRZZKXR0A1Z",5,"MIT","https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fplugins\u002Fida\u002Fskills\u002Fargdown-toulmin\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36],"argdown toulmin","writing","inference","validation","metadata","reporting","parsing","chaining","grammar","parser","editing","layout","as","2026-11-10 10:12:30",false,"---\nname: argdown-toulmin\ndescription: The grammar and presentation standard for writing an argument as Chained Toulmin Argdown -- statements, numbered premises, warrants in the inference bar, chaining, relations, `{basis, pointer, source, reason}` metadata, diagnostic tags, granularity, layout, and parser validation. Load before writing, editing, or parsing any Argdown. Not a procedure for reconstructing, evaluating, or reporting an argument.\n---\n\n# Chained Toulmin Argdown\n\nHow an argument is written. Every Argdown document follows this standard.\n\n## Document\n\n- **Frontmatter** between `===` lines. Required: `title`, `granularity` (`level`, `floor`), and `model: mode: strict`. Add other keys as the document needs (for example `source`, `author`, `date`).\n- **Main conclusion first**, as a titled statement, then the arguments for it. Group arguments under Argdown headings.\n\n## Statements and arguments\n\n- **Statement**: `[Title]: text`. Reuse a title exactly to mean the same statement; a new title is a new statement.\n- **Argument**: `\u003CTitle>: gist`, followed by a premise-conclusion block.\n- **Premises** are numbered `(1)`, `(2)` and hold only grounds: observations, findings, sample bounds, scope conditions, or prior conclusions.\n- **Warrant in the inference bar**: `-- Name: warrant text. Unless: \u003Cdefeater>; \u003Cstatus>. {uses: [1, 2], basis: \"...\", pointer: \"...\"} --`. The warrant is the rule, principle, mechanism, or method that licenses the step, qualified by defeaters and their status. A warrant is never a numbered premise.\n- **Backing** (what shows the warrant holds) goes in the bar's metadata. A warrant that needs its own support gets a child argument concluding it.\n- **Relevance rule:** every premise on an inference is a condition of its warrant, and there is no premise count. A long run of premises under one warrant usually hides several steps (a method-to-finding step and a finding-to-mechanism step, say); split them with an intermediate conclusion and a second bar.\n- **One bar per epistemic layer**: observation and method to pattern, pattern and mechanism to diagnosis, diagnosis and normative standard to evaluation.\n- **Chain, don't widen.** Stack up to 3 bars in one block. Beyond that, start a new argument whose premise `(1)` reuses the upstream conclusion's title.\n\n## Relations\n\nWrite each relation on its own indented line below the statement or argument it starts from.\n\n- `+>` supports a statement.\n- `->` attacks a statement. A reply to an objection is an attack on the objection.\n- `_>` undercuts an argument: it attacks the inference, not a premise.\n- `>\u003C` marks two statements that contradict.\n\nAttach a relation to the argument that concludes or first states the claim, never to one that only borrows it as a premise.\n\n## Metadata\n\n`{basis, pointer, source, reason}` on every premise and warrant that is not a derived intermediate conclusion.\n\n- `basis`, how the claim is known:\n  - `\"observed\"`: a finding, quotation, measured value, or inspected state.\n  - `\"method-bounded\"`: the scope or limit of a method: a sampling frame, operational definition, or instrument limit.\n  - `\"exhaustively-searched\"`: an absence or count from a search whose full boundary is stated.\n  - `\"attempted-and-failed\"`: an absence or incapacity shown by a stated attempt that failed.\n  - `\"theory\"`: a principle, mechanism, legal rule, or normative standard from scholarship, doctrine, or a governing rule.\n  - `\"reported-by\"`: a claim adopted from a cited secondary source or report.\n  - `\"stated\"`: the author's own framing: research question, definition, scope, or roadmap claim.\n  - `\"assumed\"`: supplied to complete an inference and found in no source.\n- `pointer`: a locator a reader can open: page and paragraph, section, citation handle, `owner\u002Frepo@sha:path:line`, node or span ID, URL, or the exact query run.\n- `source`: the verbatim quote (line breaks joined by single spaces, original markup kept) or the exact observed value. A derived intermediate conclusion has no `source` unless the text states it verbatim.\n- `reason`: for `\"assumed\"` only, the gap the item bridges. An assumed item has no `pointer` or `source`.\n\nFor peer messages, task handbacks, and premise-check reports, consult [`..\u002Fpremise-check\u002FSKILL.md`](..\u002Fpremise-check\u002FSKILL.md) for the closed basis vocabulary in words and rank rules (`I read it`, `I did it`, `attempted, failed`, `rule`, `worker reported, verdict`, `worker reported, unchecked`, `assumed, not checked here`).\n\nAn `\"observed\"` or `\"reported-by\"` item quotes its deciding value or text (`status: MERGED`, `p = 0.004`) inline or in `source`, because a bare pointer shows only that something exists.\n\nAn assumed inference rule goes in the bar with `basis: \"assumed\"`. An assumed condition goes in a numbered premise with `basis: \"assumed\"` and `#missing`.\n\n## Tags\n\nTags go before the `{metadata}`. Each tag marks one kind of open issue:\n\n- `#missing`: a premise, warrant, or bridge the step needs and the text does not state.\n- `#needs-evidence`: a load-bearing premise with no data or authority behind it.\n- `#scope-drift`: a conclusion wider than its premises license, in population, quantifier, or construct.\n- `#method-gap`: a method that cannot observe what the step claims from it.\n- `#unanswered`: an objection or rival explanation the argument does not meet.\n- `#conflict`: two claims that contradict, joined by `>\u003C`.\n- `#format`: a document that breaks this standard.\n\n## Granularity\n\n`level` sets how deep the document goes; `floor` is one sentence naming what counts as a leaf. A statement at the floor carries its metadata and gets no sub-argument.\n\n- `macro`: a whole work. Thesis, part-level and chapter-level claims, one argument per chapter or section. Default floor: chapter-level findings and cited theories.\n- `meso` (default): a paper, chapter, or section. Main conclusion and each line of support down to primary findings, method bounds, and warrants. Default floor: individual cited sources, summary statistics, and uncontested definitions.\n- `micro`: one to three load-bearing inferences, down to operational definitions, sampling bounds, and warrant backing. Default floor: raw observations with verbatim pointers.\n\n## Presentation\n\n- Statement text is clear, direct, modern prose. The author's own wording goes verbatim in `source`, not in the statement.\n- One blank line between arguments and around headings.\n\n```argdown\n===\ntitle: Work or question, part covered\ngranularity:\n  level: meso\n  floor: \"One sentence naming what counts as a leaf.\"\nmodel:\n  mode: strict\n===\n\n# Main Conclusion\n\n[Main Claim]: The claim the document establishes. {basis: \"stated\", pointer: \"...\", source: \"...\"}\n\n# Arguments\n\n\u003CLine of Support>: How this chain supports the main claim.\n\n(1) [Finding]: What was observed. {basis: \"observed\", pointer: \"...\", source: \"...\"}\n(2) [Bound]: The scope of the method or sample. {basis: \"method-bounded\", pointer: \"...\", source: \"...\"}\n-- Method Warrant: Why the method captures the pattern. Unless: sampling bias or instrument drift; not observed. {uses: [1, 2], basis: \"stated\", pointer: \"...\"} --\n(3) [Pattern]: The pattern the data establish.\n(4) [Condition]: A further condition the next step needs. {basis: \"observed\", pointer: \"...\", source: \"...\"}\n-- Mechanism Warrant: The rule that turns the pattern into the claim. Unless: competing mechanism explains the pattern; ruled out by (2). {uses: [3, 4], basis: \"theory\", pointer: \"...\"} --\n(5) [Section Claim]: The claim this chain supports.\n  +> [Main Claim]\n```\n\n## Parser compliance\n\n- Keep each statement (`(1) [Title]: text #tag {metadata}`) on one line, or put its `{metadata}` alone on an indented continuation line. The parser rejects a tag after the metadata.\n- Write inference-bar text without commas, because the parser splits bar text on commas into separate rules.\n- Escape a literal underscore in statement text as `\\_`, and keep unescaped `[` `]` `\u003C` `>` out of statement prose. Escapes do not apply inside quoted `source` strings.\n- Validate standalone Argdown files (authored in `argument-extraction`, `argument-audit`, or `argument-map`) with `npx -y @argdown\u002Fcli json --logParserErrors --throwExceptions \u003Cfile>.argdown \u003Coutdir>`. Handback receipts and handover reports (`dump`, `premise-check`) follow syntax rules directly without invoking an external parser CLI or writing test scripts. On a syntax error in standalone files, fix it from the parser message and retry, at most 3 times; if it still fails, halt and report the error.\n- Then read the JSON and confirm every argument appears with its premises and reaches the main conclusion, through a relation or a conclusion title reused as a premise.\n","# Chained Toulmin Argdown\n\nHow an argument is written. Every Argdown document follows this standard.\n\n## Document\n\n- **Frontmatter** between `===` lines. Required: `title`, `granularity` (`level`, `floor`), and `model: mode: strict`. Add other keys as the document needs (for example `source`, `author`, `date`).\n- **Main conclusion first**, as a titled statement, then the arguments for it. Group arguments under Argdown headings.\n\n## Statements and arguments\n\n- **Statement**: `[Title]: text`. Reuse a title exactly to mean the same statement; a new title is a new statement.\n- **Argument**: `\u003CTitle>: gist`, followed by a premise-conclusion block.\n- **Premises** are numbered `(1)`, `(2)` and hold only grounds: observations, findings, sample bounds, scope conditions, or prior conclusions.\n- **Warrant in the inference bar**: `-- Name: warrant text. Unless: \u003Cdefeater>; \u003Cstatus>. {uses: [1, 2], basis: \"...\", pointer: \"...\"} --`. The warrant is the rule, principle, mechanism, or method that licenses the step, qualified by defeaters and their status. A warrant is never a numbered premise.\n- **Backing** (what shows the warrant holds) goes in the bar's metadata. A warrant that needs its own support gets a child argument concluding it.\n- **Relevance rule:** every premise on an inference is a condition of its warrant, and there is no premise count. A long run of premises under one warrant usually hides several steps (a method-to-finding step and a finding-to-mechanism step, say); split them with an intermediate conclusion and a second bar.\n- **One bar per epistemic layer**: observation and method to pattern, pattern and mechanism to diagnosis, diagnosis and normative standard to evaluation.\n- **Chain, don't widen.** Stack up to 3 bars in one block. Beyond that, start a new argument whose premise `(1)` reuses the upstream conclusion's title.\n\n## Relations\n\nWrite each relation on its own indented line below the statement or argument it starts from.\n\n- `+>` supports a statement.\n- `->` attacks a statement. A reply to an objection is an attack on the objection.\n- `_>` undercuts an argument: it attacks the inference, not a premise.\n- `>\u003C` marks two statements that contradict.\n\nAttach a relation to the argument that concludes or first states the claim, never to one that only borrows it as a premise.\n\n## Metadata\n\n`{basis, pointer, source, reason}` on every premise and warrant that is not a derived intermediate conclusion.\n\n- `basis`, how the claim is known:\n  - `\"observed\"`: a finding, quotation, measured value, or inspected state.\n  - `\"method-bounded\"`: the scope or limit of a method: a sampling frame, operational definition, or instrument limit.\n  - `\"exhaustively-searched\"`: an absence or count from a search whose full boundary is stated.\n  - `\"attempted-and-failed\"`: an absence or incapacity shown by a stated attempt that failed.\n  - `\"theory\"`: a principle, mechanism, legal rule, or normative standard from scholarship, doctrine, or a governing rule.\n  - `\"reported-by\"`: a claim adopted from a cited secondary source or report.\n  - `\"stated\"`: the author's own framing: research question, definition, scope, or roadmap claim.\n  - `\"assumed\"`: supplied to complete an inference and found in no source.\n- `pointer`: a locator a reader can open: page and paragraph, section, citation handle, `owner\u002Frepo@sha:path:line`, node or span ID, URL, or the exact query run.\n- `source`: the verbatim quote (line breaks joined by single spaces, original markup kept) or the exact observed value. A derived intermediate conclusion has no `source` unless the text states it verbatim.\n- `reason`: for `\"assumed\"` only, the gap the item bridges. An assumed item has no `pointer` or `source`.\n\nFor peer messages, task handbacks, and premise-check reports, consult [`..\u002Fpremise-check\u002FSKILL.md`](..\u002Fpremise-check\u002FSKILL.md) for the closed basis vocabulary in words and rank rules (`I read it`, `I did it`, `attempted, failed`, `rule`, `worker reported, verdict`, `worker reported, unchecked`, `assumed, not checked here`).\n\nAn `\"observed\"` or `\"reported-by\"` item quotes its deciding value or text (`status: MERGED`, `p = 0.004`) inline or in `source`, because a bare pointer shows only that something exists.\n\nAn assumed inference rule goes in the bar with `basis: \"assumed\"`. An assumed condition goes in a numbered premise with `basis: \"assumed\"` and `#missing`.\n\n## Tags\n\nTags go before the `{metadata}`. Each tag marks one kind of open issue:\n\n- `#missing`: a premise, warrant, or bridge the step needs and the text does not state.\n- `#needs-evidence`: a load-bearing premise with no data or authority behind it.\n- `#scope-drift`: a conclusion wider than its premises license, in population, quantifier, or construct.\n- `#method-gap`: a method that cannot observe what the step claims from it.\n- `#unanswered`: an objection or rival explanation the argument does not meet.\n- `#conflict`: two claims that contradict, joined by `>\u003C`.\n- `#format`: a document that breaks this standard.\n\n## Granularity\n\n`level` sets how deep the document goes; `floor` is one sentence naming what counts as a leaf. A statement at the floor carries its metadata and gets no sub-argument.\n\n- `macro`: a whole work. Thesis, part-level and chapter-level claims, one argument per chapter or section. Default floor: chapter-level findings and cited theories.\n- `meso` (default): a paper, chapter, or section. Main conclusion and each line of support down to primary findings, method bounds, and warrants. Default floor: individual cited sources, summary statistics, and uncontested definitions.\n- `micro`: one to three load-bearing inferences, down to operational definitions, sampling bounds, and warrant backing. Default floor: raw observations with verbatim pointers.\n\n## Presentation\n\n- Statement text is clear, direct, modern prose. The author's own wording goes verbatim in `source`, not in the statement.\n- One blank line between arguments and around headings.\n\n```argdown\n===\ntitle: Work or question, part covered\ngranularity:\n  level: meso\n  floor: \"One sentence naming what counts as a leaf.\"\nmodel:\n  mode: strict\n===\n\n# Main Conclusion\n\n[Main Claim]: The claim the document establishes. {basis: \"stated\", pointer: \"...\", source: \"...\"}\n\n# Arguments\n\n\u003CLine of Support>: How this chain supports the main claim.\n\n(1) [Finding]: What was observed. {basis: \"observed\", pointer: \"...\", source: \"...\"}\n(2) [Bound]: The scope of the method or sample. {basis: \"method-bounded\", pointer: \"...\", source: \"...\"}\n-- Method Warrant: Why the method captures the pattern. Unless: sampling bias or instrument drift; not observed. {uses: [1, 2], basis: \"stated\", pointer: \"...\"} --\n(3) [Pattern]: The pattern the data establish.\n(4) [Condition]: A further condition the next step needs. {basis: \"observed\", pointer: \"...\", source: \"...\"}\n-- Mechanism Warrant: The rule that turns the pattern into the claim. Unless: competing mechanism explains the pattern; ruled out by (2). {uses: [3, 4], basis: \"theory\", pointer: \"...\"} --\n(5) [Section Claim]: The claim this chain supports.\n  +> [Main Claim]\n```\n\n## Parser compliance\n\n- Keep each statement (`(1) [Title]: text #tag {metadata}`) on one line, or put its `{metadata}` alone on an indented continuation line. The parser rejects a tag after the metadata.\n- Write inference-bar text without commas, because the parser splits bar text on commas into separate rules.\n- Escape a literal underscore in statement text as `\\_`, and keep unescaped `[` `]` `\u003C` `>` out of statement prose. Escapes do not apply inside quoted `source` strings.\n- Validate standalone Argdown files (authored in `argument-extraction`, `argument-audit`, or `argument-map`) with `npx -y @argdown\u002Fcli json --logParserErrors --throwExceptions \u003Cfile>.argdown \u003Coutdir>`. Handback receipts and handover reports (`dump`, `premise-check`) follow syntax rules directly without invoking an external parser CLI or writing test scripts. On a syntax error in standalone files, fix it from the parser message and retry, at most 3 times; if it still fails, halt and report the error.\n- Then read the JSON and confirm every argument appears with its premises and reaches the main conclusion, through a relation or a conclusion title reused as a premise.\n",{"name":5,"description":7},"main","22a4e466ac352d09f636273685845a312ee07a15","plugins\u002Fida\u002Fskills\u002Fargdown-toulmin",3,"https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps","https:\u002F\u002Fgithub.com\u002Fnicsuzor","https:\u002F\u002Fnic.suzor.net\u002F","2026-11-10 16:57:47",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add nicsuzor\u002FacademicOps --skill argdown-toulmin",{"tool":56,"command":57},"bunx","bunx skills add nicsuzor\u002FacademicOps --skill argdown-toulmin",{"tool":59,"command":60},"pnpm","pnpm dlx skills add nicsuzor\u002FacademicOps --skill argdown-toulmin","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fplugins\u002Fida\u002Fskills\u002Fargdown-toulmin\u002FSKILL.md",true,[64,70,76],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"pyproject.toml","OTHER","其他",331,"https:\u002F\u002Fgithub.com\u002Fcateyephotos\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills.pre-symlink-1776435493\u002Fanvil\u002Fpyproject.toml",{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"run.sh","SCRIPT","脚本",576,"https:\u002F\u002Fgithub.com\u002Fcateyephotos\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills.pre-symlink-1776435493\u002Fanvil\u002Frun.sh",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"sanity.sh",62,"https:\u002F\u002Fgithub.com\u002Fcateyephotos\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills.pre-symlink-1776435493\u002Fanvil\u002Fsanity.sh",[81,108,113,118,123,147],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":37},"01M6M6JR6VXPDA3MDPVS36DSSP","refresh-questions","Sweep and refresh open questions in the Telegram Mini App by closing questions that are answered elsewhere, superseded, or asking for completed actions, and ensuring active open questions carry recommendations and context. Use when asked to refresh questions, sweep stale questions, or keep the Mini App decision queue current. Exclude for asking new questions or routine chat replies.","https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fopenclaw\u002Fida-telegram\u002Fskills\u002Frefresh-questions\u002FSKILL.md",[],[88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107],"refresh","refresh questions","questions","actions","telegram mini app","open","decision","context","use","queue","telegram","stale","chat","active","recommendations","app","keep","replies","closing","for",{"skillNo":109,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":37},"01M6M6JGW7Q0SC5B28TQ7PKE8E","https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fida-telegram-openclaw\u002Fskills\u002Frefresh-questions\u002FSKILL.md",[],[88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107],{"skillNo":114,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":37},"01M6M6J7D0ZTQ4VSS5ADRSA12E","https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fida-telegram-claude\u002Fskills\u002Frefresh-questions\u002FSKILL.md",[],[88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107],{"skillNo":119,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":37},"01M6M6EP6BK1DDN2212S7Y95G0","https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fcowork\u002Fida-telegram\u002Fskills\u002Frefresh-questions\u002FSKILL.md",[],[88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":37},"01M6G9Q8538NENA2TE2V4HPRSF","dispatch-queue","Show the user the tasks ready to dispatch, ranked with a recommendation on each, and start workers on the ones the user approves -- redirects to universal workflow template wf-dispatch-queue. Use for \"what's ready\", \"what should we dispatch\", or \"dispatch the queue\". Exclude for starting workers on named tasks without the user's choice (use dispatch) or graph truth maintenance (use reconcile).","https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fopenclaw\u002Fida\u002Fskills\u002Fdispatch-queue\u002FSKILL.md",[],[130,97,131,132,133,134,135,136,137,138,96,139,140,141,142,143,144,145,146],"dispatch","dispatch queue","workflow","tasks","graph","start","template","choice","user","reconcile","ready","maintenance","workers","show","wf","recommendation","with",{"skillNo":148,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":37},"01M6G9P9M3PQXPX3647RA5E4D0","https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fida-openclaw\u002Fskills\u002Fdispatch-queue\u002FSKILL.md",[],[130,97,131,132,133,134,135,136,137,138,96,139,140,141,142,143,144,145,146]]