[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MPAEYD4TN49TKVAQ8E7RCY":3,"skill-same:01M6MPAEYD4TN49TKVAQ8E7RCY":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6MPAEYD4TN49TKVAQ8E7RCY","kanban-workflow",null,"Comprehensive guide for using YYLO Ledger task management. Covers all commands (create, list, search, get, mark, update, archive, deps, ready, order, merge), dependency management, best practices, and workflow patterns. Use when you need to interact with the YYLO Ledger board.","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\u002Fyylo-dev\u002Fyylo\u002F.claude\u002Fskills\u002Fkanban-workflow\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"kanban workflow","kanban","workflow","guide","when","for","you","commands","get","patterns","ready","dependency","list","command","question","task management","deps","search","update","create","merge","2026-11-10 10:12:30",false,"---\nname: kanban-workflow\ndescription: Comprehensive guide for using YYLO Ledger task management. Covers all commands (create, list, search, get, mark, update, archive, deps, ready, order, merge), dependency management, best practices, and workflow patterns. Use when you need to interact with the YYLO Ledger board.\nargument-hint: \"[command or workflow question]\"\n---\n\n## YYLO Ledger CLI Reference\n\nUse `yy ledger` for all commands. YYLO 0.2.2 supports the exact `yylo-ledger 0.2.0` task CLI. `yy kanban` is a labelled compatibility alias for the same controller-routed task runtime.\n\n### Supported task contract\n\n- The public Ledger 0.2.0 surface is task-oriented: create, get, update, mark, archive, list\u002Fsearch, dependencies, ordering, history, doctor, compatibility, conversion, rollback, and cold archive operations.\n- Do not advertise `record`, `wiki`, `workflow`, or `artifact` namespaces unless the installed `yy ledger --help` explicitly provides them in a future supported release.\n- Read current task state before mutation, preserve mutation receipts where offered, and never bypass controller routing or lifecycle state with direct file edits.\n- Normal discovery is hot-only unless an explicit cold-archive command is used.\n\n### Opt-in cross-project routing\n\nCross-project access is disabled by default. The source `.juno_task\u002Fconfig.json` must set `kanbanRegistry.enabled: true` and explicitly list `allowedProjects`; environment overrides are `YYLO_LEDGER_REGISTRY_ENABLED` and `YYLO_LEDGER_REGISTRY_ALLOWED_PROJECTS`. Register with `yy ledger project add ALIAS --path \u002Fabsolute\u002Fproject`, then route any command with `--project ALIAS`. The destination wrapper\u002Fruntime remains authoritative, and routing failures never fall back to the source board.\n\n### Legacy Task compatibility commands\n\n**CREATE** — Add a new task\n```bash\nyy ledger create \"Task description here\" --status backlog --tags feature,backend\n```\nOptions: `--status` (backlog|todo|in_progress|done), `--tags` (comma\u002Fspace-separated), `--blocked-by` (task IDs), `--related-tasks` (task IDs)\n\n**LIST** — Browse tasks with summary stats\n```bash\nyy ledger list --limit 5 --sort asc\nyy ledger list --status todo --sort asc\nyy ledger list --status todo,in_progress --limit 10\n```\n\n**SEARCH** — Find tasks by criteria\n```bash\nyy ledger search --status todo --tag backend --limit 10\nyy ledger search --body \"OAuth\" --open\nyy ledger search --commit abc123\n```\nFilters: `--status`, `--tag`, `--body`, `--response`, `--commit`, `--open` (no agent_response), `--recent`, `--exclude` (exclude tags)\n\n**GET** — Full task details (including dependency info and related task details)\n```bash\nyy ledger get TASK_ID\n```\n\n**MARK** — Update status with required response message\n```bash\nyy ledger mark in_progress --id TASK_ID --response \"Starting work on this\"\nyy ledger mark done --id TASK_ID --response \"Completed: implemented X, tested Y\" --commit abc123def\nyy ledger mark todo --id TASK_ID --response \"Reopening: found regression\"\n```\nRequired: `--id` and `--response`. Optional: `--commit` (recommended for done).\n\n**UPDATE** — Modify task fields\n```bash\nyy ledger update TASK_ID --status todo --tags backend,urgent\nyy ledger update TASK_ID --commit abc123def\nyy ledger update TASK_ID --response \"Additional context\"\n```\n\n**ARCHIVE** — Soft delete (preserves data, sets status to archive)\n```bash\nyy ledger archive TASK_ID\n```\n\n### Immutable cold archive packs\n\nNormal `list`, `search`, `ready`, and `order` are deliberately hot-only. Exact `get TASK_ID` transparently resolves a hot task or a read-only archived task; use `history TASK_ID` explicitly for its ledger. Discover cold tasks only with bounded, projected `archive-search` output:\n\n```bash\nyy ledger archive-search --tag backend --before 2026-01-01 --limit 20 --projection metadata\n```\n\nBefore archive maintenance, preflight the installed version\u002Fhelp and obtain explicit owner authorization. The repository and index must be clean, and reports must be durable new paths outside the repository:\n\n```bash\nyy ledger --version\nyy ledger archive-pack plan --status done,archive --older-than 90d --max-tasks 1000 --target-bytes 26214400 --hard-max-bytes 47185920 --report \u002Fexternal\u002Freceipts\u002Farchive-plan.json\n# Independently inspect selected IDs, revisions, source HEAD, policy, and plan hash.\nyy ledger archive-pack create --plan \u002Fexternal\u002Freceipts\u002Farchive-plan.json --report \u002Fexternal\u002Freceipts\u002Farchive-create.json\nyy ledger archive-pack doctor\nyy ledger doctor\n```\n\nA stale plan or selected-task\u002Fworktree conflict must fail closed: discard the plan, resolve the conflict, and plan again. Never automate archival, edit\u002Fappend packs or manifests, restore\u002Freopen an archived ID, use force\u002Flossy controls, or enumerate archive files directly. Create follow-up work as a new hot task related to the archived ID. Production archival, push\u002Fdeploy, and post-deploy E2E each require separate authorization; agents must not infer it from implementation approval.\n\n### Dependency Management\n\n**DEPS** — View, add, or remove task dependencies\n```bash\n# View dependency info (blockers, dependents, priority score)\nyy ledger deps TASK_ID\n\n# Add blockers (TASK_ID cannot start until BLOCKER1 and BLOCKER2 are done)\nyy ledger deps add --id TASK_ID --blocked-by BLOCKER1 BLOCKER2\n\n# Remove a blocker\nyy ledger deps remove --id TASK_ID --blocked-by BLOCKER1\n```\nCycle detection prevents circular dependencies automatically.\n\n**READY** — Tasks with all blockers satisfied (safe to work on)\n```bash\nyy ledger ready\nyy ledger ready --tag backend --limit 5\n```\nReturns tasks where status is backlog\u002Ftodo\u002Fin_progress AND all `blocked_by` tasks are done\u002Farchive.\n\n**ORDER** — Topological sort of open tasks respecting dependencies\n```bash\nyy ledger order\nyy ledger order --scores\n```\nUse for determining safe parallel execution order.\n\n### Body Markup for Inline Dependencies\n\nDeclare dependencies and relations directly in task body text:\n\n```\n[blocked_by]TASK_ID[\u002Fblocked_by]          — This task is blocked by TASK_ID\n[blocked_by]ID1, ID2[\u002Fblocked_by]         — Blocked by multiple tasks\n[task_id]RELATED_ID[\u002Ftask_id]             — Reference a related task\n[task_id]ID1 ID2[\u002Ftask_id]                — Multiple related tasks\n```\n\nThese are parsed automatically when the task is created\u002Fupdated.\n\n### Merge (Multi-Directory Consolidation)\n\nWhen tasks get scattered across subdirectories:\n```bash\n# First produce and review a deterministic plan\nyy ledger merge .\u002Fsub1\u002F.juno_task .\u002Fsub2\u002F.juno_task --into .\u002F.juno_task \\\n  --dry-run --plan-file \u002Fexternal\u002Fledger-merge-plan.json\n\n# Apply only that reviewed plan and retain its receipt\nyy ledger merge .\u002Fsub1\u002F.juno_task .\u002Fsub2\u002F.juno_task --into .\u002F.juno_task \\\n  --apply-plan \u002Fexternal\u002Fledger-merge-plan.json \\\n  --receipt-file \u002Fexternal\u002Fledger-merge-receipt.json\n```\n\n### Output Formats\n\nAll commands support: `-f json`, `-f ndjson` (default), `-f xml`, `-f table`\nAdd `--raw` for compact output. Add `-p` for pretty print.\n\n### Best Practices\n\n1. **Task sizing**: Create tasks small enough to complete in one iteration without filling the context window\n2. **Status flow**: backlog → todo → in_progress → done (or archive for abandoned tasks)\n3. **Always include `--response`** when using `mark` — document what you did and how you tested it\n4. **Attach commits**: Use `--commit HASH` when marking done, then `update TASK_ID --commit HASH` to link the git history\n5. **Use `ready`** before starting work to find unblocked tasks\n6. **Use `order --scores`** to plan parallel execution pipelines\n7. **Use `[blocked_by]` markup** in task body when creating tasks that depend on others\n8. **Use `[task_id]` markup** in task body to cross-reference related tasks\n9. **Use `get TASK_ID`** to see full task details including resolved dependency and related task info\n10. **Concurrent features are supported** — start each selected task with `yy task start TASK_ID`; each gets a dedicated product worktree, while `yy merge` serializes only target updates\n\n### Canonical Controller Routing\n\nYYLO Ledger mutation resolves the controller in this order: explicit `JUNO_TASK_ROOT`, repository-local registration, then the current project root. Diagnose before orchestration with `.juno_task\u002Fscripts\u002Fcontroller_resolver.py --cwd \"$PWD\" --operation kanban`. The resolver may bootstrap or idempotently confirm a registration, but changing an existing controller requires `yy migrate registration plan` followed by a separately authorized apply. Explicit\u002Fregistered path or branch errors fail closed—YYLO Ledger never switches Git branches or falls back silently.\n\nRun YYLO Ledger and workflows from the controller. A task checkout may implement\u002Ftest but routes task\u002Fsession writes to that controller. An integration-owner checkout stays clean and refuses Kanban\u002Forchestration\u002Fsession writes in strict mode; launch from the controller and pass the product checkout separately as `TASK_ROOT`.\n\n### Environment Variables\n\n- `JUNO_TASK_ROOT` — Explicit canonical controller\u002Ftask-storage root (not the product `TASK_ROOT`)\n- `JUNO_CONTROLLER_BRANCH` — Expected controller branch for environment-based routing\n- `JUNO_WORKSPACE_ROLE` — `controller`, `task`, or `integration-owner`\n- `JUNO_WORKSPACE_ENFORCEMENT` — `off`, `warn`, or `strict`\n- `JUNO_DEBUG=true` — Show diagnostic messages\n- `JUNO_VERBOSE=true` — Show informational messages\n- `JUNO_KANBAN_LIST_BODY_TRUNCATE_CHARS=N` — Override list body truncation (default: 1200)\n\n$ARGUMENTS\n","## YYLO Ledger CLI Reference\n\nUse `yy ledger` for all commands. YYLO 0.2.2 supports the exact `yylo-ledger 0.2.0` task CLI. `yy kanban` is a labelled compatibility alias for the same controller-routed task runtime.\n\n### Supported task contract\n\n- The public Ledger 0.2.0 surface is task-oriented: create, get, update, mark, archive, list\u002Fsearch, dependencies, ordering, history, doctor, compatibility, conversion, rollback, and cold archive operations.\n- Do not advertise `record`, `wiki`, `workflow`, or `artifact` namespaces unless the installed `yy ledger --help` explicitly provides them in a future supported release.\n- Read current task state before mutation, preserve mutation receipts where offered, and never bypass controller routing or lifecycle state with direct file edits.\n- Normal discovery is hot-only unless an explicit cold-archive command is used.\n\n### Opt-in cross-project routing\n\nCross-project access is disabled by default. The source `.juno_task\u002Fconfig.json` must set `kanbanRegistry.enabled: true` and explicitly list `allowedProjects`; environment overrides are `YYLO_LEDGER_REGISTRY_ENABLED` and `YYLO_LEDGER_REGISTRY_ALLOWED_PROJECTS`. Register with `yy ledger project add ALIAS --path \u002Fabsolute\u002Fproject`, then route any command with `--project ALIAS`. The destination wrapper\u002Fruntime remains authoritative, and routing failures never fall back to the source board.\n\n### Legacy Task compatibility commands\n\n**CREATE** — Add a new task\n```bash\nyy ledger create \"Task description here\" --status backlog --tags feature,backend\n```\nOptions: `--status` (backlog|todo|in_progress|done), `--tags` (comma\u002Fspace-separated), `--blocked-by` (task IDs), `--related-tasks` (task IDs)\n\n**LIST** — Browse tasks with summary stats\n```bash\nyy ledger list --limit 5 --sort asc\nyy ledger list --status todo --sort asc\nyy ledger list --status todo,in_progress --limit 10\n```\n\n**SEARCH** — Find tasks by criteria\n```bash\nyy ledger search --status todo --tag backend --limit 10\nyy ledger search --body \"OAuth\" --open\nyy ledger search --commit abc123\n```\nFilters: `--status`, `--tag`, `--body`, `--response`, `--commit`, `--open` (no agent_response), `--recent`, `--exclude` (exclude tags)\n\n**GET** — Full task details (including dependency info and related task details)\n```bash\nyy ledger get TASK_ID\n```\n\n**MARK** — Update status with required response message\n```bash\nyy ledger mark in_progress --id TASK_ID --response \"Starting work on this\"\nyy ledger mark done --id TASK_ID --response \"Completed: implemented X, tested Y\" --commit abc123def\nyy ledger mark todo --id TASK_ID --response \"Reopening: found regression\"\n```\nRequired: `--id` and `--response`. Optional: `--commit` (recommended for done).\n\n**UPDATE** — Modify task fields\n```bash\nyy ledger update TASK_ID --status todo --tags backend,urgent\nyy ledger update TASK_ID --commit abc123def\nyy ledger update TASK_ID --response \"Additional context\"\n```\n\n**ARCHIVE** — Soft delete (preserves data, sets status to archive)\n```bash\nyy ledger archive TASK_ID\n```\n\n### Immutable cold archive packs\n\nNormal `list`, `search`, `ready`, and `order` are deliberately hot-only. Exact `get TASK_ID` transparently resolves a hot task or a read-only archived task; use `history TASK_ID` explicitly for its ledger. Discover cold tasks only with bounded, projected `archive-search` output:\n\n```bash\nyy ledger archive-search --tag backend --before 2026-01-01 --limit 20 --projection metadata\n```\n\nBefore archive maintenance, preflight the installed version\u002Fhelp and obtain explicit owner authorization. The repository and index must be clean, and reports must be durable new paths outside the repository:\n\n```bash\nyy ledger --version\nyy ledger archive-pack plan --status done,archive --older-than 90d --max-tasks 1000 --target-bytes 26214400 --hard-max-bytes 47185920 --report \u002Fexternal\u002Freceipts\u002Farchive-plan.json\n# Independently inspect selected IDs, revisions, source HEAD, policy, and plan hash.\nyy ledger archive-pack create --plan \u002Fexternal\u002Freceipts\u002Farchive-plan.json --report \u002Fexternal\u002Freceipts\u002Farchive-create.json\nyy ledger archive-pack doctor\nyy ledger doctor\n```\n\nA stale plan or selected-task\u002Fworktree conflict must fail closed: discard the plan, resolve the conflict, and plan again. Never automate archival, edit\u002Fappend packs or manifests, restore\u002Freopen an archived ID, use force\u002Flossy controls, or enumerate archive files directly. Create follow-up work as a new hot task related to the archived ID. Production archival, push\u002Fdeploy, and post-deploy E2E each require separate authorization; agents must not infer it from implementation approval.\n\n### Dependency Management\n\n**DEPS** — View, add, or remove task dependencies\n```bash\n# View dependency info (blockers, dependents, priority score)\nyy ledger deps TASK_ID\n\n# Add blockers (TASK_ID cannot start until BLOCKER1 and BLOCKER2 are done)\nyy ledger deps add --id TASK_ID --blocked-by BLOCKER1 BLOCKER2\n\n# Remove a blocker\nyy ledger deps remove --id TASK_ID --blocked-by BLOCKER1\n```\nCycle detection prevents circular dependencies automatically.\n\n**READY** — Tasks with all blockers satisfied (safe to work on)\n```bash\nyy ledger ready\nyy ledger ready --tag backend --limit 5\n```\nReturns tasks where status is backlog\u002Ftodo\u002Fin_progress AND all `blocked_by` tasks are done\u002Farchive.\n\n**ORDER** — Topological sort of open tasks respecting dependencies\n```bash\nyy ledger order\nyy ledger order --scores\n```\nUse for determining safe parallel execution order.\n\n### Body Markup for Inline Dependencies\n\nDeclare dependencies and relations directly in task body text:\n\n```\n[blocked_by]TASK_ID[\u002Fblocked_by]          — This task is blocked by TASK_ID\n[blocked_by]ID1, ID2[\u002Fblocked_by]         — Blocked by multiple tasks\n[task_id]RELATED_ID[\u002Ftask_id]             — Reference a related task\n[task_id]ID1 ID2[\u002Ftask_id]                — Multiple related tasks\n```\n\nThese are parsed automatically when the task is created\u002Fupdated.\n\n### Merge (Multi-Directory Consolidation)\n\nWhen tasks get scattered across subdirectories:\n```bash\n# First produce and review a deterministic plan\nyy ledger merge .\u002Fsub1\u002F.juno_task .\u002Fsub2\u002F.juno_task --into .\u002F.juno_task \\\n  --dry-run --plan-file \u002Fexternal\u002Fledger-merge-plan.json\n\n# Apply only that reviewed plan and retain its receipt\nyy ledger merge .\u002Fsub1\u002F.juno_task .\u002Fsub2\u002F.juno_task --into .\u002F.juno_task \\\n  --apply-plan \u002Fexternal\u002Fledger-merge-plan.json \\\n  --receipt-file \u002Fexternal\u002Fledger-merge-receipt.json\n```\n\n### Output Formats\n\nAll commands support: `-f json`, `-f ndjson` (default), `-f xml`, `-f table`\nAdd `--raw` for compact output. Add `-p` for pretty print.\n\n### Best Practices\n\n1. **Task sizing**: Create tasks small enough to complete in one iteration without filling the context window\n2. **Status flow**: backlog → todo → in_progress → done (or archive for abandoned tasks)\n3. **Always include `--response`** when using `mark` — document what you did and how you tested it\n4. **Attach commits**: Use `--commit HASH` when marking done, then `update TASK_ID --commit HASH` to link the git history\n5. **Use `ready`** before starting work to find unblocked tasks\n6. **Use `order --scores`** to plan parallel execution pipelines\n7. **Use `[blocked_by]` markup** in task body when creating tasks that depend on others\n8. **Use `[task_id]` markup** in task body to cross-reference related tasks\n9. **Use `get TASK_ID`** to see full task details including resolved dependency and related task info\n10. **Concurrent features are supported** — start each selected task with `yy task start TASK_ID`; each gets a dedicated product worktree, while `yy merge` serializes only target updates\n\n### Canonical Controller Routing\n\nYYLO Ledger mutation resolves the controller in this order: explicit `JUNO_TASK_ROOT`, repository-local registration, then the current project root. Diagnose before orchestration with `.juno_task\u002Fscripts\u002Fcontroller_resolver.py --cwd \"$PWD\" --operation kanban`. The resolver may bootstrap or idempotently confirm a registration, but changing an existing controller requires `yy migrate registration plan` followed by a separately authorized apply. Explicit\u002Fregistered path or branch errors fail closed—YYLO Ledger never switches Git branches or falls back silently.\n\nRun YYLO Ledger and workflows from the controller. A task checkout may implement\u002Ftest but routes task\u002Fsession writes to that controller. An integration-owner checkout stays clean and refuses Kanban\u002Forchestration\u002Fsession writes in strict mode; launch from the controller and pass the product checkout separately as `TASK_ROOT`.\n\n### Environment Variables\n\n- `JUNO_TASK_ROOT` — Explicit canonical controller\u002Ftask-storage root (not the product `TASK_ROOT`)\n- `JUNO_CONTROLLER_BRANCH` — Expected controller branch for environment-based routing\n- `JUNO_WORKSPACE_ROLE` — `controller`, `task`, or `integration-owner`\n- `JUNO_WORKSPACE_ENFORCEMENT` — `off`, `warn`, or `strict`\n- `JUNO_DEBUG=true` — Show diagnostic messages\n- `JUNO_VERBOSE=true` — Show informational messages\n- `JUNO_KANBAN_LIST_BODY_TRUNCATE_CHARS=N` — Override list body truncation (default: 1200)\n\n$ARGUMENTS\n",{"name":5,"description":7,"argument-hint":50},"[command or workflow question]","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fyylo-dev\u002Fyylo\u002F.claude\u002Fskills\u002Fkanban-workflow",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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill kanban-workflow",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill kanban-workflow",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill kanban-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyylo-dev\u002Fyylo\u002F.claude\u002Fskills\u002Fkanban-workflow\u002FSKILL.md",true,[],[76,86,94,102,110,118],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":85},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":85},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":85},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":85},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":85},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]