[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DHQHN8GGFG0RF2PZEPAPDS":3,"skill-same:01M6DHQHN8GGFG0RF2PZEPAPDS":88},{"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":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},"01M6DHQHN8GGFG0RF2PZEPAPDS","premise-check",null,"Write or check the argument at the end of an evidence-backed report -- standard-form premises with their basis in words, warrants with their defeaters, the asker's questions answered by id -- and record the checker's verdict with its seven-line reason. Use when handing back a report, receiving one from a subagent, worker or peer, or relaying a checked claim upward. Not a fact check or requirement review, and not for extracting the argument of a text (use argument-extraction).","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\u002Fpremise-check\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"premise check","check","peer","line","id","end","worker","claim","record","back","review","evidence","use","write","text","subagent","extraction","report","2026-11-10 10:12:30",false,"---\nname: premise-check\ndescription: Write or check the argument at the end of an evidence-backed report -- standard-form premises with their basis in words, warrants with their defeaters, the asker's questions answered by id -- and record the checker's verdict with its seven-line reason. Use when handing back a report, receiving one from a subagent, worker or peer, or relaying a checked claim upward. Not a fact check or requirement review, and not for extracting the argument of a text (use argument-extraction).\n---\n\n# Premise Check\n\nA report that rests on evidence ends in an argument whose final conclusion answers the asker's questions. The writer lays it out so each step can be judged from the report alone; the checker judges every step and records why.\n\n**Standing rule: a format breach on an argument with at least one inference line is waivable on PASS and rewritten by the receiver; 0 inference lines or substantive defects require REVISE or FAIL and cannot pass or relay upward.**\n\n## Writing the Report Argument\n\nEnd the report with one fenced `argdown` block formatted per `argdown-toulmin`.\n\n````text\n```argdown\n===\nasks:\n  \u003Cask_id>: \u003Cthe asker's own words, one question>\nanswers:\n  \u003Cask_id>: \u003Cnumber of the line that answers it>\nnotes:\n  a: \u003Cpath:line, span id, task id, PR>\n===\n\n(1) \u003Cpremise>. -- \u003Cbasis phrase> ^a\n(2) \u003Cpremise quoting deciding value>. -- \u003Cbasis phrase>\n(3) \u003Cmissing premise, written in>. -- assumed, not checked here\n-- \u003Cwarrant rule>. Unless: \u003Cdefeater>; \u003Cruled out by (n) | not ruled out | not tried>. --\n(4) So, \u003Cqualifier bought by (3)>, \u003Cconclusion>.\n```\n````\n\nEvery peer message carries a fenced `argdown` block. A message making no claim (such as automated harness notices, \u002Floop wakeups, or messages making no evidence-backed claims) carries the null form:\n\n````text\n```argdown\n===\nasks: none\n===\n\n[no claim]\n```\n````\n\nThe null form clears the premise-check gate with no agent action. When an expected block is absent, the gate does not open: PASS is refused, and the receiver must return it for revision (`REVISE` \"no argument supplied\").\n\n### Basis Phrases (Closed Vocabulary)\n\nPremise lines end with their basis in words, drawn strictly from this closed vocabulary:\n\n| Phrase | Rank | Meaning |\n| - | - | - |\n| `I read it` | 3 | Primary record, diff, log, or code read directly |\n| `I did it` | 3 | Runtime command executed, test run, or artifact generated directly |\n| `attempted, failed` | 3 | Direct reproduction attempt failed with observed error |\n| `rule` | 2 | Framework axiom, project rule, or governing specification |\n| `worker reported, verdict` | 2 | Another agent's report backed by a recorded verification ID |\n| `worker reported, unchecked` | 1 | Peer writing or PKB note without a recorded verdict |\n| `assumed, not checked here` | 0 | Unchecked assumption; requires a qualifier in its conclusion |\n\n### Rules for the Block\n\n1. **The ask at the top**: Copy the asker's exact words under its immutable ID (`tg-\u003Cmsg_id>`, `\u003Ctask_id>\u002FAC\u003Cn>`).\n2. **Raw empirical observations**: Premises with an `observed` basis (`I did it`, `I read it`, rank = 3) state raw empirical observations quoting deciding values inline (`exit_code = 0`, `rank = 3`, `status: MERGED`). They never state evaluative or generalising conclusions restating an acceptance criterion (such as \"AC1 is met\" or \"behavior is correct\"). Evaluative and generalising conclusions must sit below an inference bar as claims derived from those observations.\n3. **Numbered premises**: Each line ends with `-- \u003Cbasis phrase>`, with outside values quoted.\n4. **Pointers as lettered endnotes**: Pointers live under `notes:` and are cited as `^a` on the line.\n5. **The inference line**: Starts `--`, ends `--`, on one line: warrant rule, then `Unless: \u003Cdefeater>; \u003Cstatus>`.\n6. **Chain conclusions**: Each step begins `So` and chains into subsequent steps.\n7. **Relay upward**: Relaying a report upward requires its premise-check verdict; name the line each relayed sentence restates. Read claims against their source of record before relaying. Never relay an argument with 0 inference lines or substantive defects as fact.\n8. **Method pairing line**: When an ask specifies a method, form, design, or value, the report carries a pairing line setting each specified feature beside what was done (e.g. `@file -> @.\u002Fat-test-target.md`; `read back -> Read tool`), naming each departure with its reason, else `departures: none`. A detail in a method specification is load-bearing regardless of typography (quoted, backticked, or plain) unless the ask's purpose shows it free. Rewording that preserves the construct is not a departure; exact wording is not required where the construct is preserved.\n\n## Checking a Received Report or Direction\n\n### Directions\n\nWhen an incoming direction arrives from another agent:\n\n1. Verify that every instruction and requirement derives faithfully from `## Ask` (or active user directives).\n2. Refuse (`REVISE`) unverified caller method or template prescriptions before logging deliverables. A caller may pass only `## Ask` (verbatim with ID), strategic fit\u002Fcontext, and the objective or skill invocation.\n3. Once verified, log deliverables as a frozen `## Acceptance` checklist on a PKB task before work starts.\n\n### Reports\n\nTake observed premises with a pointer as given: never open a pointer or redo the work. A PKB node or peer writing ranks as `worker reported, unchecked`. Run four tests on every inference line:\n\n| Test | Passes when | Failure looks like |\n| - | - | - |\n| **Valid** | Premises meet every condition of the warrant; conclusion is no wider than premises; construct matches and sample is adequate; all specified methods, forms, designs, and values are paired and accounted for. | Missing condition; unruled defeater; scope drift (`#scope-drift`); construct mismatch or drift (`#construct-drift`: unnamed departure or silent substitution of specified method, form, design, or value); method gap (`#method-gap`: method cannot observe what is claimed); sample inadequacy (unexplained n=1 or n=2 probes asserted as proof of representative classes). |\n| **Supported** | Each premise's basis can bear the step's stakes. Weakest premise bounds conclusion. | `worker reported, unchecked` or `assumed` on high-stakes step. |\n| **Answered** | Final conclusion answers what each ask ID needs in substance. | Narrower conclusion; relayer acceptance items substituted for ask needs. |\n| **Sufficient** | Proportionality holds: materiality, sufficiency (obvious, authority-backed, low-stakes), and necessity. A task's primary ask or acceptance criterion is never low-stakes or obvious. | Complex unbacked warrant on high-stakes step without decomposition; treating a primary ask or acceptance criterion as low-stakes or obvious. |\n\nProportionality: accept warrants as stated when obvious, authority-backed (strictly limited to user words or governing spec), backed by a cited verdict, or cheap to reverse. A task's primary ask or acceptance criterion is never low-stakes or obvious. Send back for decomposition only when complex, unbacked, or high-stakes.\n\n#### Fidelity Procedure\n\nWhen checking an inference line or deliverable where the ask specifies a method, form, design, or value:\n\n1. **Extract specified features**: Read `## Ask` for any specified method, form, design, or value. Details in method specifications are load-bearing regardless of typography (quoted, backticked, or plain) unless the ask's purpose shows them free.\n2. **Check the pairing line**: Verify the report pairs each specified feature with what was done.\n3. **Judge departures**:\n   - An unnamed departure (silent substitution of a specified method, form, design, or value) fails `Valid` with `#construct-drift` or `#method-gap`.\n   - A block that silently swaps a specified form cannot PASS; return for revision (`REVISE`).\n   - Rewording that preserves the construct and distinction passes; do not require verbatim wording outside specified forms or methods.\n\n## Recording the Verdict\n\n- **PASS**: Every inference holds, every ask is answered, the weakest basis bears the stakes, and at least one inference line is tested (>= 1). Format-only defects on a substantively sound argument with >= 1 inference line are waived under `Waived:` and rewritten into standard form by the receiver before relaying upward.\n- **REVISE**: Name the line, defect tag (`#missing`, `#scope-drift`, `#conflict`, `#unanswered`, `#undercut`, `#construct-drift`, `#method-gap`), and remedy. Mandatory for substantive defects or 0 inference lines (bare assertions); cannot be relayed upward as fact. Return to sender.\n- **FAIL**: Conclusion does not answer the ask or contradicts evidence. Mandatory for substantive defects; cannot be relayed upward as fact.\n\nWrite the reason as the seven keyed lines:\n\n```text\nJudged: \u003Cclaim id>; asks \u003Cask id>, \u003Cask id>\nValid: (n) holds -- \u003Crule and why it yields (n) here>\nSupported: weakest \u003Cbasis phrase> -- (\u003Cpremise n>) \u003Creason>\nAnswered: \u003Cask id> ← (n)\nSufficient: (n) material; \u003Cobvious | authority-backed | low-stakes>; no objection\nWaived: none | \u003Cformat item> -- \u003Cjustification>\nRelay: \"\u003Csentence to relay>\" ← (n) | none\n```\n\nFor arguments with multiple inference lines, all yielded conclusions must be accounted for under `Valid:`--either via multiple `Valid:` lines, indented continuation lines, semicolon clauses (`(n) holds -- ...; (m) holds -- ...`), or grouped references (`(n), (m) holds -- ...` or `(n) and (m) hold -- ...`).\n\nFormat items: `block`, `numbering`, `endnotes`, `basis wording`, `ask wording`, `layout`.\n\nRecord the verdict:\n\n```bash\nuv run --project \u003Cplugin-dir> python \u003Cplugin-dir>\u002Fskills\u002Fpremise-check\u002Fscripts\u002Fverdict.py --claim \u003Cclaim_id> --verdict \u003CPASS|REVISE|FAIL> --reason-file \u003Cpath>\n```\n\nThe recorder refuses a PASS whose reason misses a test line or ask ID, contradicts the block, or fails machine checks (syntax error, orphan statement, misaimed undercut); on refusal, actionable errors are emitted to stderr while keeping the gate armed.\n","# Premise Check\n\nA report that rests on evidence ends in an argument whose final conclusion answers the asker's questions. The writer lays it out so each step can be judged from the report alone; the checker judges every step and records why.\n\n**Standing rule: a format breach on an argument with at least one inference line is waivable on PASS and rewritten by the receiver; 0 inference lines or substantive defects require REVISE or FAIL and cannot pass or relay upward.**\n\n## Writing the Report Argument\n\nEnd the report with one fenced `argdown` block formatted per `argdown-toulmin`.\n\n````text\n```argdown\n===\nasks:\n  \u003Cask_id>: \u003Cthe asker's own words, one question>\nanswers:\n  \u003Cask_id>: \u003Cnumber of the line that answers it>\nnotes:\n  a: \u003Cpath:line, span id, task id, PR>\n===\n\n(1) \u003Cpremise>. -- \u003Cbasis phrase> ^a\n(2) \u003Cpremise quoting deciding value>. -- \u003Cbasis phrase>\n(3) \u003Cmissing premise, written in>. -- assumed, not checked here\n-- \u003Cwarrant rule>. Unless: \u003Cdefeater>; \u003Cruled out by (n) | not ruled out | not tried>. --\n(4) So, \u003Cqualifier bought by (3)>, \u003Cconclusion>.\n```\n````\n\nEvery peer message carries a fenced `argdown` block. A message making no claim (such as automated harness notices, \u002Floop wakeups, or messages making no evidence-backed claims) carries the null form:\n\n````text\n```argdown\n===\nasks: none\n===\n\n[no claim]\n```\n````\n\nThe null form clears the premise-check gate with no agent action. When an expected block is absent, the gate does not open: PASS is refused, and the receiver must return it for revision (`REVISE` \"no argument supplied\").\n\n### Basis Phrases (Closed Vocabulary)\n\nPremise lines end with their basis in words, drawn strictly from this closed vocabulary:\n\n| Phrase | Rank | Meaning |\n| - | - | - |\n| `I read it` | 3 | Primary record, diff, log, or code read directly |\n| `I did it` | 3 | Runtime command executed, test run, or artifact generated directly |\n| `attempted, failed` | 3 | Direct reproduction attempt failed with observed error |\n| `rule` | 2 | Framework axiom, project rule, or governing specification |\n| `worker reported, verdict` | 2 | Another agent's report backed by a recorded verification ID |\n| `worker reported, unchecked` | 1 | Peer writing or PKB note without a recorded verdict |\n| `assumed, not checked here` | 0 | Unchecked assumption; requires a qualifier in its conclusion |\n\n### Rules for the Block\n\n1. **The ask at the top**: Copy the asker's exact words under its immutable ID (`tg-\u003Cmsg_id>`, `\u003Ctask_id>\u002FAC\u003Cn>`).\n2. **Raw empirical observations**: Premises with an `observed` basis (`I did it`, `I read it`, rank = 3) state raw empirical observations quoting deciding values inline (`exit_code = 0`, `rank = 3`, `status: MERGED`). They never state evaluative or generalising conclusions restating an acceptance criterion (such as \"AC1 is met\" or \"behavior is correct\"). Evaluative and generalising conclusions must sit below an inference bar as claims derived from those observations.\n3. **Numbered premises**: Each line ends with `-- \u003Cbasis phrase>`, with outside values quoted.\n4. **Pointers as lettered endnotes**: Pointers live under `notes:` and are cited as `^a` on the line.\n5. **The inference line**: Starts `--`, ends `--`, on one line: warrant rule, then `Unless: \u003Cdefeater>; \u003Cstatus>`.\n6. **Chain conclusions**: Each step begins `So` and chains into subsequent steps.\n7. **Relay upward**: Relaying a report upward requires its premise-check verdict; name the line each relayed sentence restates. Read claims against their source of record before relaying. Never relay an argument with 0 inference lines or substantive defects as fact.\n8. **Method pairing line**: When an ask specifies a method, form, design, or value, the report carries a pairing line setting each specified feature beside what was done (e.g. `@file -> @.\u002Fat-test-target.md`; `read back -> Read tool`), naming each departure with its reason, else `departures: none`. A detail in a method specification is load-bearing regardless of typography (quoted, backticked, or plain) unless the ask's purpose shows it free. Rewording that preserves the construct is not a departure; exact wording is not required where the construct is preserved.\n\n## Checking a Received Report or Direction\n\n### Directions\n\nWhen an incoming direction arrives from another agent:\n\n1. Verify that every instruction and requirement derives faithfully from `## Ask` (or active user directives).\n2. Refuse (`REVISE`) unverified caller method or template prescriptions before logging deliverables. A caller may pass only `## Ask` (verbatim with ID), strategic fit\u002Fcontext, and the objective or skill invocation.\n3. Once verified, log deliverables as a frozen `## Acceptance` checklist on a PKB task before work starts.\n\n### Reports\n\nTake observed premises with a pointer as given: never open a pointer or redo the work. A PKB node or peer writing ranks as `worker reported, unchecked`. Run four tests on every inference line:\n\n| Test | Passes when | Failure looks like |\n| - | - | - |\n| **Valid** | Premises meet every condition of the warrant; conclusion is no wider than premises; construct matches and sample is adequate; all specified methods, forms, designs, and values are paired and accounted for. | Missing condition; unruled defeater; scope drift (`#scope-drift`); construct mismatch or drift (`#construct-drift`: unnamed departure or silent substitution of specified method, form, design, or value); method gap (`#method-gap`: method cannot observe what is claimed); sample inadequacy (unexplained n=1 or n=2 probes asserted as proof of representative classes). |\n| **Supported** | Each premise's basis can bear the step's stakes. Weakest premise bounds conclusion. | `worker reported, unchecked` or `assumed` on high-stakes step. |\n| **Answered** | Final conclusion answers what each ask ID needs in substance. | Narrower conclusion; relayer acceptance items substituted for ask needs. |\n| **Sufficient** | Proportionality holds: materiality, sufficiency (obvious, authority-backed, low-stakes), and necessity. A task's primary ask or acceptance criterion is never low-stakes or obvious. | Complex unbacked warrant on high-stakes step without decomposition; treating a primary ask or acceptance criterion as low-stakes or obvious. |\n\nProportionality: accept warrants as stated when obvious, authority-backed (strictly limited to user words or governing spec), backed by a cited verdict, or cheap to reverse. A task's primary ask or acceptance criterion is never low-stakes or obvious. Send back for decomposition only when complex, unbacked, or high-stakes.\n\n#### Fidelity Procedure\n\nWhen checking an inference line or deliverable where the ask specifies a method, form, design, or value:\n\n1. **Extract specified features**: Read `## Ask` for any specified method, form, design, or value. Details in method specifications are load-bearing regardless of typography (quoted, backticked, or plain) unless the ask's purpose shows them free.\n2. **Check the pairing line**: Verify the report pairs each specified feature with what was done.\n3. **Judge departures**:\n   - An unnamed departure (silent substitution of a specified method, form, design, or value) fails `Valid` with `#construct-drift` or `#method-gap`.\n   - A block that silently swaps a specified form cannot PASS; return for revision (`REVISE`).\n   - Rewording that preserves the construct and distinction passes; do not require verbatim wording outside specified forms or methods.\n\n## Recording the Verdict\n\n- **PASS**: Every inference holds, every ask is answered, the weakest basis bears the stakes, and at least one inference line is tested (>= 1). Format-only defects on a substantively sound argument with >= 1 inference line are waived under `Waived:` and rewritten into standard form by the receiver before relaying upward.\n- **REVISE**: Name the line, defect tag (`#missing`, `#scope-drift`, `#conflict`, `#unanswered`, `#undercut`, `#construct-drift`, `#method-gap`), and remedy. Mandatory for substantive defects or 0 inference lines (bare assertions); cannot be relayed upward as fact. Return to sender.\n- **FAIL**: Conclusion does not answer the ask or contradicts evidence. Mandatory for substantive defects; cannot be relayed upward as fact.\n\nWrite the reason as the seven keyed lines:\n\n```text\nJudged: \u003Cclaim id>; asks \u003Cask id>, \u003Cask id>\nValid: (n) holds -- \u003Crule and why it yields (n) here>\nSupported: weakest \u003Cbasis phrase> -- (\u003Cpremise n>) \u003Creason>\nAnswered: \u003Cask id> ← (n)\nSufficient: (n) material; \u003Cobvious | authority-backed | low-stakes>; no objection\nWaived: none | \u003Cformat item> -- \u003Cjustification>\nRelay: \"\u003Csentence to relay>\" ← (n) | none\n```\n\nFor arguments with multiple inference lines, all yielded conclusions must be accounted for under `Valid:`--either via multiple `Valid:` lines, indented continuation lines, semicolon clauses (`(n) holds -- ...; (m) holds -- ...`), or grouped references (`(n), (m) holds -- ...` or `(n) and (m) hold -- ...`).\n\nFormat items: `block`, `numbering`, `endnotes`, `basis wording`, `ask wording`, `layout`.\n\nRecord the verdict:\n\n```bash\nuv run --project \u003Cplugin-dir> python \u003Cplugin-dir>\u002Fskills\u002Fpremise-check\u002Fscripts\u002Fverdict.py --claim \u003Cclaim_id> --verdict \u003CPASS|REVISE|FAIL> --reason-file \u003Cpath>\n```\n\nThe recorder refuses a PASS whose reason misses a test line or ask ID, contradicts the block, or fails machine checks (syntax error, orphan statement, misaimed undercut); on refusal, actionable errors are emitted to stderr while keeping the gate armed.\n",{"name":5,"description":7},"main","22a4e466ac352d09f636273685845a312ee07a15","plugins\u002Fida\u002Fskills\u002Fpremise-check",3,"https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps","https:\u002F\u002Fgithub.com\u002Fnicsuzor","https:\u002F\u002Fnic.suzor.net\u002F","2026-11-13 21:19:25",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add nicsuzor\u002FacademicOps --skill premise-check",{"tool":56,"command":57},"bunx","bunx skills add nicsuzor\u002FacademicOps --skill premise-check",{"tool":59,"command":60},"pnpm","pnpm dlx skills add nicsuzor\u002FacademicOps --skill premise-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fplugins\u002Fida\u002Fskills\u002Fpremise-check\u002FSKILL.md",true,[64,70,74,78,82],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fchecker-reason.md","REFERENCE","参考文档",3071,"https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fplugins\u002Fida\u002Fskills\u002Fpremise-check\u002Freferences\u002Fchecker-reason.md",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Freport-form.md",3776,"https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fplugins\u002Fida\u002Fskills\u002Fpremise-check\u002Freferences\u002Freport-form.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fvocabulary.toml",1492,"https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fplugins\u002Fida\u002Fskills\u002Fpremise-check\u002Freferences\u002Fvocabulary.toml",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"resources\u002Fimplementation-playbook.md",21125,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fbacktesting-frameworks\u002Fresources\u002Fimplementation-playbook.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fverdict.py","SCRIPT","脚本",1211,"https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fplugins\u002Fida\u002Fskills\u002Fpremise-check\u002Fscripts\u002Fverdict.py",[89,115,120,125,130,154],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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",[],[96,97,98,99,100,101,102,103,31,104,105,106,107,108,109,110,111,112,113,114],"refresh","refresh questions","questions","actions","telegram mini app","open","decision","context","queue","telegram","stale","chat","active","recommendations","app","keep","replies","closing","for",{"skillNo":116,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":37},"01M6M6JGW7Q0SC5B28TQ7PKE8E","https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fida-telegram-openclaw\u002Fskills\u002Frefresh-questions\u002FSKILL.md",[],[96,97,98,99,100,101,102,103,31,104,105,106,107,108,109,110,111,112,113,114],{"skillNo":121,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":37},"01M6M6J7D0ZTQ4VSS5ADRSA12E","https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fida-telegram-claude\u002Fskills\u002Frefresh-questions\u002FSKILL.md",[],[96,97,98,99,100,101,102,103,31,104,105,106,107,108,109,110,111,112,113,114],{"skillNo":126,"name":91,"nameZh":6,"description":92,"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},"01M6M6EP6BK1DDN2212S7Y95G0","https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fcowork\u002Fida-telegram\u002Fskills\u002Frefresh-questions\u002FSKILL.md",[],[96,97,98,99,100,101,102,103,31,104,105,106,107,108,109,110,111,112,113,114],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"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",[],[137,104,138,139,140,141,142,143,144,145,31,146,147,148,149,150,151,152,153],"dispatch","dispatch queue","workflow","tasks","graph","start","template","choice","user","reconcile","ready","maintenance","workers","show","wf","recommendation","with",{"skillNo":155,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":37},"01M6G9P9M3PQXPX3647RA5E4D0","https:\u002F\u002Fgithub.com\u002Fnicsuzor\u002FacademicOps\u002Fblob\u002Fmain\u002Fida-openclaw\u002Fskills\u002Fdispatch-queue\u002FSKILL.md",[],[137,104,138,139,140,141,142,143,144,145,31,146,147,148,149,150,151,152,153]]