[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ME7Y58KZW1W2WD4K111RV1":3,"skill-same:01M6ME7Y58KZW1W2WD4K111RV1":87},{"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":28,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":80},"01M6ME7Y58KZW1W2WD4K111RV1","debug",null,"Diagnosis before prescription: reproduce, hypothesize, isolate, fix root cause, add a regression test; refactor mode maps deps, coupling and blast radius. Triggers: bug, error, fix, broken, not working, crashed, stack trace, exception, refactor, restructure, coupling, dependency map.","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\u002Fariaxhan\u002Fkernel-claude\u002Fskills\u002Fdebug\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[5,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"mode","workflow","error","add","diagnosis","map","maps","bug","dependency","fix","write","read","broken","regression","stack","deps","Bash","radius","refactor","2026-11-10 10:12:30",false,"---\nname: debug\ndescription: \"Diagnosis before prescription: reproduce, hypothesize, isolate, fix root cause, add a regression test; refactor mode maps deps, coupling and blast radius. Triggers: bug, error, fix, broken, not working, crashed, stack trace, exception, refactor, restructure, coupling, dependency map.\"\nuser-invocable: true\nallowed-tools: Read, Bash, Grep, Glob, Write, Agent\nkernel:\n  kind: workflow\n  version: 1\n  side_effects: none\n  confirmation: none\n---\n\n\u003Cskill id=\"debug\">\n\n\u003Cpurpose>\nDebugging is forming and testing a THEORY that explains the bug.\nNot random changes. Not guessing. Scientific method applied to code.\nDEFECT (in code) → INFECTION (in state) → FAILURE (visible symptom).\nThe failure you see is NOT where the bug is. Binary search upstream.\nSystematic methodology beats ad-hoc guessing. The process is the multiplier.\n\nDiagnosis comes before prescription: a surgeon cutting before the X-ray is guessing with a\nknife. Two modes, same discipline. `bug` (default) is the steps below. `refactor` swaps the\nsubject from a failure to a structure, and produces a plan instead of a fix.\n\u003C\u002Fpurpose>\n\n\u003Cprerequisite>Run `agentdb recall` with the exact error text, subsystem\u002Flibrary, failing\ntest, and known files\u002Fsymbols. Recall again when the hypothesis changes or a new failure\nappears; that is a new retrieval question. Reference on demand:\nskills\u002Fdebug\u002Freference\u002Fdebug-research.md.\u003C\u002Fprerequisite>\n\n\u003Csteps>\n1. **REPRODUCE**: get specific before touching code.\n   - Document: exact input, expected output, actual output (full stack trace), environment, frequency.\n   - \"Sometimes fails\" is not a reproduction. Get deterministic.\n   - Sensitive or high-blast-radius bug: investigate read-only (plan mode) and settle the approach before any edit.\n   \u003C!-- Updated 2026-09-20: sitepoint.com \u002F claudelog.com Claude Code debugging guides -->\n   - (gate: can reproduce consistently, OR have added targeted logging to wait for next occurrence)\n\n\n2. **HYPOTHESIZE**: list 3 causes before pursuing any.\n   - Read ALL error output first (anchoring bias mitigation).\n   - Write each hypothesis to AgentDB. Prevents circular re-investigation.\n   - (gate: 3 candidate hypotheses written; none pursued yet)\n\n3. **ISOLATE**: binary search, O(log n) not O(n).\n   - **Code**: call chain A→B→C→D→E fails → check midpoint C → recurse into failing half.\n   - **Time**: `git bisect` between known-good and known-bad commit. ~10 tests for 1000 commits.\n   - **Input**: large failing input → split in half → recurse to minimal reproduction case.\n   - Instrument at boundaries: log inputs\u002Foutputs at each layer boundary.\n   - Mock external dependencies to isolate which one causes failure.\n   \u003C!-- Updated 2026-09-19: dev.to flaky-test patterns; claudelog\u002Fsfeir debugging guides -->\n   - Diff working vs failing state (env, config, input, commit) before theorizing.\n   - Flaky test: classify first as timing\u002Frace, shared state, unseeded randomness, or\n     environment difference; only then propose a fix.\n\n   - (gate: failure localized to a specific function\u002Fcommit\u002Finput subset)\n\n4. **ROOT CAUSE**: the error line is the FAILURE. The DEFECT is upstream.\n   - Ask: what assumption was violated? What invariant broke?\n   - If you can't explain WHY it broke, you haven't found root cause.\n   - Top causes by frequency: wrong input shape\u002Ftype · off-by-one · missing null check · race condition · shared-state mutation · wrong comparison operator · variable scope · swallowed error · API contract mismatch · environment difference.\n   - (gate: can state root cause in one sentence explaining the violated invariant)\n\n5. **FIX**: root cause, not symptom.\n   - Fix the DEFECT, not the FAILURE site. (Null check at crash site = symptom fix.)\n   - Write regression test that fails before fix, passes after.\n   - Run: original failing case + edge cases + full regression suite.\n   - Commit fix + test together.\n   - (gate: regression test green; original failing case passes)\n\u003C\u002Fsteps>\n\n\u003Crefactor_mode>\nTriggers: refactor, restructure, clean up, coupling, dependency, \"what breaks if\".\nSame rule: diagnose, then hand off. Do not start cutting inside this mode.\n1. **MAP**: every file\u002Fmodule touching the target. Grep\u002FGlob every reference, or\n   `graphify affected \u003Csymbol>` when the graph is fresh. Build the import\u002Fcall map.\n2. **TRACE DEPS**: per file, who calls it, who depends on it, what breaks if it changes.\n3. **MEASURE COUPLING**: cross-module reference counts, circular dependencies, the\n   per-function CCN from `scripts\u002Fcomplexity.sh`.\n4. **RISKS**: current edge cases, what is tested, what is not, invariants to preserve.\n5. **PLAN**: files in change order, tests that must pass before AND after, tier by\n   reversibility x blast radius (file count is only a weak hint).\nHand off to \u002Fkernel:simplify to execute, which owns the preservation contract and the gate.\n\u003C\u002Frefactor_mode>\n\n\u003Cdiagnosis_output>\nWhen the run ends at a diagnosis rather than a fix, emit this and stop:\n```\n## Diagnosis: \u003Ctitle>\nMode: bug | refactor · Confidence: high | medium | low\nRoot cause: \u003Cone sentence naming the violated invariant>\nAffected: \u003Cfile - origin> | \u003Cfile - downstream> ...\nBlast radius: N files. Tier 1|2|3.\nHypotheses: 1. \u003Ch> -> CONFIRMED | REJECTED (\u003Cevidence>) ...\nRecommended approach: \u003Cwhat, not how>\nTests required: \u003Cfails before> \u002F \u003Cpasses after>\nNext: \u002Fkernel:ingest to implement, \u002Fkernel:simplify to restructure.\n```\nDecide and state the recommendation. Never stop to ask which hypothesis to pursue.\n\u003C\u002Fdiagnosis_output>\n\n\u003Canti_patterns>\nShotgun (random changes until it works) · fix-and-pray (never re-run the original case) ·\nsymptom fixing (null check at the crash site) · printf flooding (binary search first, then\ntargeted logging) · blame-the-framework (it's almost never the library) · unscoped\n\"investigate\" (scope narrowly or use a subagent so the file reads don't fill context).\n\u003C\u002Fanti_patterns>\n\n\u003Cwhen_stuck>\nExplain the problem in writing · re-read the error message (the answer is there most of\nthe time) · reduce to a minimal reproduction · ask \"what changed?\" (git log\u002Fdiff, deps,\nenv) · search the exact error message in quotes · step away, bias accumulates. Re-run the\nEXACT original failing case before declaring victory; \"seems to work\" is not evidence.\n\u003C\u002Fwhen_stuck>\n\n\u003Cescalation>\n30+ min on one hypothesis with no evidence → abandon it. 3+ hypotheses rejected → step\nback, re-examine assumptions. 2 failed fix attempts → invoke tearitapart; it may be a\ndesign problem. Repeated failed corrections in one session → \u002Fclear with a minimal\nreproduction. Bug only in production → add targeted monitoring, document, move on.\nFor 3+ plausible causes, spawn one fresh-context agent per hypothesis (evidence_for \u002F\nevidence_against \u002F confidence); fresh context catches what a long session anchors past.\n\u003C\u002Fescalation>\n\n\u003Ctelemetry>\nagentdb emit command \"debug\" \"\" '{\"mode\":\"bug|refactor\",\"confidence\":\"high|medium|low\",\"blast_radius\":N,\"tier\":N}'\n\u003C\u002Ftelemetry>\n\n\u003Con_complete>\nagentdb write-end '{\"skill\":\"debug\",\"bug\":\"\u003Cdescription>\",\"root_cause\":\"\u003Cwhat_broke>\",\"fix\":\"\u003Cwhat_fixed>\",\"test\":\"\u003Cregression_test_name>\",\"learned\":\"\u003Cpattern_for_future>\"}'\n\u003C\u002Fon_complete>\n\n\u003C\u002Fskill>\n","\u003Cskill id=\"debug\">\n\n\u003Cpurpose>\nDebugging is forming and testing a THEORY that explains the bug.\nNot random changes. Not guessing. Scientific method applied to code.\nDEFECT (in code) → INFECTION (in state) → FAILURE (visible symptom).\nThe failure you see is NOT where the bug is. Binary search upstream.\nSystematic methodology beats ad-hoc guessing. The process is the multiplier.\n\nDiagnosis comes before prescription: a surgeon cutting before the X-ray is guessing with a\nknife. Two modes, same discipline. `bug` (default) is the steps below. `refactor` swaps the\nsubject from a failure to a structure, and produces a plan instead of a fix.\n\u003C\u002Fpurpose>\n\n\u003Cprerequisite>Run `agentdb recall` with the exact error text, subsystem\u002Flibrary, failing\ntest, and known files\u002Fsymbols. Recall again when the hypothesis changes or a new failure\nappears; that is a new retrieval question. Reference on demand:\nskills\u002Fdebug\u002Freference\u002Fdebug-research.md.\u003C\u002Fprerequisite>\n\n\u003Csteps>\n1. **REPRODUCE**: get specific before touching code.\n   - Document: exact input, expected output, actual output (full stack trace), environment, frequency.\n   - \"Sometimes fails\" is not a reproduction. Get deterministic.\n   - Sensitive or high-blast-radius bug: investigate read-only (plan mode) and settle the approach before any edit.\n   \u003C!-- Updated 2026-09-20: sitepoint.com \u002F claudelog.com Claude Code debugging guides -->\n   - (gate: can reproduce consistently, OR have added targeted logging to wait for next occurrence)\n\n\n2. **HYPOTHESIZE**: list 3 causes before pursuing any.\n   - Read ALL error output first (anchoring bias mitigation).\n   - Write each hypothesis to AgentDB. Prevents circular re-investigation.\n   - (gate: 3 candidate hypotheses written; none pursued yet)\n\n3. **ISOLATE**: binary search, O(log n) not O(n).\n   - **Code**: call chain A→B→C→D→E fails → check midpoint C → recurse into failing half.\n   - **Time**: `git bisect` between known-good and known-bad commit. ~10 tests for 1000 commits.\n   - **Input**: large failing input → split in half → recurse to minimal reproduction case.\n   - Instrument at boundaries: log inputs\u002Foutputs at each layer boundary.\n   - Mock external dependencies to isolate which one causes failure.\n   \u003C!-- Updated 2026-09-19: dev.to flaky-test patterns; claudelog\u002Fsfeir debugging guides -->\n   - Diff working vs failing state (env, config, input, commit) before theorizing.\n   - Flaky test: classify first as timing\u002Frace, shared state, unseeded randomness, or\n     environment difference; only then propose a fix.\n\n   - (gate: failure localized to a specific function\u002Fcommit\u002Finput subset)\n\n4. **ROOT CAUSE**: the error line is the FAILURE. The DEFECT is upstream.\n   - Ask: what assumption was violated? What invariant broke?\n   - If you can't explain WHY it broke, you haven't found root cause.\n   - Top causes by frequency: wrong input shape\u002Ftype · off-by-one · missing null check · race condition · shared-state mutation · wrong comparison operator · variable scope · swallowed error · API contract mismatch · environment difference.\n   - (gate: can state root cause in one sentence explaining the violated invariant)\n\n5. **FIX**: root cause, not symptom.\n   - Fix the DEFECT, not the FAILURE site. (Null check at crash site = symptom fix.)\n   - Write regression test that fails before fix, passes after.\n   - Run: original failing case + edge cases + full regression suite.\n   - Commit fix + test together.\n   - (gate: regression test green; original failing case passes)\n\u003C\u002Fsteps>\n\n\u003Crefactor_mode>\nTriggers: refactor, restructure, clean up, coupling, dependency, \"what breaks if\".\nSame rule: diagnose, then hand off. Do not start cutting inside this mode.\n1. **MAP**: every file\u002Fmodule touching the target. Grep\u002FGlob every reference, or\n   `graphify affected \u003Csymbol>` when the graph is fresh. Build the import\u002Fcall map.\n2. **TRACE DEPS**: per file, who calls it, who depends on it, what breaks if it changes.\n3. **MEASURE COUPLING**: cross-module reference counts, circular dependencies, the\n   per-function CCN from `scripts\u002Fcomplexity.sh`.\n4. **RISKS**: current edge cases, what is tested, what is not, invariants to preserve.\n5. **PLAN**: files in change order, tests that must pass before AND after, tier by\n   reversibility x blast radius (file count is only a weak hint).\nHand off to \u002Fkernel:simplify to execute, which owns the preservation contract and the gate.\n\u003C\u002Frefactor_mode>\n\n\u003Cdiagnosis_output>\nWhen the run ends at a diagnosis rather than a fix, emit this and stop:\n```\n## Diagnosis: \u003Ctitle>\nMode: bug | refactor · Confidence: high | medium | low\nRoot cause: \u003Cone sentence naming the violated invariant>\nAffected: \u003Cfile - origin> | \u003Cfile - downstream> ...\nBlast radius: N files. Tier 1|2|3.\nHypotheses: 1. \u003Ch> -> CONFIRMED | REJECTED (\u003Cevidence>) ...\nRecommended approach: \u003Cwhat, not how>\nTests required: \u003Cfails before> \u002F \u003Cpasses after>\nNext: \u002Fkernel:ingest to implement, \u002Fkernel:simplify to restructure.\n```\nDecide and state the recommendation. Never stop to ask which hypothesis to pursue.\n\u003C\u002Fdiagnosis_output>\n\n\u003Canti_patterns>\nShotgun (random changes until it works) · fix-and-pray (never re-run the original case) ·\nsymptom fixing (null check at the crash site) · printf flooding (binary search first, then\ntargeted logging) · blame-the-framework (it's almost never the library) · unscoped\n\"investigate\" (scope narrowly or use a subagent so the file reads don't fill context).\n\u003C\u002Fanti_patterns>\n\n\u003Cwhen_stuck>\nExplain the problem in writing · re-read the error message (the answer is there most of\nthe time) · reduce to a minimal reproduction · ask \"what changed?\" (git log\u002Fdiff, deps,\nenv) · search the exact error message in quotes · step away, bias accumulates. Re-run the\nEXACT original failing case before declaring victory; \"seems to work\" is not evidence.\n\u003C\u002Fwhen_stuck>\n\n\u003Cescalation>\n30+ min on one hypothesis with no evidence → abandon it. 3+ hypotheses rejected → step\nback, re-examine assumptions. 2 failed fix attempts → invoke tearitapart; it may be a\ndesign problem. Repeated failed corrections in one session → \u002Fclear with a minimal\nreproduction. Bug only in production → add targeted monitoring, document, move on.\nFor 3+ plausible causes, spawn one fresh-context agent per hypothesis (evidence_for \u002F\nevidence_against \u002F confidence); fresh context catches what a long session anchors past.\n\u003C\u002Fescalation>\n\n\u003Ctelemetry>\nagentdb emit command \"debug\" \"\" '{\"mode\":\"bug|refactor\",\"confidence\":\"high|medium|low\",\"blast_radius\":N,\"tier\":N}'\n\u003C\u002Ftelemetry>\n\n\u003Con_complete>\nagentdb write-end '{\"skill\":\"debug\",\"bug\":\"\u003Cdescription>\",\"root_cause\":\"\u003Cwhat_broke>\",\"fix\":\"\u003Cwhat_fixed>\",\"test\":\"\u003Cregression_test_name>\",\"learned\":\"\u003Cpattern_for_future>\"}'\n\u003C\u002Fon_complete>\n\n\u003C\u002Fskill>\n",{"name":5,"kernel":53,"description":7,"allowed-tools":56,"user-invocable":57},{"kind":30,"version":54,"confirmation":55,"side_effects":55},1,"none","Read, Bash, Grep, Glob, Write, Agent",true,"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fariaxhan\u002Fkernel-claude\u002Fskills\u002Fdebug",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":69,"prompt":79,"zipAvailable":57},[70,73,76],{"tool":71,"command":72},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill debug",{"tool":74,"command":75},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill debug",{"tool":77,"command":78},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill debug","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fariaxhan\u002Fkernel-claude\u002Fskills\u002Fdebug\u002FSKILL.md",[81],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"reference\u002Fdebug-research.md","REFERENCE","参考文档",18807,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fariaxhan\u002Fkernel-claude\u002Fskills\u002Fdebug\u002Freference\u002Fdebug-research.md",[88,98,106,114,122,130],{"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":92,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":97},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":97},"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":97},"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":97},"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":97},"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":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":97},"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",[],[]]