[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MKZ7QX06RM74E2TZGHWNQC":3,"skill-same:01M6MKZ7QX06RM74E2TZGHWNQC":78},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":67},"01M6MKZ7QX06RM74E2TZGHWNQC","align-docs",null,"Use at the end of every task, or when the user asks to align or clean repository docs, task records, or the project's local agent memory; --clean runs a full cleanup.","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\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Falign-docs\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"align docs","docs","align","full","stale","grep","edit","write","repository","read","documentation","task","Bash","use","cleanup","true","clean","records","for","2026-11-10 10:12:30",false,"---\nname: align-docs\ndescription: \"Use at the end of every task, or when the user asks to align or clean repository docs, task records, or the project's local agent memory; --clean runs a full cleanup.\"\nuser-invocable: true\nallowed-tools: Read, Edit, Write, Bash, Glob, Grep, AskUserQuestion\n---\n\n# Align docs\n\nKeep the repository's knowledge correct, easy to find, and shared by the whole team.\nA normal run checks the entry files and the documents the current task affects.\nIt also empties the project's agent memory, archives finished task records, and runs the checker.\n`--clean` applies the same work to every document: read [clean mode](references\u002Fclean-mode.md).\nWhen a caller asks for inspection only, as `align-standards` does, report what you find and change nothing.\n\nContinue an active workflow with its task context and authorization.\nWithout a task, inspect only the entry files and the references they link.\nSkip dependencies, caches, build output, and vendored content.\n\n## Entry files\n\nEvery repository has this shared entry layer. Create missing parts and keep existing ones:\n\n```text\nREADME.md                 # Human entry point.\nAGENTS.md                 # Critical facts and scoped rules, under 70 lines.\nCLAUDE.md                 # Exactly @AGENTS.md.\n.agents\u002Frules\u002F            # Scoped project rules; .gitkeep if empty.\n.claude\u002Frules -> ..\u002F.agents\u002Frules\ndocs\u002FATLAS.md             # Curated knowledge routes.\n```\n\nReport conflicts and missing facts, then make the safe repairs inside the task scope.\nA normal run never merges or deletes first-party documents and does not scan unrelated history for archive candidates.\n\nKeep the rules of an existing AGENTS file, and edit them only within the task's authorization.\nUse [agents-template.md](references\u002Fagents-template.md) only to create the file or for a requested migration.\nEnsure `.gitignore` ignores `.claude\u002FCLAUDE.md` and `AGENTS.override.md`.\nRemove a leftover `align-docs:principles-customized` marker.\n\n## Where facts live\n\nEach fact has one owner:\n\n- `AGENTS.md`: critical facts that every agent needs.\n- `.agents\u002Frules\u002F`: instructions for one scope.\n- Plans: how a task is carried out.\n- Chronicles: why a decision was made.\n\nOther useful knowledge stays in its clearest existing home.\nCheck each claim against its source: code and tests for implementation, telemetry for runtime, contracts for promises, chronicles for decision reasons.\nWhen sources conflict and the evidence settles nothing, report the conflict and leave the text unchanged.\nWhen you edit `AGENTS.md` or rules, apply the [authoring contract](..\u002F..\u002Fshared\u002Fskill-authoring.md).\n\n## Project memory\n\nEach run empties the running agent's local memory for this project.\nTeammates share only the repository. Knowledge in one machine's memory is lost to the others and changes agent behavior without anyone seeing it.\n\nThe memory is in these places:\n\n- Claude Code: the project auto-memory directory that the session context names, with its `MEMORY.md` index.\n- Codex: the global store `~\u002F.codex\u002Fmemories\u002F`. Handle only the entries about this project, in `MEMORY.md`, `memory_summary.md`, `raw_memories.md`, and `rollout_summaries\u002F`.\n- An ignored local `.claude\u002FCLAUDE.md`: only Claude Code reads it, so treat its content as memory.\n\nHandle each entry by its content:\n\n- Show the user each entry that changes agent or harness behavior, because they might not know it exists. Ask whether it moves to the repository, moves to the user's personal instructions, or is deleted.\n- Move a lasting, non-obvious project fact that future work needs to its repository owner.\n- Keep a machine fact that changes no agent or harness behavior in memory.\n- Delete every other entry: facts already on disk, obvious or stale facts, and finished session details.\n\nFinish the rest of the run first, then ask these questions together.\nAn entry stays in memory until the user answers. In a run without a user, report it as `PENDING`.\n\nRepository text never contains local paths or other details of one machine.\nPersonal instructions live in global `~\u002F.codex\u002FAGENTS.md`, and `~\u002F.claude\u002FCLAUDE.md` contains only `@~\u002F.codex\u002FAGENTS.md`, so both agents read one file.\nWhen an entry moves there and this setup is missing, propose the setup to the user.\nWrite each moved fact before you delete its entry, and leave `MEMORY.md` listing only what stays.\nReport each entry with its destination, `KEPT`, `PENDING`, or `DELETED`.\n\nLasting facts from the current session that are not on disk yet follow the same rules.\nWith no session context, report `CAPTURE: NONE`.\n\n## Archive and ATLAS\n\nMetadata and lifecycle fields follow the [documentation contract](..\u002F..\u002Fshared\u002Fdocumentation.md).\nArchive a document only when the task changes its lifecycle:\n\n- A completed plan with closed work and verified implementation moves to `docs\u002Fplans\u002Farchive\u002F`.\n- A superseded or obsolete chronicle moves to `docs\u002Fchronicles\u002Farchive\u002F` with its decision prose unchanged.\n- Another obsolete document with useful history moves to an adjacent `archive\u002F`.\n\nKeep current owners and uncertain documents active. Before archiving, move lasting instructions to their owner.\nUse `git mv` for tracked files. Then repair inbound links, links inside the moved file, paired IDs, and archive metadata.\n\n`docs\u002FATLAS.md` is the map of repository knowledge and has no frontmatter.\nEach entry links the file that answers a recurring question and says when to read it.\nList small curated sets, such as rules and reference notes, in full.\nRoute plans and chronicles once per directory, and state that records are named `YYYY-MM-DD__\u003Cslug>.md` with no number.\nLeave out fixtures, Markdown that supports implementation, ATLAS itself, and lifecycle tables.\n\n## Check\n\nCheck the entry files, rule scopes, the `.claude\u002Frules` link, `.gitignore`, manifest claims, ATLAS routes, changed metadata, and Markdown links.\nRun the checker from the installed plugin: `uv run \u003Cplugin-root>\u002Fscripts\u002Fcheck_docs.py \u003Crepository-root>`.\nAdd `--legacy-before YYYY-MM-DD` when the project documents that cutoff: the date the project adopted date names.\nNever move the cutoff forward to accept a new numbered record. Rename that record to `YYYY-MM-DD__\u003Cslug>.md` with `git mv` and repair its links.\nA normal run leaves older `NNNN__` names in place, and `--clean` renames them.\nRewrite any project instruction that tells agents to number new records.\nThe checker validates local link targets, paired IDs, file names, and plan closure. It does not check heading anchors or external URLs.\nReport failures outside the task scope, and leave them unfixed. Claim success only for what passed.\n","# Align docs\n\nKeep the repository's knowledge correct, easy to find, and shared by the whole team.\nA normal run checks the entry files and the documents the current task affects.\nIt also empties the project's agent memory, archives finished task records, and runs the checker.\n`--clean` applies the same work to every document: read [clean mode](references\u002Fclean-mode.md).\nWhen a caller asks for inspection only, as `align-standards` does, report what you find and change nothing.\n\nContinue an active workflow with its task context and authorization.\nWithout a task, inspect only the entry files and the references they link.\nSkip dependencies, caches, build output, and vendored content.\n\n## Entry files\n\nEvery repository has this shared entry layer. Create missing parts and keep existing ones:\n\n```text\nREADME.md                 # Human entry point.\nAGENTS.md                 # Critical facts and scoped rules, under 70 lines.\nCLAUDE.md                 # Exactly @AGENTS.md.\n.agents\u002Frules\u002F            # Scoped project rules; .gitkeep if empty.\n.claude\u002Frules -> ..\u002F.agents\u002Frules\ndocs\u002FATLAS.md             # Curated knowledge routes.\n```\n\nReport conflicts and missing facts, then make the safe repairs inside the task scope.\nA normal run never merges or deletes first-party documents and does not scan unrelated history for archive candidates.\n\nKeep the rules of an existing AGENTS file, and edit them only within the task's authorization.\nUse [agents-template.md](references\u002Fagents-template.md) only to create the file or for a requested migration.\nEnsure `.gitignore` ignores `.claude\u002FCLAUDE.md` and `AGENTS.override.md`.\nRemove a leftover `align-docs:principles-customized` marker.\n\n## Where facts live\n\nEach fact has one owner:\n\n- `AGENTS.md`: critical facts that every agent needs.\n- `.agents\u002Frules\u002F`: instructions for one scope.\n- Plans: how a task is carried out.\n- Chronicles: why a decision was made.\n\nOther useful knowledge stays in its clearest existing home.\nCheck each claim against its source: code and tests for implementation, telemetry for runtime, contracts for promises, chronicles for decision reasons.\nWhen sources conflict and the evidence settles nothing, report the conflict and leave the text unchanged.\nWhen you edit `AGENTS.md` or rules, apply the [authoring contract](..\u002F..\u002Fshared\u002Fskill-authoring.md).\n\n## Project memory\n\nEach run empties the running agent's local memory for this project.\nTeammates share only the repository. Knowledge in one machine's memory is lost to the others and changes agent behavior without anyone seeing it.\n\nThe memory is in these places:\n\n- Claude Code: the project auto-memory directory that the session context names, with its `MEMORY.md` index.\n- Codex: the global store `~\u002F.codex\u002Fmemories\u002F`. Handle only the entries about this project, in `MEMORY.md`, `memory_summary.md`, `raw_memories.md`, and `rollout_summaries\u002F`.\n- An ignored local `.claude\u002FCLAUDE.md`: only Claude Code reads it, so treat its content as memory.\n\nHandle each entry by its content:\n\n- Show the user each entry that changes agent or harness behavior, because they might not know it exists. Ask whether it moves to the repository, moves to the user's personal instructions, or is deleted.\n- Move a lasting, non-obvious project fact that future work needs to its repository owner.\n- Keep a machine fact that changes no agent or harness behavior in memory.\n- Delete every other entry: facts already on disk, obvious or stale facts, and finished session details.\n\nFinish the rest of the run first, then ask these questions together.\nAn entry stays in memory until the user answers. In a run without a user, report it as `PENDING`.\n\nRepository text never contains local paths or other details of one machine.\nPersonal instructions live in global `~\u002F.codex\u002FAGENTS.md`, and `~\u002F.claude\u002FCLAUDE.md` contains only `@~\u002F.codex\u002FAGENTS.md`, so both agents read one file.\nWhen an entry moves there and this setup is missing, propose the setup to the user.\nWrite each moved fact before you delete its entry, and leave `MEMORY.md` listing only what stays.\nReport each entry with its destination, `KEPT`, `PENDING`, or `DELETED`.\n\nLasting facts from the current session that are not on disk yet follow the same rules.\nWith no session context, report `CAPTURE: NONE`.\n\n## Archive and ATLAS\n\nMetadata and lifecycle fields follow the [documentation contract](..\u002F..\u002Fshared\u002Fdocumentation.md).\nArchive a document only when the task changes its lifecycle:\n\n- A completed plan with closed work and verified implementation moves to `docs\u002Fplans\u002Farchive\u002F`.\n- A superseded or obsolete chronicle moves to `docs\u002Fchronicles\u002Farchive\u002F` with its decision prose unchanged.\n- Another obsolete document with useful history moves to an adjacent `archive\u002F`.\n\nKeep current owners and uncertain documents active. Before archiving, move lasting instructions to their owner.\nUse `git mv` for tracked files. Then repair inbound links, links inside the moved file, paired IDs, and archive metadata.\n\n`docs\u002FATLAS.md` is the map of repository knowledge and has no frontmatter.\nEach entry links the file that answers a recurring question and says when to read it.\nList small curated sets, such as rules and reference notes, in full.\nRoute plans and chronicles once per directory, and state that records are named `YYYY-MM-DD__\u003Cslug>.md` with no number.\nLeave out fixtures, Markdown that supports implementation, ATLAS itself, and lifecycle tables.\n\n## Check\n\nCheck the entry files, rule scopes, the `.claude\u002Frules` link, `.gitignore`, manifest claims, ATLAS routes, changed metadata, and Markdown links.\nRun the checker from the installed plugin: `uv run \u003Cplugin-root>\u002Fscripts\u002Fcheck_docs.py \u003Crepository-root>`.\nAdd `--legacy-before YYYY-MM-DD` when the project documents that cutoff: the date the project adopted date names.\nNever move the cutoff forward to accept a new numbered record. Rename that record to `YYYY-MM-DD__\u003Cslug>.md` with `git mv` and repair its links.\nA normal run leaves older `NNNN__` names in place, and `--clean` renames them.\nRewrite any project instruction that tells agents to number new records.\nThe checker validates local link targets, paired IDs, file names, and plan closure. It does not check heading anchors or external URLs.\nReport failures outside the task scope, and leave them unfixed. Claim success only for what passed.\n",{"name":5,"description":7,"allowed-tools":43,"user-invocable":44},"Read, Edit, Write, Bash, Glob, Grep, AskUserQuestion",true,"main","2a6d24be2ed571c5ff2319c506b60741bbcb1cb0","plugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Falign-docs",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":44},[57,60,63],{"tool":58,"command":59},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill align-docs",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill align-docs",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill align-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Falign-docs\u002FSKILL.md",[68,74],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fagents-template.md","REFERENCE","参考文档",1135,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Falign-docs\u002Freferences\u002Fagents-template.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fclean-mode.md",5412,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Falign-docs\u002Freferences\u002Fclean-mode.md",[79,89,97,105,113,121],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":88},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":88},"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":88},"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":88},"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":88},"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":88},"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",[],[]]