[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MD0JXKC1R943APY25S9KYA":3,"skill-same:01M6MD0JXKC1R943APY25S9KYA":85},{"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":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6MD0JXKC1R943APY25S9KYA","since-cutoff",null,"Find which dependency APIs this project's Python code uses changed after the model's training cutoff (no model calls), write short AGENTS.md or CLAUDE.md notes from the API diff, each with its source, and keep them in step with the lockfile; optionally measure which of the changes the model gets wrong. Use when the user asks whether the model knows their library versions, when code keeps failing on renamed or removed library APIs, or after upgrading dependencies. Trigger with requests such as \"does the model know my openai version\", \"scan my dependencies for API changes\" or \"check whether the library notes are up to date\".","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FMohammadHijjawi97\u002Fsince-cutoff\u002Fskills\u002Fsince-cutoff\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"since cutoff","up","failing","when","checker","python code","which","pipx","type checker","project","uv","cli","command","short","model","access","Bash","api","lockfile","code","training","notes","2026-11-10 10:12:30",false,"---\nname: since-cutoff\ndescription: Find which dependency APIs this project's Python code uses changed after the model's training cutoff (no model calls), write short AGENTS.md or CLAUDE.md notes from the API diff, each with its source, and keep them in step with the lockfile; optionally measure which of the changes the model gets wrong. Use when the user asks whether the model knows their library versions, when code keeps failing on renamed or removed library APIs, or after upgrading dependencies. Trigger with requests such as \"does the model know my openai version\", \"scan my dependencies for API changes\" or \"check whether the library notes are up to date\".\nlicense: MIT\ncompatibility: Needs since-cutoff on PATH, or uv or pipx to run it, and network access to PyPI. The run command also needs model access (the claude CLI or a provider API key) and the basedpyright type checker (pip install \"since-cutoff[run]\", or uvx --with basedpyright since-cutoff run); scan, sync and status make no model calls, and status works offline.\nallowed-tools: Bash(since-cutoff scan:*), Bash(since-cutoff sync:*), Bash(since-cutoff status:*), Bash(since-cutoff run:*), Bash(since-cutoff models:*), Bash(since-cutoff unapply:*), Bash(uvx since-cutoff:*), Bash(uvx --with basedpyright since-cutoff:*), Bash(pipx run since-cutoff:*), Read\nmetadata:\n  author: Mohammad Hijjawi\n  version: \"0.5.0\"\n---\n\n# since-cutoff\n\n`since-cutoff` is a command-line tool that finds the APIs a project's dependencies changed after\nthe model's training cutoff and writes notes about them, each with its source. Run the tool and\nreport what it prints.\n\n## Overview\n\n- `since-cutoff scan` compares, for each dependency, the public API of the latest release\n  published at least 30 days before the model's training cutoff (`--cutoff-margin`; 0 compares\n  from the cutoff itself) with the version the project pins (a static diff, no model calls), and\n  lists the changed APIs the code uses.\n- `since-cutoff sync` writes notes from that diff into a marked block in AGENTS.md or CLAUDE.md\n  and keeps them in step with the lockfile; `since-cutoff status` checks the block offline, and\n  `since-cutoff unapply` removes it.\n- `since-cutoff run` is optional. It does the measuring itself by calling a fresh copy of the\n  model with no tools and no project context, so **do not answer the probe tasks yourself and\n  do not guess results**.\n\n## Prerequisites\n\n- A Python project with its dependencies in `pyproject.toml`, `requirements.txt` or a lockfile.\n- since-cutoff on PATH, or uv or pipx to run it (`uvx since-cutoff`, `pipx run since-cutoff`).\n- Network access to PyPI; `status` works offline.\n- For `run` only: model access, through the `claude` CLI for Claude Code models or the\n  provider's API key for other models, and the basedpyright type checker: `pip install\n  \"since-cutoff[run]\"`, or run it as `uvx --with basedpyright since-cutoff run`. Without it,\n  `run` stops at once and says so. `scan`, `sync` and `status` make no model calls.\n\n## Instructions\n\n1. Work from the project root (the directory with `pyproject.toml`, `requirements.txt` or a lockfile).\n2. Pick the command. Use the arguments the user gave, if any (`scan`, `sync`, `status` or `run`,\n   with flags such as `--apply`, `--quick` or `--model`); otherwise:\n   - quick look, no model calls: `since-cutoff scan` (then offer `sync`, step 7)\n   - full measurement, with notes a model writes and keeps only when their example\n     type-checks: `since-cutoff run --quick`\n3. Name the model. Without `--model`, the tool tests the model your coding agent is set up with\n   (`SINCE_CUTOFF_MODEL`; inside Claude Code, only Claude Code's settings; elsewhere the Claude\n   Code, Codex, Gemini CLI, OpenCode and Aider settings, the project's before the user's) and\n   says where it read it (\"model from ...\"). If that is not the model you are, or it warns that\n   no model setting was found, add `--model PROVIDER:MODEL` for the model you are (for example\n   `--model openai:gpt-5.4`, or `--model claude-code:MODEL` for a model picked with `\u002Fmodel`).\n   `run` calls Claude Code models through the `claude` CLI and other models through their\n   provider's API key.\n4. Before `run`, tell the user that it sends prompts (package names, versions, public API\n   signatures and generated tasks, never their source code) to the model provider they choose,\n   uses their API credits or Claude Code usage, and can take 5-20 minutes. Wait for a yes.\n   `scan` needs no confirmation.\n5. Run it. If `since-cutoff` is not installed, use `uvx since-cutoff` with the same arguments\n   (or use `pipx run since-cutoff`); for `run`, `uvx --with basedpyright since-cutoff run`,\n   which adds the type checker. Start `run` in the background or with a long timeout, not a\n   2-minute foreground call. Everything is cached, so re-running after an interruption resumes\n   quickly.\n6. Summarise the result card: the model and its training cutoff, how many dependencies changed\n   after the cutoff, what was stale, and the held-out before\u002Fafter numbers. Quote each interval\n   with the number it belongs to: the bootstrap CI goes with the difference of the task-level\n   rates, the other CI with \"changes fixed: X of Y\". If the run compared baseline notes\n   (`--compare`), give each block's \"changes fixed\" with its CI, and call one block better\n   only when report.md's head-to-head sign test for it has a small p-value.\n7. Only write notes into the user's files if they asked for it. After `scan`, run\n   `since-cutoff sync --dry-run`, show the user the diff it prints, and only when they agree run\n   `since-cutoff sync --yes`: it writes the notes from the API diff into a marked block in\n   AGENTS.md (or CLAUDE.md if that is the file the project uses) and, run again later, keeps\n   them in step with the lockfile. When `scan` suggests `sync --scope imported` (the code uses\n   none of the changed APIs yet), add it to both commands. When the user asks for the\n   configuration the benchmark measured, use `--profile evaluated`; for the shortest block\n   (the changed packages and their versions, no change lines), `--header-only`. After `run`, `--apply` writes that\n   run's notes in place of the whole block; `since-cutoff sync` then adds the notes from the\n   diff for the other changed APIs the code uses, keeping the run's `[type-checked]` ones.\n   `since-cutoff unapply` removes the block again. `since-cutoff status` says, without the\n   network, whether the notes still match the lockfile; from since-cutoff 0.4.0 the Claude Code\n   plugin runs it when a session starts (the first time, uvx downloads since-cutoff).\n\n## Output\n\n- The terminal: the model, its training cutoff and where the tool read the model, the\n  dependencies that changed since the release each is compared from, and the changed APIs the\n  code uses, each with its note. `run` adds the result card of step 6.\n- `.since-cutoff\u002Freport.md`: the full report. Read it when the user wants details.\n- The notes block in AGENTS.md or CLAUDE.md, written only by `sync --yes` or `run --apply`. The\n  notes in it are API reference facts about the versions the project pins: what was removed,\n  renamed or deprecated after the release they compare from (the latest one published at least\n  30 days before your training cutoff), each tagged with what was checked, for example `[diff]`\n  (a static comparison of the two releases' public APIs),\n  `[diff + library]` (the library's own deprecation text names the replacement),\n  `[diff + move checked]`, `[diff + metadata]` (the two releases' Requires-Dist: the package\n  requires another library, such as `httpx2` instead of `httpx`, and its API takes that\n  library's types), `[diff; probable rename]` (a guess, labelled as one) or\n  `[type-checked]` (written during `run`; its example passed the type check). Check them when\n  you write code that uses those libraries, and claim no more than the tag says.\n\n## Error Handling\n\n- No lockfile or pinned versions found: tell the user which file the tool asked for; do not\n  invent versions.\n- A model or login error during `run`: report the message and offer `scan`, which makes no\n  model calls.\n- `sync` exits with code 4: the block was edited by hand. Tell the user, and pass `--force`\n  only if they say so.\n- `sync` without `--yes` asks on the terminal; with no terminal to ask in it writes nothing and\n  exits with code 3. Show the `--dry-run` diff and use `--yes` once the user agrees.\n- `status` exits with code 3 when the notes are out of date: offer `sync` as in step 7.\n- `run` was interrupted: run the same command again; it resumes from the cache.\n\n## Examples\n\n**Example 1: \"Does the model know the library versions this project pins?\"**\n\n```bash\nsince-cutoff scan\n```\n\nSummarise what it lists. If the user wants notes, show the diff and write once they agree:\n\n```bash\nsince-cutoff sync --dry-run\nsince-cutoff sync --yes\n```\n\n**Example 2: \"Measure which of these changes you get wrong, and add the notes.\"**\n\nTell the user what `run` sends, what it costs and how long it takes (step 4). After a yes, start\nit in the background (with `--model` if step 3 calls for it), then show the notes `sync` would\nadd for the other changed APIs:\n\n```bash\nsince-cutoff run --quick --apply\nsince-cutoff sync --dry-run\n```\n\n**Example 3: \"I upgraded openai. Are the notes in AGENTS.md still right?\"**\n\n```bash\nsince-cutoff status\n```\n\nIf the notes are out of date, show the diff of `since-cutoff sync --dry-run` and run\n`since-cutoff sync --yes` once the user agrees; to remove them, `since-cutoff unapply`.\n\n## Quick lookups without a run\n\nIf the since-cutoff MCP server is connected (the Claude Code plugin starts it), its tools answer\nfrom a static diff, with no model calls: `api_changes` (one package, optionally one `symbol`),\n`project_changes` (every dependency of the project) and `model_cutoff`. Pass your own model id\nas `model`. Use them before writing code against a dependency that may be newer than your\ntraining data; use the CLI above when the user wants the model measured or notes written.\n\n## Resources\n\n- [since-cutoff on GitHub](https:\u002F\u002Fgithub.com\u002FMohammadHijjawi97\u002Fsince-cutoff): the README, with\n  every command, flag and exit code, and what each note tag means.\n- [How it works](https:\u002F\u002Fgithub.com\u002FMohammadHijjawi97\u002Fsince-cutoff\u002Fblob\u002Fmain\u002Fdocs\u002Fhow-it-works.md):\n  the diff, the notes and the measurement in detail.\n- [Privacy](https:\u002F\u002Fgithub.com\u002FMohammadHijjawi97\u002Fsince-cutoff\u002Fblob\u002Fmain\u002FPRIVACY.md): what `run`\n  sends to the model provider, and what stays on the machine.\n- [Changelog](https:\u002F\u002Fgithub.com\u002FMohammadHijjawi97\u002Fsince-cutoff\u002Fblob\u002Fmain\u002FCHANGELOG.md): what\n  changed in each release.\n","# since-cutoff\n\n`since-cutoff` is a command-line tool that finds the APIs a project's dependencies changed after\nthe model's training cutoff and writes notes about them, each with its source. Run the tool and\nreport what it prints.\n\n## Overview\n\n- `since-cutoff scan` compares, for each dependency, the public API of the latest release\n  published at least 30 days before the model's training cutoff (`--cutoff-margin`; 0 compares\n  from the cutoff itself) with the version the project pins (a static diff, no model calls), and\n  lists the changed APIs the code uses.\n- `since-cutoff sync` writes notes from that diff into a marked block in AGENTS.md or CLAUDE.md\n  and keeps them in step with the lockfile; `since-cutoff status` checks the block offline, and\n  `since-cutoff unapply` removes it.\n- `since-cutoff run` is optional. It does the measuring itself by calling a fresh copy of the\n  model with no tools and no project context, so **do not answer the probe tasks yourself and\n  do not guess results**.\n\n## Prerequisites\n\n- A Python project with its dependencies in `pyproject.toml`, `requirements.txt` or a lockfile.\n- since-cutoff on PATH, or uv or pipx to run it (`uvx since-cutoff`, `pipx run since-cutoff`).\n- Network access to PyPI; `status` works offline.\n- For `run` only: model access, through the `claude` CLI for Claude Code models or the\n  provider's API key for other models, and the basedpyright type checker: `pip install\n  \"since-cutoff[run]\"`, or run it as `uvx --with basedpyright since-cutoff run`. Without it,\n  `run` stops at once and says so. `scan`, `sync` and `status` make no model calls.\n\n## Instructions\n\n1. Work from the project root (the directory with `pyproject.toml`, `requirements.txt` or a lockfile).\n2. Pick the command. Use the arguments the user gave, if any (`scan`, `sync`, `status` or `run`,\n   with flags such as `--apply`, `--quick` or `--model`); otherwise:\n   - quick look, no model calls: `since-cutoff scan` (then offer `sync`, step 7)\n   - full measurement, with notes a model writes and keeps only when their example\n     type-checks: `since-cutoff run --quick`\n3. Name the model. Without `--model`, the tool tests the model your coding agent is set up with\n   (`SINCE_CUTOFF_MODEL`; inside Claude Code, only Claude Code's settings; elsewhere the Claude\n   Code, Codex, Gemini CLI, OpenCode and Aider settings, the project's before the user's) and\n   says where it read it (\"model from ...\"). If that is not the model you are, or it warns that\n   no model setting was found, add `--model PROVIDER:MODEL` for the model you are (for example\n   `--model openai:gpt-5.4`, or `--model claude-code:MODEL` for a model picked with `\u002Fmodel`).\n   `run` calls Claude Code models through the `claude` CLI and other models through their\n   provider's API key.\n4. Before `run`, tell the user that it sends prompts (package names, versions, public API\n   signatures and generated tasks, never their source code) to the model provider they choose,\n   uses their API credits or Claude Code usage, and can take 5-20 minutes. Wait for a yes.\n   `scan` needs no confirmation.\n5. Run it. If `since-cutoff` is not installed, use `uvx since-cutoff` with the same arguments\n   (or use `pipx run since-cutoff`); for `run`, `uvx --with basedpyright since-cutoff run`,\n   which adds the type checker. Start `run` in the background or with a long timeout, not a\n   2-minute foreground call. Everything is cached, so re-running after an interruption resumes\n   quickly.\n6. Summarise the result card: the model and its training cutoff, how many dependencies changed\n   after the cutoff, what was stale, and the held-out before\u002Fafter numbers. Quote each interval\n   with the number it belongs to: the bootstrap CI goes with the difference of the task-level\n   rates, the other CI with \"changes fixed: X of Y\". If the run compared baseline notes\n   (`--compare`), give each block's \"changes fixed\" with its CI, and call one block better\n   only when report.md's head-to-head sign test for it has a small p-value.\n7. Only write notes into the user's files if they asked for it. After `scan`, run\n   `since-cutoff sync --dry-run`, show the user the diff it prints, and only when they agree run\n   `since-cutoff sync --yes`: it writes the notes from the API diff into a marked block in\n   AGENTS.md (or CLAUDE.md if that is the file the project uses) and, run again later, keeps\n   them in step with the lockfile. When `scan` suggests `sync --scope imported` (the code uses\n   none of the changed APIs yet), add it to both commands. When the user asks for the\n   configuration the benchmark measured, use `--profile evaluated`; for the shortest block\n   (the changed packages and their versions, no change lines), `--header-only`. After `run`, `--apply` writes that\n   run's notes in place of the whole block; `since-cutoff sync` then adds the notes from the\n   diff for the other changed APIs the code uses, keeping the run's `[type-checked]` ones.\n   `since-cutoff unapply` removes the block again. `since-cutoff status` says, without the\n   network, whether the notes still match the lockfile; from since-cutoff 0.4.0 the Claude Code\n   plugin runs it when a session starts (the first time, uvx downloads since-cutoff).\n\n## Output\n\n- The terminal: the model, its training cutoff and where the tool read the model, the\n  dependencies that changed since the release each is compared from, and the changed APIs the\n  code uses, each with its note. `run` adds the result card of step 6.\n- `.since-cutoff\u002Freport.md`: the full report. Read it when the user wants details.\n- The notes block in AGENTS.md or CLAUDE.md, written only by `sync --yes` or `run --apply`. The\n  notes in it are API reference facts about the versions the project pins: what was removed,\n  renamed or deprecated after the release they compare from (the latest one published at least\n  30 days before your training cutoff), each tagged with what was checked, for example `[diff]`\n  (a static comparison of the two releases' public APIs),\n  `[diff + library]` (the library's own deprecation text names the replacement),\n  `[diff + move checked]`, `[diff + metadata]` (the two releases' Requires-Dist: the package\n  requires another library, such as `httpx2` instead of `httpx`, and its API takes that\n  library's types), `[diff; probable rename]` (a guess, labelled as one) or\n  `[type-checked]` (written during `run`; its example passed the type check). Check them when\n  you write code that uses those libraries, and claim no more than the tag says.\n\n## Error Handling\n\n- No lockfile or pinned versions found: tell the user which file the tool asked for; do not\n  invent versions.\n- A model or login error during `run`: report the message and offer `scan`, which makes no\n  model calls.\n- `sync` exits with code 4: the block was edited by hand. Tell the user, and pass `--force`\n  only if they say so.\n- `sync` without `--yes` asks on the terminal; with no terminal to ask in it writes nothing and\n  exits with code 3. Show the `--dry-run` diff and use `--yes` once the user agrees.\n- `status` exits with code 3 when the notes are out of date: offer `sync` as in step 7.\n- `run` was interrupted: run the same command again; it resumes from the cache.\n\n## Examples\n\n**Example 1: \"Does the model know the library versions this project pins?\"**\n\n```bash\nsince-cutoff scan\n```\n\nSummarise what it lists. If the user wants notes, show the diff and write once they agree:\n\n```bash\nsince-cutoff sync --dry-run\nsince-cutoff sync --yes\n```\n\n**Example 2: \"Measure which of these changes you get wrong, and add the notes.\"**\n\nTell the user what `run` sends, what it costs and how long it takes (step 4). After a yes, start\nit in the background (with `--model` if step 3 calls for it), then show the notes `sync` would\nadd for the other changed APIs:\n\n```bash\nsince-cutoff run --quick --apply\nsince-cutoff sync --dry-run\n```\n\n**Example 3: \"I upgraded openai. Are the notes in AGENTS.md still right?\"**\n\n```bash\nsince-cutoff status\n```\n\nIf the notes are out of date, show the diff of `since-cutoff sync --dry-run` and run\n`since-cutoff sync --yes` once the user agrees; to remove them, `since-cutoff unapply`.\n\n## Quick lookups without a run\n\nIf the since-cutoff MCP server is connected (the Claude Code plugin starts it), its tools answer\nfrom a static diff, with no model calls: `api_changes` (one package, optionally one `symbol`),\n`project_changes` (every dependency of the project) and `model_cutoff`. Pass your own model id\nas `model`. Use them before writing code against a dependency that may be newer than your\ntraining data; use the CLI above when the user wants the model measured or notes written.\n\n## Resources\n\n- [since-cutoff on GitHub](https:\u002F\u002Fgithub.com\u002FMohammadHijjawi97\u002Fsince-cutoff): the README, with\n  every command, flag and exit code, and what each note tag means.\n- [How it works](https:\u002F\u002Fgithub.com\u002FMohammadHijjawi97\u002Fsince-cutoff\u002Fblob\u002Fmain\u002Fdocs\u002Fhow-it-works.md):\n  the diff, the notes and the measurement in detail.\n- [Privacy](https:\u002F\u002Fgithub.com\u002FMohammadHijjawi97\u002Fsince-cutoff\u002Fblob\u002Fmain\u002FPRIVACY.md): what `run`\n  sends to the model provider, and what stays on the machine.\n- [Changelog](https:\u002F\u002Fgithub.com\u002FMohammadHijjawi97\u002Fsince-cutoff\u002Fblob\u002Fmain\u002FCHANGELOG.md): what\n  changed in each release.\n",{"name":5,"license":15,"metadata":56,"description":7,"allowed-tools":59,"compatibility":60},{"author":57,"version":58},"Mohammad Hijjawi","0.5.0","Bash(since-cutoff scan:*), Bash(since-cutoff sync:*), Bash(since-cutoff status:*), Bash(since-cutoff run:*), Bash(since-cutoff models:*), Bash(since-cutoff unapply:*), Bash(uvx since-cutoff:*), Bash(uvx --with basedpyright since-cutoff:*), Bash(pipx run since-cutoff:*), Read","Needs since-cutoff on PATH, or uv or pipx to run it, and network access to PyPI. The run command also needs model access (the claude CLI or a provider API key) and the basedpyright type checker (pip install \"since-cutoff[run]\", or uvx --with basedpyright since-cutoff run); scan, sync and status make no model calls, and status works offline.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FMohammadHijjawi97\u002Fsince-cutoff\u002Fskills\u002Fsince-cutoff",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":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill since-cutoff",{"tool":77,"command":78},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill since-cutoff",{"tool":80,"command":81},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill since-cutoff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FMohammadHijjawi97\u002Fsince-cutoff\u002Fskills\u002Fsince-cutoff\u002FSKILL.md",true,[],[86,95,103,111,119,127],{"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":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":94},"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.","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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":94},"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":94},"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":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":94},"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":94},"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":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":94},"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",[],[]]