[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MP5CTBAEEKG6RN1C0F2X5F":3,"skill-same:01M6MP5CTBAEEKG6RN1C0F2X5F":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6MP5CTBAEEKG6RN1C0F2X5F","verification",null,"Verification command resolution and evidence rule for skills that run a project's tests or build before calling work done. Resolves the test and build command from project instructions, then from the stack, then to none; defines what a pass, fail, or skipped claim must quote.","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\u002Fyagizdo\u002Fquiver\u002Fskills\u002Fverification\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"calling","for","rule","false","tests","resolution","project","quote","done","claim","test","build","evidence","instructions","command","work","stack","run","2026-11-10 10:12:30",false,"---\nname: verification\ndescription: \"Verification command resolution and evidence rule for skills that run a project's tests or build before calling work done. Resolves the test and build command from project instructions, then from the stack, then to none; defines what a pass, fail, or skipped claim must quote.\"\nuser-invocable: false\n---\n\n# Verification\n\nReference skill read by `\u002Fwork`, `\u002Fship`, `\u002Fdesign-build`, `\u002Fhypothesis-debugging`, and `\u002Fquiver:review` at their verification step. It is never invoked and never runs a command itself: the consumer resolves the command by the rules here, runs it, and quotes the evidence.\n\n## Command Resolution\n\n```\ntest: \u003Ccommand> | none (\u003Creason>)\nbuild: \u003Ccommand> | none (\u003Creason>)\nsource: docs | stack | none\n```\n\nThe consumer resolves once, before the first task runs, records these three lines, and passes the resolved command to every subagent as a literal. `none` is a value, not a gap to fill: it carries its reason in the parentheses and is never promoted to a guess. Test and build resolve independently under the same rules; `source` names the rule that produced the test command.\n\nApply the rules in order. The first rule that yields a command decides `source`.\n\n1. *Project instructions.* A command named in the project's `CLAUDE.md`, `AGENTS.md`, or equivalent agent-instruction file, in a Testing or Build section. When present it wins and `source` is `docs`.\n2. *Stack detection.* The table below, matched on files at the project root. `source` is `stack`.\n3. *None.* `source` is `none`. Write the reason in the parentheses; never substitute a guess.\n\nA command from rule 1 or 2 is confirmed before it runs: the script or task is declared in the manifest, and the tool is on `PATH` (`command -v`). A command that fails confirmation resolves to `none` with the reason, not to the next rule.\n\n| Stack | Signal | Test command | Build command | Confirm | Summary line | Exit caveat |\n|-------|--------|--------------|---------------|---------|--------------|-------------|\n| **Node** | `package.json`; package manager from the lockfile (`package-lock.json` npm, `pnpm-lock.yaml` pnpm, `yarn.lock` yarn, `bun.lock` or `bun.lockb` bun); a `packageManager` field overrides | `CI=true \u003Cpm> run test` | `\u003Cpm> run build` | `scripts.test` in `package.json` is a string that is not the placeholder `echo \"Error: no test specified\" && exit 1`, and `command -v \u003Cpm>` finds the resolved manager; same for `scripts.build`; a missing script is `none` | jest `Tests: N passed, N total`; vitest `Tests  N passed (N)`; mocha `N passing`; node:test `pass N` (spec reporter, the default since Node 23) or `# pass N` (tap, Node \u003C=22 on a pipe) | mocha exits the failure count; jest and vitest exit 1 on zero test files; node:test exits 0 and prints `pass 0`, so only the summary line separates `skipped` from `pass`; `bun test` is not the script, use `bun run test` |\n| **Python** | `pyproject.toml`, `setup.py`, or `requirements*.txt`; runner from `uv.lock` (`uv run pytest`), `poetry.lock` (`poetry run pytest`), else `python -m pytest`; `python -m unittest discover` only when pytest is not declared and `tests\u002F` or `test_*.py` exists | as resolved | `uv build` \u002F `poetry build` \u002F `python -m build` only when `pyproject.toml` has `[build-system]` or `setup.py` exists, else `none (application, no build step)` | pytest declared in `pyproject.toml`, `requirements*.txt`, `tox.ini`, or a `pytest.ini` exists, and `import pytest` succeeds under the resolved runner (`uv run python -c \"import pytest\"`, `poetry run python -c \"import pytest\"`, else `python -c \"import pytest\"`); `python -m build` needs `import build` under the same runner | pytest `N passed in Xs`; unittest `Ran N tests` then `OK` | exit 5 from pytest, or from unittest on 3.12+, means no tests ran: `skipped`, not `fail` |\n| **Go** | `go.mod` | `go test .\u002F...` | `go build .\u002F...` | `command -v go` | `ok  \u003Cpkg>  Xs` per package; build prints nothing on success, quote `no output, exit 0` | exit 0 with only `[no test files]` lines is `skipped`, not `pass` |\n| **Rust** | `Cargo.toml`; add `--workspace` when a `[workspace]` table exists | `cargo test` | `cargo build` | `command -v cargo` | `test result: ok. N passed; ...` once per target, quote the last line and the target count; build `Finished ... target(s) in Xs` | exit 101 on failure; `0 passed` on every target is `skipped` |\n| **Ruby** | `Gemfile` and `Gemfile.lock`; `rspec-core` in the lock -> `bundle exec rspec`; `minitest` in the lock with `test\u002F` -> `bundle exec rake test`; `bin\u002Frails` present -> `bin\u002Frails test` | as resolved | `bundle exec rake build` only when a `*.gemspec` exists and the Rakefile requires `bundler\u002Fgem_tasks`, else `none (application, no build task)` | `bundle exec rake -T test` lists the task for rake-based runners; `command -v bundle` | rspec `N examples, N failures`; minitest `N runs, N assertions, N failures, N errors` | `0 examples` or `0 runs` exits 0 and is `skipped` |\n| **Flutter\u002FDart** | `pubspec.yaml`; Flutter when `sdk: flutter` appears under `dependencies`, else Dart | `flutter test` (Dart: `dart test`) | `flutter analyze` (Dart: `dart analyze`); `flutter build \u003Ctarget>` only when the matching platform directory (`android\u002F`, `ios\u002F`, `web\u002F`, `macos\u002F`, `linux\u002F`, `windows\u002F`) exists and the consumer asked for an artifact; never `flutter build apk` on a project with no `android\u002F` | `command -v flutter` (or `dart`) and `test\u002F` contains at least one `*_test.dart` | \"All tests passed!\", \"Some tests failed.\", \"No tests ran.\"; analyze \"No issues found!\" | \"No tests ran.\" exits 79: read the line, not the code; `skipped`, not `fail` |\n\n### Cross-cutting rules\n\n1. Exit 0 is not evidence. The summary line must show at least one test executed; otherwise the outcome is `skipped`.\n2. Compare exit codes as zero versus nonzero, never `== 1`. pytest and unittest exit 5 when nothing ran, the Dart test runner exits 79, cargo exits 101, and mocha exits the failure count.\n3. Never let a runner wait. `CI=true` on every Node script, `vitest run` in place of a bare `vitest` script, and the consumer's own wait rules for cold builds.\n4. A command is runnable only when the tool is on `PATH` and the script or task is declared. Otherwise it is `none`.\n5. A failure whose first error line names a service, port, or environment variable (a `docker-compose.yml`, `.env.example`, or `DATABASE_URL` in test config is the usual signal) is reported verbatim and flagged as environmental. It is not counted as a code failure and not retried.\n\n## Evidence Rule\n\n- **Pass** is this run's exit code plus the runner's summary line, from a run made after the last edit. When the runner prints no summary, the last output line stands in.\n- **Fail** is the first failing test name plus the first error line. More output belongs in a report file, not in the evidence line.\n- **Skipped** carries its reason: `none` from resolution, a failed confirmation, or a zero-test run. It never counts as a pass; a consumer that requires a pass treats skipped as not passed.\n- **No evidence means not run.** \"Should pass\", \"ran earlier\", and \"the change is safe\" are not outcomes.\n- **A command that has not returned is not a pass.** Waiting for it is the consumer's business.\n\nConsumers quote the outcome in one of these line formats:\n\n```\npass:    \u003Ccommand> -> exit 0: \u003Csummary line>\nfail:    \u003Ccommand> -> exit \u003Ccode>: \u003Cfirst failing test> -- \u003Cfirst error line>\nskipped: \u003Creason>\n```\n\n## For Skill Authors\n\n- Read this file at the verification step, not at skill start.\n- Resolve once per run in the controller and pass the resolved command into any subagent prompt as a literal (`Test command: npm test`), never as \"detect the test command\".\n- Require the evidence line format back from a subagent, and paste the `### Subagent restatement` below into its prompt verbatim. It is the only text from this file that is copied anywhere, and `tests\u002Fskills\u002Ftest-verification-contract.sh` compares the copies to it.\n- Do not restate the resolution table. When a stack is missing, add a row here.\n\n### Subagent restatement\n\nRun the test command you were given exactly as written, and report a pass only by quoting this run's exit code and the runner's summary line -- a run that executed zero tests, a command that has not returned, or a result remembered from an earlier run is not a pass. On failure, quote the first failing test name and the first error line.\n","# Verification\n\nReference skill read by `\u002Fwork`, `\u002Fship`, `\u002Fdesign-build`, `\u002Fhypothesis-debugging`, and `\u002Fquiver:review` at their verification step. It is never invoked and never runs a command itself: the consumer resolves the command by the rules here, runs it, and quotes the evidence.\n\n## Command Resolution\n\n```\ntest: \u003Ccommand> | none (\u003Creason>)\nbuild: \u003Ccommand> | none (\u003Creason>)\nsource: docs | stack | none\n```\n\nThe consumer resolves once, before the first task runs, records these three lines, and passes the resolved command to every subagent as a literal. `none` is a value, not a gap to fill: it carries its reason in the parentheses and is never promoted to a guess. Test and build resolve independently under the same rules; `source` names the rule that produced the test command.\n\nApply the rules in order. The first rule that yields a command decides `source`.\n\n1. *Project instructions.* A command named in the project's `CLAUDE.md`, `AGENTS.md`, or equivalent agent-instruction file, in a Testing or Build section. When present it wins and `source` is `docs`.\n2. *Stack detection.* The table below, matched on files at the project root. `source` is `stack`.\n3. *None.* `source` is `none`. Write the reason in the parentheses; never substitute a guess.\n\nA command from rule 1 or 2 is confirmed before it runs: the script or task is declared in the manifest, and the tool is on `PATH` (`command -v`). A command that fails confirmation resolves to `none` with the reason, not to the next rule.\n\n| Stack | Signal | Test command | Build command | Confirm | Summary line | Exit caveat |\n|-------|--------|--------------|---------------|---------|--------------|-------------|\n| **Node** | `package.json`; package manager from the lockfile (`package-lock.json` npm, `pnpm-lock.yaml` pnpm, `yarn.lock` yarn, `bun.lock` or `bun.lockb` bun); a `packageManager` field overrides | `CI=true \u003Cpm> run test` | `\u003Cpm> run build` | `scripts.test` in `package.json` is a string that is not the placeholder `echo \"Error: no test specified\" && exit 1`, and `command -v \u003Cpm>` finds the resolved manager; same for `scripts.build`; a missing script is `none` | jest `Tests: N passed, N total`; vitest `Tests  N passed (N)`; mocha `N passing`; node:test `pass N` (spec reporter, the default since Node 23) or `# pass N` (tap, Node \u003C=22 on a pipe) | mocha exits the failure count; jest and vitest exit 1 on zero test files; node:test exits 0 and prints `pass 0`, so only the summary line separates `skipped` from `pass`; `bun test` is not the script, use `bun run test` |\n| **Python** | `pyproject.toml`, `setup.py`, or `requirements*.txt`; runner from `uv.lock` (`uv run pytest`), `poetry.lock` (`poetry run pytest`), else `python -m pytest`; `python -m unittest discover` only when pytest is not declared and `tests\u002F` or `test_*.py` exists | as resolved | `uv build` \u002F `poetry build` \u002F `python -m build` only when `pyproject.toml` has `[build-system]` or `setup.py` exists, else `none (application, no build step)` | pytest declared in `pyproject.toml`, `requirements*.txt`, `tox.ini`, or a `pytest.ini` exists, and `import pytest` succeeds under the resolved runner (`uv run python -c \"import pytest\"`, `poetry run python -c \"import pytest\"`, else `python -c \"import pytest\"`); `python -m build` needs `import build` under the same runner | pytest `N passed in Xs`; unittest `Ran N tests` then `OK` | exit 5 from pytest, or from unittest on 3.12+, means no tests ran: `skipped`, not `fail` |\n| **Go** | `go.mod` | `go test .\u002F...` | `go build .\u002F...` | `command -v go` | `ok  \u003Cpkg>  Xs` per package; build prints nothing on success, quote `no output, exit 0` | exit 0 with only `[no test files]` lines is `skipped`, not `pass` |\n| **Rust** | `Cargo.toml`; add `--workspace` when a `[workspace]` table exists | `cargo test` | `cargo build` | `command -v cargo` | `test result: ok. N passed; ...` once per target, quote the last line and the target count; build `Finished ... target(s) in Xs` | exit 101 on failure; `0 passed` on every target is `skipped` |\n| **Ruby** | `Gemfile` and `Gemfile.lock`; `rspec-core` in the lock -> `bundle exec rspec`; `minitest` in the lock with `test\u002F` -> `bundle exec rake test`; `bin\u002Frails` present -> `bin\u002Frails test` | as resolved | `bundle exec rake build` only when a `*.gemspec` exists and the Rakefile requires `bundler\u002Fgem_tasks`, else `none (application, no build task)` | `bundle exec rake -T test` lists the task for rake-based runners; `command -v bundle` | rspec `N examples, N failures`; minitest `N runs, N assertions, N failures, N errors` | `0 examples` or `0 runs` exits 0 and is `skipped` |\n| **Flutter\u002FDart** | `pubspec.yaml`; Flutter when `sdk: flutter` appears under `dependencies`, else Dart | `flutter test` (Dart: `dart test`) | `flutter analyze` (Dart: `dart analyze`); `flutter build \u003Ctarget>` only when the matching platform directory (`android\u002F`, `ios\u002F`, `web\u002F`, `macos\u002F`, `linux\u002F`, `windows\u002F`) exists and the consumer asked for an artifact; never `flutter build apk` on a project with no `android\u002F` | `command -v flutter` (or `dart`) and `test\u002F` contains at least one `*_test.dart` | \"All tests passed!\", \"Some tests failed.\", \"No tests ran.\"; analyze \"No issues found!\" | \"No tests ran.\" exits 79: read the line, not the code; `skipped`, not `fail` |\n\n### Cross-cutting rules\n\n1. Exit 0 is not evidence. The summary line must show at least one test executed; otherwise the outcome is `skipped`.\n2. Compare exit codes as zero versus nonzero, never `== 1`. pytest and unittest exit 5 when nothing ran, the Dart test runner exits 79, cargo exits 101, and mocha exits the failure count.\n3. Never let a runner wait. `CI=true` on every Node script, `vitest run` in place of a bare `vitest` script, and the consumer's own wait rules for cold builds.\n4. A command is runnable only when the tool is on `PATH` and the script or task is declared. Otherwise it is `none`.\n5. A failure whose first error line names a service, port, or environment variable (a `docker-compose.yml`, `.env.example`, or `DATABASE_URL` in test config is the usual signal) is reported verbatim and flagged as environmental. It is not counted as a code failure and not retried.\n\n## Evidence Rule\n\n- **Pass** is this run's exit code plus the runner's summary line, from a run made after the last edit. When the runner prints no summary, the last output line stands in.\n- **Fail** is the first failing test name plus the first error line. More output belongs in a report file, not in the evidence line.\n- **Skipped** carries its reason: `none` from resolution, a failed confirmation, or a zero-test run. It never counts as a pass; a consumer that requires a pass treats skipped as not passed.\n- **No evidence means not run.** \"Should pass\", \"ran earlier\", and \"the change is safe\" are not outcomes.\n- **A command that has not returned is not a pass.** Waiting for it is the consumer's business.\n\nConsumers quote the outcome in one of these line formats:\n\n```\npass:    \u003Ccommand> -> exit 0: \u003Csummary line>\nfail:    \u003Ccommand> -> exit \u003Ccode>: \u003Cfirst failing test> -- \u003Cfirst error line>\nskipped: \u003Creason>\n```\n\n## For Skill Authors\n\n- Read this file at the verification step, not at skill start.\n- Resolve once per run in the controller and pass the resolved command into any subagent prompt as a literal (`Test command: npm test`), never as \"detect the test command\".\n- Require the evidence line format back from a subagent, and paste the `### Subagent restatement` below into its prompt verbatim. It is the only text from this file that is copied anywhere, and `tests\u002Fskills\u002Ftest-verification-contract.sh` compares the copies to it.\n- Do not restate the resolution table. When a stack is missing, add a row here.\n\n### Subagent restatement\n\nRun the test command you were given exactly as written, and report a pass only by quoting this run's exit code and the runner's summary line -- a run that executed zero tests, a command that has not returned, or a result remembered from an earlier run is not a pass. On failure, quote the first failing test name and the first error line.\n",{"name":5,"description":7,"user-invocable":38},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fyagizdo\u002Fquiver\u002Fskills\u002Fverification",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill verification",{"tool":58,"command":59},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill verification",{"tool":61,"command":62},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill verification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyagizdo\u002Fquiver\u002Fskills\u002Fverification\u002FSKILL.md",true,[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"TEST-PLAN.md","REFERENCE","参考文档",1733,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyagizdo\u002Fquiver\u002Fskills\u002Fverification\u002FTEST-PLAN.md",[73,83,91,99,107,115],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":82},"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":82},"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":82},"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":82},"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":82},"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":82},"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",[],[]]