[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVQ729VHNBS70FP0MZRZ6F":3,"skill-same:01M6JVQ729VHNBS70FP0MZRZ6F":71},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6JVQ729VHNBS70FP0MZRZ6F","first-principles-review",null,"Use when asked for first-principles or Occam's-razor review, or when high-risk decisions involve competing constraints, fallback growth, duplicate owners, or architecture direction risk. Ordinary bug fixes stay on the fast path.","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\u002FGanyuanRan\u002FAegis\u002Fskills\u002Ffirst-principles-review\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"review","first principles review","first","principles","first principles","when","fixes","for","path","high","razor","direction","duplicate","first-principles","fallback","bug","use","growth","decisions","owners","risk","fast","architecture","2026-11-10 10:12:30",false,"---\nname: first-principles-review\ndescription: \"Use when asked for first-principles or Occam's-razor review, or when high-risk decisions involve competing constraints, fallback growth, duplicate owners, or architecture direction risk. Ordinary bug fixes stay on the fast path.\"\n---\n\n# First Principles Review\n\n## Purpose\n\nUse this as a lightweight decision review before another Aegis workflow makes a\ndirectional choice. It is a compositional skill, not a standalone workflow.\n\nDo not replace `brainstorming`, `systematic-debugging`, `writing-plans`,\n`requesting-code-review`, or `verification-before-completion`. Use it to clean\nthe decision surface those skills will act on.\n\nWhen this review materially changes the direction, surface `Aegis Visibility`\nin natural prose: name the first principle, dropped assumption, smallest\nsufficient path, or owner \u002F retirement falsifier that changed the decision.\nKeep it advisory and task-specific; do not turn the lens into approval\nauthority or a generic skill trace.\n\n## Use When\n\n- The user asks for first principles, first-principles thinking, or Occam's\n  razor.\n- A design, plan, or fix has multiple plausible paths and unclear selection\n  criteria.\n- The task has ambiguous goals, competing constraints, or product\u002Farchitecture\n  direction risk.\n- Debugging is drifting into repeated fixes, fallback growth, duplicate owners,\n  consumer-side patches, or \"just add another branch\" reasoning.\n- A review finds that the implementation may be locally correct but directionally\n  wrong.\n\n## Do Not Use\n\n- Simple Q&A, status checks, tiny wording\u002Fconfig edits, or clearly bounded\n  single-owner changes.\n- Mechanical execution of an approved plan unless a new directional conflict\n  appears.\n- As a required step for every task, every turn, or every TDD cycle.\n\n## Five-Line Review\n\nCheck the agreed goal for omissions and unsupported additions, including\nquantities, exclusions, relationships and conditions. Review criteria come from\nauthorized requirements; this lens cannot add them or veto an authorized\ntransformation merely because its form differs.\n\nAnswer only what is needed, usually in five short lines:\n\n```text\nFirst Principle: What irreducible outcome must this satisfy?\nNon-negotiables: What constraints cannot be broken?\nAssumptions to Drop: What is habit, inherited shape, or unproven preference?\nSmallest Sufficient Path: What is the least complex path that satisfies the first principle?\nEscalation Signal: What finding would require spec\u002Fdesign\u002Farchitecture review?\n```\n\nWhen the direction depends on a new mechanism or an unfamiliar domain, insert\none optional line between path and escalation:\n\n```text\nKnown Prior Art: proven external pattern worth adopting or adapting to project\nconstraints (cite source), or `unknown` when precedent cannot be verified here\n```\n\nFor repairs and optimization, require evidence for the cause or bottleneck\nbefore retaining a solution. Resolve unknowns that could change the choice;\nexperiments may precede that decision. \"Smallest\" means the least intervention\ncovering relevant causal paths while preserving required behavior, not the\nsmallest diff or fewest owners. Independent causes may need separate repairs;\na shared carrier does not prove a shared cause. Use systematic debugging when\ncausal coverage is unresolved; no extra checklist is required for a settled case:\n\n```text\nMinimality Check:\n- Smallest textual diff:\n- Correct owner:\n- Bug class fixed:\n- New branch\u002Ffallback added:\n- Old path retired or scheduled:\n- Verdict: sufficient repair | local patch | needs first-principles review\n```\n\n## Decision Hygiene Review\n\nUse this escalation only when a design, fix, or plan needs endorsement before it\nis written into a spec or implementation plan.\n\nEscalate from the five-line review when any of these risk signals appear:\n\n- multiple plausible paths and no clear selection criteria\n- a new owner, duplicate owner, fallback, adapter, or compat-only carrier\n- an old path that may need delete-first handling or a retirement trigger\n- an unverified assumption that the proposal depends on\n- user language such as \"more elegant\", \"long-term stable\", \"first\n  principles\", or \"Occam\"\n- a plan could encode the wrong owner, abstraction, compatibility boundary, or\n  retirement schedule\n- an existing object, behavior, responsibility, contract, or relationship may\n  be reinterpreted, narrowed, replaced, or retired, and the proposal could lose\n  a legitimate role or explicit reference while removing invalid authority\n\nUse this compact shape:\n\n```text\nFirst-principles invariants:\n- Non-negotiable goal:\n- Non-negotiable constraints:\n- Historical assumptions to delete:\n\nBounded preservation reminder:\n- Evidence-backed behavior that must remain correct:\n- Highest-risk counterexample:\n- Material unknown \u002F uninspected surface:\n- Known explicit anchors \u002F upstream-downstream refs and disposition:\n- Role-before-value ambiguity, if any:\n\nOwner \u002F retirement matrix:\n- New canonical owner:\n- Old owner:\n- Compat-only carrier:\n- Delete-first \u002F retirement trigger:\n\nFalsification matrix (evaluate in order; stop at the first failing gate):\n- Gate 0 - Premise evidence (stage-graded): design stage accepts spec\u002Flogic\n  refs; implementation\u002Fruntime stage requires log, telemetry, or test\n  evidence. No evidence -> park as watch-listed, do not enter value\n  evaluation.\n- Gate 1 - Decidability: no obtainable evidence to judge it -> park as a\n  watched falsifier, do not act.\n- Gate 2 - Value (any one): lowers future fix probability \u002F shrinks the\n  solution set \u002F exposes a missing actionable acceptance criterion \u002F the same\n  broken assumption is reused elsewhere. Passing here still requires\n  gates 3-5.\n- Gate 3 - Cost match: change cost vs business priority, costed at the\n  current stage; a valid but deferred counterexample is recorded in the owner\n  doc, never parked orally.\n- Gate 4 - Goal regression: the constrained solution still meets the original\n  goal; re-read the accepted-constraint list at existing checkpoints (design\n  review, plan approval, pre-completion verification).\n- Gate 5 - Minimize then classify: boundary-shaped destructive claims must be\n  minimized first; premise attacks classify as destructive directly.\n  Classes: destructive (refactor\u002Fretirement track) | supplementary (boundary\n  constraint) | watch-listed (falsifier). Conflicting counterexamples are\n  decided by business-goal ranking, never by stacking constraints.\n- Gate 6 - Adoption trace: the cheapest checkable form (regression test for\n  destructive; contract, assertion, or checklist line for supplementary),\n  written into the existing owner doc.\n\nVerdict:\n- Adopt \u002F revise \u002F reject \u002F needs evidence:\n- Blocking gaps:\n- Next evidence:\n```\n\n## Architecture Integrity Lens\n\nUse this narrower lens when a proposal is executable but may still encode the\nwrong owner, abstraction, contract boundary, or retirement path. It is advisory\nmethod-pack output and may be embedded inside `Decision Hygiene Review` when\nthat is enough.\n\nTrigger it when any of these appear before approach selection, task\ndecomposition, review, or completion-risk reporting:\n\n- responsibilities may overlap or a canonical owner is unclear\n- the smallest diff adds a caller-side fallback, guard, adapter, or compat-only\n  carrier\n- an existing source-of-truth or contract could solve the class of problem at a\n  higher level\n- a stale owner, fallback, or old path may keep carrying real logic\n- the work makes a long-term stability, \"cleaner architecture\", or\n  higher-level simplification claim\n\nUse this compact shape:\n\n```text\nArchitecture Integrity Lens:\n- Invariant: What must remain true for the system to be coherent?\n- Canonical owner \u002F contract: Which owner, contract, or source-of-truth should carry the behavior?\n- Responsibility overlap: What duplicate owner, caller-side patch, fallback, or stale path might still carry real logic?\n- Higher-level simplification: Can the problem be solved at the owner \u002F contract \u002F source-of-truth layer instead of by another local branch?\n- Retirement \u002F falsifier: What old path retires, or what evidence would disprove this architecture judgment?\n- Responsibility \u002F capability boundary: Which invalid authority retires, and\n  does the same carrier still serve a separately evidenced legitimate role?\n- Verdict: proceed | revise design | split owner | return to baseline | needs ADR\u002Fbaseline sync\n```\n\n`Bounded preservation reminder` is a risk-triggered reasoning aid, not a\nuniversal artifact or an exhaustive behavior inventory. Inspect the smallest\nrelevant contract, consumer, test, or history evidence. Preserve, rebind,\nretire, or reject each known explicit reference; state unresolved relationships\nas unknown instead of re-inferring them or claiming semantic completeness. The\nMethod Pack does not build an authoritative relationship graph, prove\nreferential integrity or input lineage, calculate complete behavior coverage,\nor issue a runtime gate.\n\nDo not run this lens for every low-risk task. If it does not change the\ndecision surface, return to the active workflow immediately.\n\n## Composition\n\n- With `brainstorming`: run before approach selection when the request is broad,\n  ambiguous, likely to inherit a poor product shape, or involves owner \u002F\n  retirement \u002F fallback \u002F adapter risk. Use `Decision Hygiene Review` or the\n  narrower `Architecture Integrity Lens` before recommending or selecting an\n  approach when those signals appear.\n- With `systematic-debugging`: run after evidence shows repeated fixes, fallback\n  growth, duplicate owners, or consumer-side patching.\n- With `writing-plans`: run before task decomposition when the plan could encode\n  the wrong owner, abstraction, compatibility boundary, fallback, adapter, or\n  retirement schedule. If the approved spec did not already cover this, use\n  `Decision Hygiene Review` or the `Architecture Integrity Lens` before writing\n  tasks.\n- With `requesting-code-review`: run when review should check direction and\n  owner integrity, not just code quality.\n- With `verification-before-completion`: use only to name residual directional\n  risk. It does not grant completion authority.\n\n## Boundaries\n\n- Prefer evidence from current project files, baseline docs, tests, logs, and\n  user requirements. If evidence is missing, mark the line as unknown rather\n  than inventing a principle.\n- Keep the result advisory. This skill may recommend escalation, but it does\n  not create authoritative `GateDecision`, `PolicySnapshot`, or completion\n  authority.\n- If the five-line review does not change the decision surface, return to the\n  active workflow immediately.\n","# First Principles Review\n\n## Purpose\n\nUse this as a lightweight decision review before another Aegis workflow makes a\ndirectional choice. It is a compositional skill, not a standalone workflow.\n\nDo not replace `brainstorming`, `systematic-debugging`, `writing-plans`,\n`requesting-code-review`, or `verification-before-completion`. Use it to clean\nthe decision surface those skills will act on.\n\nWhen this review materially changes the direction, surface `Aegis Visibility`\nin natural prose: name the first principle, dropped assumption, smallest\nsufficient path, or owner \u002F retirement falsifier that changed the decision.\nKeep it advisory and task-specific; do not turn the lens into approval\nauthority or a generic skill trace.\n\n## Use When\n\n- The user asks for first principles, first-principles thinking, or Occam's\n  razor.\n- A design, plan, or fix has multiple plausible paths and unclear selection\n  criteria.\n- The task has ambiguous goals, competing constraints, or product\u002Farchitecture\n  direction risk.\n- Debugging is drifting into repeated fixes, fallback growth, duplicate owners,\n  consumer-side patches, or \"just add another branch\" reasoning.\n- A review finds that the implementation may be locally correct but directionally\n  wrong.\n\n## Do Not Use\n\n- Simple Q&A, status checks, tiny wording\u002Fconfig edits, or clearly bounded\n  single-owner changes.\n- Mechanical execution of an approved plan unless a new directional conflict\n  appears.\n- As a required step for every task, every turn, or every TDD cycle.\n\n## Five-Line Review\n\nCheck the agreed goal for omissions and unsupported additions, including\nquantities, exclusions, relationships and conditions. Review criteria come from\nauthorized requirements; this lens cannot add them or veto an authorized\ntransformation merely because its form differs.\n\nAnswer only what is needed, usually in five short lines:\n\n```text\nFirst Principle: What irreducible outcome must this satisfy?\nNon-negotiables: What constraints cannot be broken?\nAssumptions to Drop: What is habit, inherited shape, or unproven preference?\nSmallest Sufficient Path: What is the least complex path that satisfies the first principle?\nEscalation Signal: What finding would require spec\u002Fdesign\u002Farchitecture review?\n```\n\nWhen the direction depends on a new mechanism or an unfamiliar domain, insert\none optional line between path and escalation:\n\n```text\nKnown Prior Art: proven external pattern worth adopting or adapting to project\nconstraints (cite source), or `unknown` when precedent cannot be verified here\n```\n\nFor repairs and optimization, require evidence for the cause or bottleneck\nbefore retaining a solution. Resolve unknowns that could change the choice;\nexperiments may precede that decision. \"Smallest\" means the least intervention\ncovering relevant causal paths while preserving required behavior, not the\nsmallest diff or fewest owners. Independent causes may need separate repairs;\na shared carrier does not prove a shared cause. Use systematic debugging when\ncausal coverage is unresolved; no extra checklist is required for a settled case:\n\n```text\nMinimality Check:\n- Smallest textual diff:\n- Correct owner:\n- Bug class fixed:\n- New branch\u002Ffallback added:\n- Old path retired or scheduled:\n- Verdict: sufficient repair | local patch | needs first-principles review\n```\n\n## Decision Hygiene Review\n\nUse this escalation only when a design, fix, or plan needs endorsement before it\nis written into a spec or implementation plan.\n\nEscalate from the five-line review when any of these risk signals appear:\n\n- multiple plausible paths and no clear selection criteria\n- a new owner, duplicate owner, fallback, adapter, or compat-only carrier\n- an old path that may need delete-first handling or a retirement trigger\n- an unverified assumption that the proposal depends on\n- user language such as \"more elegant\", \"long-term stable\", \"first\n  principles\", or \"Occam\"\n- a plan could encode the wrong owner, abstraction, compatibility boundary, or\n  retirement schedule\n- an existing object, behavior, responsibility, contract, or relationship may\n  be reinterpreted, narrowed, replaced, or retired, and the proposal could lose\n  a legitimate role or explicit reference while removing invalid authority\n\nUse this compact shape:\n\n```text\nFirst-principles invariants:\n- Non-negotiable goal:\n- Non-negotiable constraints:\n- Historical assumptions to delete:\n\nBounded preservation reminder:\n- Evidence-backed behavior that must remain correct:\n- Highest-risk counterexample:\n- Material unknown \u002F uninspected surface:\n- Known explicit anchors \u002F upstream-downstream refs and disposition:\n- Role-before-value ambiguity, if any:\n\nOwner \u002F retirement matrix:\n- New canonical owner:\n- Old owner:\n- Compat-only carrier:\n- Delete-first \u002F retirement trigger:\n\nFalsification matrix (evaluate in order; stop at the first failing gate):\n- Gate 0 - Premise evidence (stage-graded): design stage accepts spec\u002Flogic\n  refs; implementation\u002Fruntime stage requires log, telemetry, or test\n  evidence. No evidence -> park as watch-listed, do not enter value\n  evaluation.\n- Gate 1 - Decidability: no obtainable evidence to judge it -> park as a\n  watched falsifier, do not act.\n- Gate 2 - Value (any one): lowers future fix probability \u002F shrinks the\n  solution set \u002F exposes a missing actionable acceptance criterion \u002F the same\n  broken assumption is reused elsewhere. Passing here still requires\n  gates 3-5.\n- Gate 3 - Cost match: change cost vs business priority, costed at the\n  current stage; a valid but deferred counterexample is recorded in the owner\n  doc, never parked orally.\n- Gate 4 - Goal regression: the constrained solution still meets the original\n  goal; re-read the accepted-constraint list at existing checkpoints (design\n  review, plan approval, pre-completion verification).\n- Gate 5 - Minimize then classify: boundary-shaped destructive claims must be\n  minimized first; premise attacks classify as destructive directly.\n  Classes: destructive (refactor\u002Fretirement track) | supplementary (boundary\n  constraint) | watch-listed (falsifier). Conflicting counterexamples are\n  decided by business-goal ranking, never by stacking constraints.\n- Gate 6 - Adoption trace: the cheapest checkable form (regression test for\n  destructive; contract, assertion, or checklist line for supplementary),\n  written into the existing owner doc.\n\nVerdict:\n- Adopt \u002F revise \u002F reject \u002F needs evidence:\n- Blocking gaps:\n- Next evidence:\n```\n\n## Architecture Integrity Lens\n\nUse this narrower lens when a proposal is executable but may still encode the\nwrong owner, abstraction, contract boundary, or retirement path. It is advisory\nmethod-pack output and may be embedded inside `Decision Hygiene Review` when\nthat is enough.\n\nTrigger it when any of these appear before approach selection, task\ndecomposition, review, or completion-risk reporting:\n\n- responsibilities may overlap or a canonical owner is unclear\n- the smallest diff adds a caller-side fallback, guard, adapter, or compat-only\n  carrier\n- an existing source-of-truth or contract could solve the class of problem at a\n  higher level\n- a stale owner, fallback, or old path may keep carrying real logic\n- the work makes a long-term stability, \"cleaner architecture\", or\n  higher-level simplification claim\n\nUse this compact shape:\n\n```text\nArchitecture Integrity Lens:\n- Invariant: What must remain true for the system to be coherent?\n- Canonical owner \u002F contract: Which owner, contract, or source-of-truth should carry the behavior?\n- Responsibility overlap: What duplicate owner, caller-side patch, fallback, or stale path might still carry real logic?\n- Higher-level simplification: Can the problem be solved at the owner \u002F contract \u002F source-of-truth layer instead of by another local branch?\n- Retirement \u002F falsifier: What old path retires, or what evidence would disprove this architecture judgment?\n- Responsibility \u002F capability boundary: Which invalid authority retires, and\n  does the same carrier still serve a separately evidenced legitimate role?\n- Verdict: proceed | revise design | split owner | return to baseline | needs ADR\u002Fbaseline sync\n```\n\n`Bounded preservation reminder` is a risk-triggered reasoning aid, not a\nuniversal artifact or an exhaustive behavior inventory. Inspect the smallest\nrelevant contract, consumer, test, or history evidence. Preserve, rebind,\nretire, or reject each known explicit reference; state unresolved relationships\nas unknown instead of re-inferring them or claiming semantic completeness. The\nMethod Pack does not build an authoritative relationship graph, prove\nreferential integrity or input lineage, calculate complete behavior coverage,\nor issue a runtime gate.\n\nDo not run this lens for every low-risk task. If it does not change the\ndecision surface, return to the active workflow immediately.\n\n## Composition\n\n- With `brainstorming`: run before approach selection when the request is broad,\n  ambiguous, likely to inherit a poor product shape, or involves owner \u002F\n  retirement \u002F fallback \u002F adapter risk. Use `Decision Hygiene Review` or the\n  narrower `Architecture Integrity Lens` before recommending or selecting an\n  approach when those signals appear.\n- With `systematic-debugging`: run after evidence shows repeated fixes, fallback\n  growth, duplicate owners, or consumer-side patching.\n- With `writing-plans`: run before task decomposition when the plan could encode\n  the wrong owner, abstraction, compatibility boundary, fallback, adapter, or\n  retirement schedule. If the approved spec did not already cover this, use\n  `Decision Hygiene Review` or the `Architecture Integrity Lens` before writing\n  tasks.\n- With `requesting-code-review`: run when review should check direction and\n  owner integrity, not just code quality.\n- With `verification-before-completion`: use only to name residual directional\n  risk. It does not grant completion authority.\n\n## Boundaries\n\n- Prefer evidence from current project files, baseline docs, tests, logs, and\n  user requirements. If evidence is missing, mark the line as unknown rather\n  than inventing a principle.\n- Keep the result advisory. This skill may recommend escalation, but it does\n  not create authoritative `GateDecision`, `PolicySnapshot`, or completion\n  authority.\n- If the five-line review does not change the decision surface, return to the\n  active workflow immediately.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Ffirst-principles-review",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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill first-principles-review",{"tool":63,"command":64},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill first-principles-review",{"tool":66,"command":67},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill first-principles-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Ffirst-principles-review\u002FSKILL.md",true,[],[72,82,90,98,106,114],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":81},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":81},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":81},"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":81},"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":81},"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",[],[]]