[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVPWDVXEC0AT6DBMV7KBDD":3,"skill-same:01M6JVPWDVXEC0AT6DBMV7KBDD":69},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6JVPWDVXEC0AT6DBMV7KBDD","executing-plans",null,"Use when executing a written implementation plan across sessions or with review checkpoints. Small or single-slice plans stay inline. For same-session independent tasks, use subagent-driven-development instead.","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\u002Fexecuting-plans\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"executing plans","plans","across","when","slice","single","implementation plan","inline","for","checkpoints","with","driven","review","implementation","use","session","subagent","plan","development","tasks","sessions","2026-11-10 10:12:30",false,"---\nname: executing-plans\ndescription: \"Use when executing a written implementation plan across sessions or with review checkpoints. Small or single-slice plans stay inline. For same-session independent tasks, use subagent-driven-development instead.\"\n---\n\n# Executing Plans\n\n## Overview\n\nLoad plan, review critically, execute all tasks, report when complete.\n\n**Announce at start:** \"I'm using the executing-plans skill to implement this plan.\"\n\nFor non-trivial execution, include `Aegis Visibility`: briefly tie the active\nslice to its plan, checkpoint, drift or verification boundary. At completion,\npass plan adherence, evidence, complexity and residual risk to\n`verification-before-completion` for the unified receipt.\n\nIf subagents are available and the plan has genuinely independent tasks,\nprefer `subagent-driven-development`; lack of subagent support does not block\ninline execution. Same-task agents share one workspace, and the coordinator\nremains the only Git mutation owner.\n\n## The Process\n\n### Step 1: Load and Review Plan\n1. Read plan file\n2. If the plan or active checkpoint includes an `Execution Readiness View`,\n   read it before implementation and compare the plan against its intent lock,\n   scope fence, baseline lock, owner \u002F contract constraints, compatibility\n   boundary, retirement boundary, test obligations, review gates, drift \u002F\n   rewind rules, and evidence required before completion.\n3. Review critically - identify any questions or concerns about the plan\n4. If the view contradicts the plan, baseline, or current worktree evidence,\n   return to plan review or refresh the advisory handoff before editing.\n5. Run the TDD Route Guard before implementation: confirm `Mode`, `Decision`, `Strict authority`,\n   strict signals, light eligibility, `Test posture`, and verification. Strict\n   steps require either an explicit user\u002Fproject request or a recorded auto\n   decision; plan approval or risk labels alone are not authority. An\n   off-mode missing record may be repaired only as `Mode: off \u002F Decision:\n   skipped` without loading TDD. Missing\u002Funsupported auto decisions return to\n   plan review. An auto-light record is unsupported when any strict signal is\n   present or when its tiny\u002Flow-risk\u002Fsingle-owner\u002Fno-behavior-change proof is\n   incomplete. Only `Decision: strict` with recorded strict authority may\n   authorize steps named `Write failing test`, `Verify RED`, `GREEN`, or\n   `REFACTOR`. Do not infer `strict` during execution.\n6. If concerns: Raise them with your human partner before starting\n7. Before the first write, capture `TaskStartSnapshot`: root, `HEAD`, branch or\n   detached state, upstream divergence, staged\u002Funstaged\u002Funtracked paths, active\n   Git operations, and `git worktree list --porcelain`. Preserve task-preexisting\n   state; do not stash, reset, clean, or commit it.\n8. Reuse the current branch unless rules require independent history or another\n   goal owns it. If justified, switch\u002Fcreate it in the\n   current workspace when safe; a worktree still requires\n   concurrent checkout or blocking dirty state.\n9. If no concerns: Create TodoWrite and proceed\n\n### Step 1.5: Long-Task Checkpoint Setup\n\nIf the plan has multiple tasks, may span sessions, or includes architecture \u002F contract \u002F workflow changes:\n\n1. Announce: \"I'm using the long-task-continuation skill to keep this plan checkpointed and drift-aware.\"\n2. Load aegis:long-task-continuation.\n3. Create the initial checkpoint from the plan:\n   - current todo\n   - active task\n   - completed tasks\n   - evidence refs\n   - blockers\n   - next step\n4. Before each task, restate the current checkpoint.\n5. After each task, update checkpoint, evidence refs, and drift check.\n\nBefore a verification-driven unplanned edit, read retained `PatchShape`,\n`CanonicalOwner`, `UpwardDrillSignal`, outcome, and evidence refs. Route their\ncomparison with the candidate to `systematic-debugging` before editing; it\ndecides whether the directions converge. A proven independent canonical-owner\nroot stays on the normal plan path.\n\n### Step 2: Execute Tasks\n\nFor interface\u002Finteraction changes, compose `ui-ux-governance` before affected\nedits and verify the plan's scoped experience criteria at the relevant user seam.\n\nFor each task:\n1. Mark as in_progress\n2. Follow each step exactly (plan has bite-sized steps)\n3. Before any new source-code path is added by a task, restate the plan's\n   `Change Necessity` or create a compact one if the plan failed to carry it\n   forward. Plan approval is not by itself proof that a new helper, small guard,\n   new branch, fallback, adapter, or owner is necessary.\n\n   ```text\n   Change Necessity:\n   - User-visible need:\n   - No-change \u002F non-code option:\n   - Why code change is necessary:\n   - Minimum change boundary:\n   - Decision: no-change | docs\u002Fconfig-only | code-change | needs-clarification\n   ```\n\n   If the decision is not `code-change`, pause execution and return to plan\n   review instead of editing. If the decision is `code-change`, carry the\n   minimum boundary into the edit and verification scope.\n4. Before any non-trivial source edit, run the plan's\n   `Pre-Edit Complexity Check` or create a compact one:\n\n   Use `using-aegis\u002Freferences\u002Fcomplexity-governance.md` for shared artifact\n   classes, pressure signals, and `over-budget` handling.\n\n   ```text\n   Complexity Budget:\n   - Artifact class:\n   - Target files \u002F artifacts:\n   - Current pressure:\n   - Projected post-change pressure:\n   - Budget result: within-budget | at-risk | over-budget\n   - Planned governance:\n\n   Pre-Edit Complexity Check:\n   - Target edit file:\n   - Existing pressure signal:\n   - Safer edit boundary:\n   - Decision: edit-in-place | extract helper | add owner file | split task | pause for plan update\n\n   Pre-Edit Owner-Fit Decision:\n   - Edit intent: wiring-only | move-out \u002F extract-first | local-fix-without-new-responsibility | new-responsibility | emergency \u002F compatibility patch\n   - Owner fit:\n   - Safer edit boundary:\n   - Decision: edit-in-place | extract helper | add owner file | split task | pause for plan update\n   ```\n\n   If the check contradicts the plan's file boundary, pause and return to plan\n   review instead of silently stuffing logic into an overloaded owner. If the\n   budget result is `over-budget` and the task does not also govern that\n   overrun, stop execution and return to plan review rather than pushing the\n   task through as if it were still atomic.\n   When the target edit file is over-budget or mixed-purpose,\n   `new-responsibility` must not be added in place by default. `wiring-only`,\n   `move-out \u002F extract-first`, and `local-fix-without-new-responsibility` may\n   proceed only when they do not add a new responsibility and the verification\n   boundary is clear. `emergency \u002F compatibility patch` requires residual risk\n   and a retirement trigger.\n5. Run verifications as specified\n6. The coordinator is the Git mutation owner. After the coherent Task passes\n   its planned verification, use `verification-before-completion` before a\n   default local commit, stage only task-owned paths, and read back `HEAD`, the\n   committed file list, and remaining task delta. `no commit`, read-only,\n   no-change, and failed-verification tasks create no normal commit.\n7. Update `TodoCheckpointDraft` and `DriftCheckDraft` before marking the task completed.\n   When an `Execution Readiness View` exists, the drift check must explicitly\n   compare the active slice against the view's intent lock, scope fence,\n   baseline lock, compatibility boundary, retirement boundary, test\n   obligations, and review gates.\n8. Mark as completed\n\n### Step 3: Complete Development\n\nAfter all tasks complete and verified:\n\n- if Aegis created a branch\u002Fworktree or the user requests integration handling,\n  use `aegis:finishing-a-development-branch`;\n- otherwise use `verification-before-completion`, report the local task commit\n  and `Task clean` \u002F `Repository clean`, and do not invent merge\u002FPR ceremony.\n\n## When to Stop and Ask for Help\n\n**STOP executing immediately when:**\n- Hit a blocker (missing dependency, test fails, instruction unclear)\n- Plan has critical gaps preventing starting\n- You don't understand an instruction\n- Verification fails repeatedly\n\n**Ask for clarification rather than guessing.**\n\n## When to Revisit Earlier Steps\n\n**Return to Review (Step 1) when:**\n- Partner updates the plan based on your feedback\n- Fundamental approach needs rethinking\n\n**Don't force through blockers** - stop and ask.\n\n## Remember\n- Review plan critically first\n- Follow plan steps exactly\n- Don't skip verifications\n- Reference skills when plan says to\n- Stop when blocked, don't guess\n- Do not create a branch merely because the current branch is `main`\u002F`master`\n- Do not let task complexity, TDD, planning, or subagents alone trigger a worktree\n\n## Integration\n\n**Required workflow skills:**\n- **aegis:writing-plans** - Creates the plan this skill executes\n- **aegis:using-git-worktrees** - Only when the approved Git lifecycle says a concurrent checkout is necessary\n- **aegis:finishing-a-development-branch** - Only when branch\u002Fworktree integration or cleanup is in scope\n","# Executing Plans\n\n## Overview\n\nLoad plan, review critically, execute all tasks, report when complete.\n\n**Announce at start:** \"I'm using the executing-plans skill to implement this plan.\"\n\nFor non-trivial execution, include `Aegis Visibility`: briefly tie the active\nslice to its plan, checkpoint, drift or verification boundary. At completion,\npass plan adherence, evidence, complexity and residual risk to\n`verification-before-completion` for the unified receipt.\n\nIf subagents are available and the plan has genuinely independent tasks,\nprefer `subagent-driven-development`; lack of subagent support does not block\ninline execution. Same-task agents share one workspace, and the coordinator\nremains the only Git mutation owner.\n\n## The Process\n\n### Step 1: Load and Review Plan\n1. Read plan file\n2. If the plan or active checkpoint includes an `Execution Readiness View`,\n   read it before implementation and compare the plan against its intent lock,\n   scope fence, baseline lock, owner \u002F contract constraints, compatibility\n   boundary, retirement boundary, test obligations, review gates, drift \u002F\n   rewind rules, and evidence required before completion.\n3. Review critically - identify any questions or concerns about the plan\n4. If the view contradicts the plan, baseline, or current worktree evidence,\n   return to plan review or refresh the advisory handoff before editing.\n5. Run the TDD Route Guard before implementation: confirm `Mode`, `Decision`, `Strict authority`,\n   strict signals, light eligibility, `Test posture`, and verification. Strict\n   steps require either an explicit user\u002Fproject request or a recorded auto\n   decision; plan approval or risk labels alone are not authority. An\n   off-mode missing record may be repaired only as `Mode: off \u002F Decision:\n   skipped` without loading TDD. Missing\u002Funsupported auto decisions return to\n   plan review. An auto-light record is unsupported when any strict signal is\n   present or when its tiny\u002Flow-risk\u002Fsingle-owner\u002Fno-behavior-change proof is\n   incomplete. Only `Decision: strict` with recorded strict authority may\n   authorize steps named `Write failing test`, `Verify RED`, `GREEN`, or\n   `REFACTOR`. Do not infer `strict` during execution.\n6. If concerns: Raise them with your human partner before starting\n7. Before the first write, capture `TaskStartSnapshot`: root, `HEAD`, branch or\n   detached state, upstream divergence, staged\u002Funstaged\u002Funtracked paths, active\n   Git operations, and `git worktree list --porcelain`. Preserve task-preexisting\n   state; do not stash, reset, clean, or commit it.\n8. Reuse the current branch unless rules require independent history or another\n   goal owns it. If justified, switch\u002Fcreate it in the\n   current workspace when safe; a worktree still requires\n   concurrent checkout or blocking dirty state.\n9. If no concerns: Create TodoWrite and proceed\n\n### Step 1.5: Long-Task Checkpoint Setup\n\nIf the plan has multiple tasks, may span sessions, or includes architecture \u002F contract \u002F workflow changes:\n\n1. Announce: \"I'm using the long-task-continuation skill to keep this plan checkpointed and drift-aware.\"\n2. Load aegis:long-task-continuation.\n3. Create the initial checkpoint from the plan:\n   - current todo\n   - active task\n   - completed tasks\n   - evidence refs\n   - blockers\n   - next step\n4. Before each task, restate the current checkpoint.\n5. After each task, update checkpoint, evidence refs, and drift check.\n\nBefore a verification-driven unplanned edit, read retained `PatchShape`,\n`CanonicalOwner`, `UpwardDrillSignal`, outcome, and evidence refs. Route their\ncomparison with the candidate to `systematic-debugging` before editing; it\ndecides whether the directions converge. A proven independent canonical-owner\nroot stays on the normal plan path.\n\n### Step 2: Execute Tasks\n\nFor interface\u002Finteraction changes, compose `ui-ux-governance` before affected\nedits and verify the plan's scoped experience criteria at the relevant user seam.\n\nFor each task:\n1. Mark as in_progress\n2. Follow each step exactly (plan has bite-sized steps)\n3. Before any new source-code path is added by a task, restate the plan's\n   `Change Necessity` or create a compact one if the plan failed to carry it\n   forward. Plan approval is not by itself proof that a new helper, small guard,\n   new branch, fallback, adapter, or owner is necessary.\n\n   ```text\n   Change Necessity:\n   - User-visible need:\n   - No-change \u002F non-code option:\n   - Why code change is necessary:\n   - Minimum change boundary:\n   - Decision: no-change | docs\u002Fconfig-only | code-change | needs-clarification\n   ```\n\n   If the decision is not `code-change`, pause execution and return to plan\n   review instead of editing. If the decision is `code-change`, carry the\n   minimum boundary into the edit and verification scope.\n4. Before any non-trivial source edit, run the plan's\n   `Pre-Edit Complexity Check` or create a compact one:\n\n   Use `using-aegis\u002Freferences\u002Fcomplexity-governance.md` for shared artifact\n   classes, pressure signals, and `over-budget` handling.\n\n   ```text\n   Complexity Budget:\n   - Artifact class:\n   - Target files \u002F artifacts:\n   - Current pressure:\n   - Projected post-change pressure:\n   - Budget result: within-budget | at-risk | over-budget\n   - Planned governance:\n\n   Pre-Edit Complexity Check:\n   - Target edit file:\n   - Existing pressure signal:\n   - Safer edit boundary:\n   - Decision: edit-in-place | extract helper | add owner file | split task | pause for plan update\n\n   Pre-Edit Owner-Fit Decision:\n   - Edit intent: wiring-only | move-out \u002F extract-first | local-fix-without-new-responsibility | new-responsibility | emergency \u002F compatibility patch\n   - Owner fit:\n   - Safer edit boundary:\n   - Decision: edit-in-place | extract helper | add owner file | split task | pause for plan update\n   ```\n\n   If the check contradicts the plan's file boundary, pause and return to plan\n   review instead of silently stuffing logic into an overloaded owner. If the\n   budget result is `over-budget` and the task does not also govern that\n   overrun, stop execution and return to plan review rather than pushing the\n   task through as if it were still atomic.\n   When the target edit file is over-budget or mixed-purpose,\n   `new-responsibility` must not be added in place by default. `wiring-only`,\n   `move-out \u002F extract-first`, and `local-fix-without-new-responsibility` may\n   proceed only when they do not add a new responsibility and the verification\n   boundary is clear. `emergency \u002F compatibility patch` requires residual risk\n   and a retirement trigger.\n5. Run verifications as specified\n6. The coordinator is the Git mutation owner. After the coherent Task passes\n   its planned verification, use `verification-before-completion` before a\n   default local commit, stage only task-owned paths, and read back `HEAD`, the\n   committed file list, and remaining task delta. `no commit`, read-only,\n   no-change, and failed-verification tasks create no normal commit.\n7. Update `TodoCheckpointDraft` and `DriftCheckDraft` before marking the task completed.\n   When an `Execution Readiness View` exists, the drift check must explicitly\n   compare the active slice against the view's intent lock, scope fence,\n   baseline lock, compatibility boundary, retirement boundary, test\n   obligations, and review gates.\n8. Mark as completed\n\n### Step 3: Complete Development\n\nAfter all tasks complete and verified:\n\n- if Aegis created a branch\u002Fworktree or the user requests integration handling,\n  use `aegis:finishing-a-development-branch`;\n- otherwise use `verification-before-completion`, report the local task commit\n  and `Task clean` \u002F `Repository clean`, and do not invent merge\u002FPR ceremony.\n\n## When to Stop and Ask for Help\n\n**STOP executing immediately when:**\n- Hit a blocker (missing dependency, test fails, instruction unclear)\n- Plan has critical gaps preventing starting\n- You don't understand an instruction\n- Verification fails repeatedly\n\n**Ask for clarification rather than guessing.**\n\n## When to Revisit Earlier Steps\n\n**Return to Review (Step 1) when:**\n- Partner updates the plan based on your feedback\n- Fundamental approach needs rethinking\n\n**Don't force through blockers** - stop and ask.\n\n## Remember\n- Review plan critically first\n- Follow plan steps exactly\n- Don't skip verifications\n- Reference skills when plan says to\n- Stop when blocked, don't guess\n- Do not create a branch merely because the current branch is `main`\u002F`master`\n- Do not let task complexity, TDD, planning, or subagents alone trigger a worktree\n\n## Integration\n\n**Required workflow skills:**\n- **aegis:writing-plans** - Creates the plan this skill executes\n- **aegis:using-git-worktrees** - Only when the approved Git lifecycle says a concurrent checkout is necessary\n- **aegis:finishing-a-development-branch** - Only when branch\u002Fworktree integration or cleanup is in scope\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fexecuting-plans",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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill executing-plans",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill executing-plans",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill executing-plans","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FGanyuanRan\u002FAegis\u002Fskills\u002Fexecuting-plans\u002FSKILL.md",true,[],[70,80,88,96,104,112],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":79},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":79},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":79},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":79},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":79},"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":79},"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",[],[]]