[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MJSN6VMKMDNXKPWK2QX1KF":3,"skill-same:01M6MJSN6VMKMDNXKPWK2QX1KF":71},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6MJSN6VMKMDNXKPWK2QX1KF","structured-output-file-integrity",null,"Use when saving, regenerating, reviewing, or transforming local TSV, CSV, JSONL, or table-shaped outputs where row count, row order, stable ids, headers, or schema must be preserved.","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\u002Fnebelov\u002Fyandex-direct-for-all\u002Fskills\u002Fstructured-output-file-integrity\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"file","integrity","structured output file integrity","structured","structured output","output","when","outputs","count","jsonl","headers","local","schema","use","table","ids","csv","2026-11-10 10:12:30",false,"---\nname: structured-output-file-integrity\ndescription: Use when saving, regenerating, reviewing, or transforming local TSV, CSV, JSONL, or table-shaped outputs where row count, row order, stable ids, headers, or schema must be preserved.\n---\n\n# Structured Output File Integrity\n\nUse this skill for local structured files and pasted structured answers that must be saved without silent row loss, re-keying, reordering, schema drift, or invented rows.\n\nThis also applies to single JSON deliverables that contain arrays or object\ncollections, such as role results, scored candidates, media plans, validation\npackets, and other schema-bound local artifacts. A JSON file does not become\nsafe just because it is one document instead of JSONL.\n\n## Core Rule\n\nWhen the user asks to save, repair, or transform an existing TSV\u002FCSV\u002FJSONL\u002Ftable output, preserve the declared structure unless the user explicitly authorizes a structural change.\n\n## Required Checks\n\nWhen extracting a registry or other table from a multi-table document, identify\nthe intended container by its headings, expected columns and surrounding\ncontext before comparing rows. The first table is not a default semantic match.\nZero or several matching containers means unresolved selection, not an empty\nregistry. Use a positional table index only after identifying the container,\nthen perform the key, schema and count checks below.\n\n1. Identify stable row keys before writing: `candidate_id`, `row_id`, `id`, primary key, or a deterministic composite if no single key exists.\n   For JSON arrays or object collections, identify the stable object key before\n   editing, for example `candidate_code`, `role_id`, `slug`, `rank`, or a\n   documented composite. Do not patch by broad text replacement when the same\n   wording can occur in another object.\n2. Preserve header fields, delimiter, row order, and every stable row key unless the current task explicitly permits changing them.\n   Derive validation constraints from the declared format and actual source\n   records. Do not reject established representations, such as same-origin\n   relative API URLs, merely because a new checker assumed absolute URLs.\n3. After writing, compare the source and destination:\n   - header equality or documented approved header change;\n   - row count;\n   - stable row-key set;\n   - duplicate key count;\n   - order of stable keys when order matters.\n   For scripted rewrites, write to a temporary sibling file first. Parse and\n   validate its schema and keys before atomically replacing the original, so\n   an exception during serialization cannot leave only a header or partial rows.\n   When using Python `csv`, set `lineterminator='\\n'` if the source uses LF;\n   the writer's default CRLF otherwise changes line endings even when parsed\n   values match.\n   Before reading a TSV\u002FCSV whose fields may contain long source evidence or\n   serialized arrays, raise Python's default 131072-byte CSV field limit (for\n   example, `csv.field_size_limit(sys.maxsize)`, or the largest supported\n   value on that platform). A `field larger than field limit` parser error is\n   not evidence of a damaged row; never skip or truncate that row to proceed.\n4. Remove tool-wrapper or transcript contamination before saving: shell warnings, truncation notices, command banners, assistant prose, Markdown fences, pasted log headers, and other non-table lines must not be mixed into TSV\u002FCSV\u002FJSONL content. If such lines are present in the source transcript, filter them by schema and stable keys before writing.\n5. Do not trust line count alone. A file can have the expected number of lines and still lose one source row, duplicate another, change keys, or include warning\u002Fprose lines in place of data.\n   Calculate reported CSV\u002FTSV volumes from parsed data records, excluding the\n   header. Never use `wc -l` as the delivered record count: it includes the header\n   and may count multiline fields as several lines. Describe uniqueness using\n   the actual deduplication key, including language or other composite fields.\n6. If the output came from a previous assistant answer, reconstruct the source row-key set from that answer or the original source file before saving.\n7. If any key is missing, new, duplicated, reordered without approval, or replaced by a non-data line, stop and repair before reporting completion.\n8. If a structured source has already been pinned by a passport, checksum, signed decision, or mutation journal, treat those exact bytes as immutable after the external write. Record later owner decisions, application outcomes, and status transitions in a separate decision or result artifact. Before editing such a source, check whether any existing passport or completed write references its digest; editing the pinned source would invalidate the audit chain.\n\nFor JSON object collections, after each write parse the file and compare the\ntarget object and its siblings separately. Confirm the intended object changed,\nunrelated sibling objects kept their key sets and substantive fields, object\ncount and ordering are still correct, ranking or shortlist counters still match\nthe collection, and every declared schema or media-format constraint still\npasses. A parser pass alone is not enough if the wrong object was edited.\n\n## Dictionary Matching and Reference Labels\n\nBefore building a reference set for classification, inspect actual dictionary values and their relationships, not just column names. A field named \"brand attribute\" can contain generic product descriptions and need not require a named brand. Do not mark such fields missing solely because another field is absent. Do not add properties from a dictionary label that the source does not establish. If several labels remain valid, record ambiguity or explicit acceptable alternatives before model evaluation. Freeze the reference before model calls; record later adjudication separately, and distinguish exact label agreement from factual correctness.\n\n## Compact model classification transport\n\nWhen a large row set is classified through a model, a compact batch response may use short batch-local codes instead of repeating long source phrases and global identifiers. Keep an immutable map from each code to the original stable row key and source text outside the model response. Rejoin only through that map, then verify one verdict per assigned row, no unknown or duplicate codes, original order when required, and explicit preservation of uncertain or abstained results. A shorter response reduces transport size; it does not establish semantic accuracy.\n\n## Control Character Checks\n\nFor JavaScript builders in directories with spaces or non-ASCII names, convert `import.meta.url` or a relative file URL with `fileURLToPath` from `node:url` before using filesystem APIs. `new URL(...).pathname` remains percent-encoded and is not a valid local filesystem path for those directories. Verify the resolved input path exists before authoring.\n\nWhen transforming TSV, CSV, JSONL, or pasted table output, inspect invisible control characters after writing. This includes carriage returns inside fields, mixed CRLF\u002FLF drift, embedded tabs in TSV fields, null bytes, ANSI escapes, and other non-printing characters that can shift columns without changing visible row counts.\n\nFor TSV\u002FCSV, run a parser-level check as well as a text-level scan. If a field append or merge introduces hidden `\\r` characters, extra delimiters, or multiline field drift that was not explicitly allowed, block closeout and regenerate from the structured source rather than hand-editing visible rows only.\n\nFor JSONL, read records by actual newline boundaries (`for line in file` or an explicit `split('\\n')` on a complete string). Do not use Python `str.splitlines()` to address JSONL rows: it also splits Unicode line-separator characters such as U+2028 that can occur legally inside a JSON string. Before batch writes, parse and count every selected record; if a transport tool truncates a batch, reduce only that batch size and resume from the first unconfirmed row.\n\n## Reporting\n\nReport the human-readable file path, row count, key field used, and whether the key-set comparison passed. Do not dump large table contents to chat.\n","# Structured Output File Integrity\n\nUse this skill for local structured files and pasted structured answers that must be saved without silent row loss, re-keying, reordering, schema drift, or invented rows.\n\nThis also applies to single JSON deliverables that contain arrays or object\ncollections, such as role results, scored candidates, media plans, validation\npackets, and other schema-bound local artifacts. A JSON file does not become\nsafe just because it is one document instead of JSONL.\n\n## Core Rule\n\nWhen the user asks to save, repair, or transform an existing TSV\u002FCSV\u002FJSONL\u002Ftable output, preserve the declared structure unless the user explicitly authorizes a structural change.\n\n## Required Checks\n\nWhen extracting a registry or other table from a multi-table document, identify\nthe intended container by its headings, expected columns and surrounding\ncontext before comparing rows. The first table is not a default semantic match.\nZero or several matching containers means unresolved selection, not an empty\nregistry. Use a positional table index only after identifying the container,\nthen perform the key, schema and count checks below.\n\n1. Identify stable row keys before writing: `candidate_id`, `row_id`, `id`, primary key, or a deterministic composite if no single key exists.\n   For JSON arrays or object collections, identify the stable object key before\n   editing, for example `candidate_code`, `role_id`, `slug`, `rank`, or a\n   documented composite. Do not patch by broad text replacement when the same\n   wording can occur in another object.\n2. Preserve header fields, delimiter, row order, and every stable row key unless the current task explicitly permits changing them.\n   Derive validation constraints from the declared format and actual source\n   records. Do not reject established representations, such as same-origin\n   relative API URLs, merely because a new checker assumed absolute URLs.\n3. After writing, compare the source and destination:\n   - header equality or documented approved header change;\n   - row count;\n   - stable row-key set;\n   - duplicate key count;\n   - order of stable keys when order matters.\n   For scripted rewrites, write to a temporary sibling file first. Parse and\n   validate its schema and keys before atomically replacing the original, so\n   an exception during serialization cannot leave only a header or partial rows.\n   When using Python `csv`, set `lineterminator='\\n'` if the source uses LF;\n   the writer's default CRLF otherwise changes line endings even when parsed\n   values match.\n   Before reading a TSV\u002FCSV whose fields may contain long source evidence or\n   serialized arrays, raise Python's default 131072-byte CSV field limit (for\n   example, `csv.field_size_limit(sys.maxsize)`, or the largest supported\n   value on that platform). A `field larger than field limit` parser error is\n   not evidence of a damaged row; never skip or truncate that row to proceed.\n4. Remove tool-wrapper or transcript contamination before saving: shell warnings, truncation notices, command banners, assistant prose, Markdown fences, pasted log headers, and other non-table lines must not be mixed into TSV\u002FCSV\u002FJSONL content. If such lines are present in the source transcript, filter them by schema and stable keys before writing.\n5. Do not trust line count alone. A file can have the expected number of lines and still lose one source row, duplicate another, change keys, or include warning\u002Fprose lines in place of data.\n   Calculate reported CSV\u002FTSV volumes from parsed data records, excluding the\n   header. Never use `wc -l` as the delivered record count: it includes the header\n   and may count multiline fields as several lines. Describe uniqueness using\n   the actual deduplication key, including language or other composite fields.\n6. If the output came from a previous assistant answer, reconstruct the source row-key set from that answer or the original source file before saving.\n7. If any key is missing, new, duplicated, reordered without approval, or replaced by a non-data line, stop and repair before reporting completion.\n8. If a structured source has already been pinned by a passport, checksum, signed decision, or mutation journal, treat those exact bytes as immutable after the external write. Record later owner decisions, application outcomes, and status transitions in a separate decision or result artifact. Before editing such a source, check whether any existing passport or completed write references its digest; editing the pinned source would invalidate the audit chain.\n\nFor JSON object collections, after each write parse the file and compare the\ntarget object and its siblings separately. Confirm the intended object changed,\nunrelated sibling objects kept their key sets and substantive fields, object\ncount and ordering are still correct, ranking or shortlist counters still match\nthe collection, and every declared schema or media-format constraint still\npasses. A parser pass alone is not enough if the wrong object was edited.\n\n## Dictionary Matching and Reference Labels\n\nBefore building a reference set for classification, inspect actual dictionary values and their relationships, not just column names. A field named \"brand attribute\" can contain generic product descriptions and need not require a named brand. Do not mark such fields missing solely because another field is absent. Do not add properties from a dictionary label that the source does not establish. If several labels remain valid, record ambiguity or explicit acceptable alternatives before model evaluation. Freeze the reference before model calls; record later adjudication separately, and distinguish exact label agreement from factual correctness.\n\n## Compact model classification transport\n\nWhen a large row set is classified through a model, a compact batch response may use short batch-local codes instead of repeating long source phrases and global identifiers. Keep an immutable map from each code to the original stable row key and source text outside the model response. Rejoin only through that map, then verify one verdict per assigned row, no unknown or duplicate codes, original order when required, and explicit preservation of uncertain or abstained results. A shorter response reduces transport size; it does not establish semantic accuracy.\n\n## Control Character Checks\n\nFor JavaScript builders in directories with spaces or non-ASCII names, convert `import.meta.url` or a relative file URL with `fileURLToPath` from `node:url` before using filesystem APIs. `new URL(...).pathname` remains percent-encoded and is not a valid local filesystem path for those directories. Verify the resolved input path exists before authoring.\n\nWhen transforming TSV, CSV, JSONL, or pasted table output, inspect invisible control characters after writing. This includes carriage returns inside fields, mixed CRLF\u002FLF drift, embedded tabs in TSV fields, null bytes, ANSI escapes, and other non-printing characters that can shift columns without changing visible row counts.\n\nFor TSV\u002FCSV, run a parser-level check as well as a text-level scan. If a field append or merge introduces hidden `\\r` characters, extra delimiters, or multiline field drift that was not explicitly allowed, block closeout and regenerate from the structured source rather than hand-editing visible rows only.\n\nFor JSONL, read records by actual newline boundaries (`for line in file` or an explicit `split('\\n')` on a complete string). Do not use Python `str.splitlines()` to address JSONL rows: it also splits Unicode line-separator characters such as U+2028 that can occur legally inside a JSON string. Before batch writes, parse and count every selected record; if a transport tool truncates a batch, reduce only that batch size and resume from the first unconfirmed row.\n\n## Reporting\n\nReport the human-readable file path, row count, key field used, and whether the key-set comparison passed. Do not dump large table contents to chat.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fnebelov\u002Fyandex-direct-for-all\u002Fskills\u002Fstructured-output-file-integrity",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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill structured-output-file-integrity",{"tool":57,"command":58},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill structured-output-file-integrity",{"tool":60,"command":61},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill structured-output-file-integrity","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnebelov\u002Fyandex-direct-for-all\u002Fskills\u002Fstructured-output-file-integrity\u002FSKILL.md",true,[65],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"agents\u002Fopenai.yaml","REFERENCE","参考文档",311,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnebelov\u002Fyandex-direct-for-all\u002Fskills\u002Fstructured-output-file-integrity\u002Fagents\u002Fopenai.yaml",[72,82,90,98,106,114],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":81},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":81},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":81},"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":81},"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":81},"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",[],[]]