[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MMVCDQ1QY3NVC7Y96FRRTK":3,"skill-same:01M6MMVCDQ1QY3NVC7Y96FRRTK":79},{"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":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6MMVCDQ1QY3NVC7Y96FRRTK","x-repurposer",null,"Repurpose existing content into a native X (Twitter) post or thread. Take a LinkedIn post, blog, YouTube script, or newsletter and rewrite it for X: re-hook for the no-fold first line, refit to 280 chars or a thread, strip off-platform artifacts, run the humanizer, publish via Publora on approval. Not for writing from scratch (use x-post-writer or x-thread-builder), not for auditing a draft (use x-humanizer --mode audit).","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\u002Fsergebulaev\u002Fx-skills\u002Fskills\u002Fx-repurposer\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"x repurposer","writer","first line","for","mode","re","hook","native","linkedin post","line","platform","writing","newsletter","youtube","Fold","builder","take","publish","audit","run","humanizer","2026-11-10 10:12:30",false,"---\nname: x-repurposer\ndescription: \"Repurpose existing content into a native X (Twitter) post or thread. Take a LinkedIn post, blog, YouTube script, or newsletter and rewrite it for X: re-hook for the no-fold first line, refit to 280 chars or a thread, strip off-platform artifacts, run the humanizer, publish via Publora on approval. Not for writing from scratch (use x-post-writer or x-thread-builder), not for auditing a draft (use x-humanizer --mode audit).\"\n---\n\n# X Repurposer\n\nTurn something you already made into a tweet or thread that reads like it was born on X. Repurposing is not copy-paste. A post that killed on LinkedIn will die on X if you paste it: wrong hook, wrong length, wrong rhythm, and artifacts (\"link in bio\", hashtag walls) that scream off-platform.\n\nThis skill transforms, it does not generate. It reads your source, keeps the idea, and rebuilds the delivery for X.\n\n## When to use\n\n- \"Turn this LinkedIn post into a tweet \u002F thread\"\n- \"Repurpose my blog post \u002F newsletter \u002F YouTube script for X\"\n- \"This worked on Threads, adapt it for X\"\n- \"I have a rough idea in another format, make it native here\"\n\nNot for a blank-page draft (use `x-post-writer` for a tweet, `x-thread-builder` for a thread) and not for reviewing an already-X draft (use `x-humanizer --mode audit`).\n\n## How it works\n\n**Voice profile first (all drafts).** If `..\u002F..\u002Freferences\u002Fvoice-profile.md` has `filled: yes`, load it and match the user's voice fingerprint, hard rules, and CTA\u002Flink style throughout. If it is not filled, mention once that `x-humanizer --mode profile` can learn their voice from a few posts, then proceed with the generic voice rules.\n\n**Story bank next.** If `..\u002F..\u002Freferences\u002Fstory-bank.md` has `filled: yes`, load it and take every concrete detail (numbers, dates, named projects, positions) from there instead of asking mid-draft. **Never invent a figure, a date or a client name that is not in the bank or supplied by the user in this conversation.** If the bank has nothing that fits, ask the user, or say once that `x-humanizer --mode interview` fills it in 20 to 40 minutes. A draft with a plausible invented number is worse than a draft with none: one is vague, the other is a retraction.\n\n1. **Take the source.** Any format: a post, a paragraph, a script, a caption, a transcript, a bullet list, a link to read. Ask for the source and the goal (replies \u002F reposts \u002F likes \u002F bookmarks) if not given.\n2. **Extract the spine.** Strip the source platform's shell and pull out the one claim, the one story, or the one number worth keeping. Most repurposing fails because it keeps the words instead of the point.\n3. **Choose the container.** One claim or number -> single tweet. A teach or a build -> thread (hand structure to `x-thread-builder`'s shapes). A LinkedIn carousel or a listicle -> a thread, one slide per tweet, hook rebuilt. A long video -> a thread that delivers the payoff, not a summary.\n4. **Re-hook for X.** X has no \"see more\" fold: line one must land the whole punch. The source's hook almost never survives; write a new first line using a 2026 X formula (see `..\u002F..\u002Freferences\u002Fhook-formulas.md`), picked by the goal.\n5. **Refit the format.** 280 chars on a standard account (emoji count as 2). One idea per tweet, line breaks as beats. Cut the source's connective tissue; X rewards compression.\n6. **Strip off-platform artifacts.** Remove \"link in bio\", \"smash subscribe\", \"read more below\", hashtag walls, @-handles that only exist elsewhere, and any \"as I wrote on LinkedIn\" throat-clearing. A repurposed post should not admit it was repurposed.\n7. **Humanizer pass.** Run the scrub: 2026 AI vocab by density, em dashes above the cap (at most one per tweet, never swapped for a period), stacked rule-of-three triads, generic openers and reveal bridges. Leave a single tweet's rhythm alone; on a thread never insert a punch tweet for variance. Keep the user's real numbers and named entities from the source. Canonical rules: `x-humanizer` V3.\n8. **Approval card.** Show: source -> X mapping (what became what), the container (tweet or N-tweet thread), formula used, char counts, primary goal.\n9. **On approval.** Publish via `lib.publish(kind=\"post\", draft_text=\u003Capproved>, target_url=\"https:\u002F\u002Fx.com\u002Fcompose\u002Ftweet\", platforms=[\u003CX_PLATFORM_ID>], scheduled_time=\u003Ciso_or_None>)`. Publora auto-splits an over-length draft into a numbered thread.\n\n## Native-fit rules (source -> X)\n\n- **LinkedIn post -> X:** cut ~40%. LinkedIn tolerates warm-up; X does not. The LinkedIn hook is usually too long; rewrite it.\n- **Blog \u002F newsletter -> X:** pick the single most quotable claim as the hook, then thread the supporting beats. Do not summarize the whole piece.\n- **YouTube script -> X:** lead with the video's payoff, not its intro. \"Here's what I found\" beats \"In this video\".\n- **Carousel \u002F listicle -> thread:** one item per tweet, each with its own micro-hook, not a wall.\n- **Instagram \u002F TikTok caption -> X:** strip emoji density and hashtag blocks; X reads them as noise.\n\n## Hard rules\n\nGlobal voice rules: see root `SKILL.md` Voice rules. Additional skill-specific rules:\n\n- Keep the source's **claim and facts** intact. Repurposing changes the delivery, never the meaning or the numbers.\n- The new first line must stop the scroll on its own. If it needs line two, rewrite it.\n- Never paste the source verbatim and trim. Rebuild the hook and rhythm from the spine.\n- One specific number where the source offers one. Keep it.\n- Do not hard-sell the user's product. One natural mention max.\n\n## Anti-patterns (skill will refuse)\n\n- Copy-pasting the source with light edits (that is not repurposing).\n- Keeping the source platform's artifacts (\"link in bio\", \"smash subscribe\", hashtag walls).\n- ALL CAPS first line for intensity. Carry it with word choice.\n- Em dashes above the cap (more than one in a tweet), or an em dash swapped for a period.\n- \"The result?\" \u002F \"Here's what\" reveal bridges and staccato stacks added during the rewrite.\n- Rule-of-three lists without specifics.\n- \"leverage\", \"fundamentally\", \"game-changer\", \"deep dive\".\n- An external link in the tweet body (offer a reply).\n- Meta throat-clearing (\"I originally posted this on...\").\n\n## Resources\n\n- `..\u002F..\u002Freferences\u002Fhook-formulas.md` - the 11 X formula skeletons to re-hook with\n- `..\u002F..\u002Freferences\u002Falgorithm-heuristics.md` - 2026 X ranking rules (length, timing, signals)\n\n## Related skills\n\n- `x-post-writer` - write a fresh tweet from scratch\n- `x-thread-builder` - structure a multi-tweet thread (repurposer hands long builds here)\n- `x-humanizer` - scrub AI tells, plus `--mode audit` to review the result\n","# X Repurposer\n\nTurn something you already made into a tweet or thread that reads like it was born on X. Repurposing is not copy-paste. A post that killed on LinkedIn will die on X if you paste it: wrong hook, wrong length, wrong rhythm, and artifacts (\"link in bio\", hashtag walls) that scream off-platform.\n\nThis skill transforms, it does not generate. It reads your source, keeps the idea, and rebuilds the delivery for X.\n\n## When to use\n\n- \"Turn this LinkedIn post into a tweet \u002F thread\"\n- \"Repurpose my blog post \u002F newsletter \u002F YouTube script for X\"\n- \"This worked on Threads, adapt it for X\"\n- \"I have a rough idea in another format, make it native here\"\n\nNot for a blank-page draft (use `x-post-writer` for a tweet, `x-thread-builder` for a thread) and not for reviewing an already-X draft (use `x-humanizer --mode audit`).\n\n## How it works\n\n**Voice profile first (all drafts).** If `..\u002F..\u002Freferences\u002Fvoice-profile.md` has `filled: yes`, load it and match the user's voice fingerprint, hard rules, and CTA\u002Flink style throughout. If it is not filled, mention once that `x-humanizer --mode profile` can learn their voice from a few posts, then proceed with the generic voice rules.\n\n**Story bank next.** If `..\u002F..\u002Freferences\u002Fstory-bank.md` has `filled: yes`, load it and take every concrete detail (numbers, dates, named projects, positions) from there instead of asking mid-draft. **Never invent a figure, a date or a client name that is not in the bank or supplied by the user in this conversation.** If the bank has nothing that fits, ask the user, or say once that `x-humanizer --mode interview` fills it in 20 to 40 minutes. A draft with a plausible invented number is worse than a draft with none: one is vague, the other is a retraction.\n\n1. **Take the source.** Any format: a post, a paragraph, a script, a caption, a transcript, a bullet list, a link to read. Ask for the source and the goal (replies \u002F reposts \u002F likes \u002F bookmarks) if not given.\n2. **Extract the spine.** Strip the source platform's shell and pull out the one claim, the one story, or the one number worth keeping. Most repurposing fails because it keeps the words instead of the point.\n3. **Choose the container.** One claim or number -> single tweet. A teach or a build -> thread (hand structure to `x-thread-builder`'s shapes). A LinkedIn carousel or a listicle -> a thread, one slide per tweet, hook rebuilt. A long video -> a thread that delivers the payoff, not a summary.\n4. **Re-hook for X.** X has no \"see more\" fold: line one must land the whole punch. The source's hook almost never survives; write a new first line using a 2026 X formula (see `..\u002F..\u002Freferences\u002Fhook-formulas.md`), picked by the goal.\n5. **Refit the format.** 280 chars on a standard account (emoji count as 2). One idea per tweet, line breaks as beats. Cut the source's connective tissue; X rewards compression.\n6. **Strip off-platform artifacts.** Remove \"link in bio\", \"smash subscribe\", \"read more below\", hashtag walls, @-handles that only exist elsewhere, and any \"as I wrote on LinkedIn\" throat-clearing. A repurposed post should not admit it was repurposed.\n7. **Humanizer pass.** Run the scrub: 2026 AI vocab by density, em dashes above the cap (at most one per tweet, never swapped for a period), stacked rule-of-three triads, generic openers and reveal bridges. Leave a single tweet's rhythm alone; on a thread never insert a punch tweet for variance. Keep the user's real numbers and named entities from the source. Canonical rules: `x-humanizer` V3.\n8. **Approval card.** Show: source -> X mapping (what became what), the container (tweet or N-tweet thread), formula used, char counts, primary goal.\n9. **On approval.** Publish via `lib.publish(kind=\"post\", draft_text=\u003Capproved>, target_url=\"https:\u002F\u002Fx.com\u002Fcompose\u002Ftweet\", platforms=[\u003CX_PLATFORM_ID>], scheduled_time=\u003Ciso_or_None>)`. Publora auto-splits an over-length draft into a numbered thread.\n\n## Native-fit rules (source -> X)\n\n- **LinkedIn post -> X:** cut ~40%. LinkedIn tolerates warm-up; X does not. The LinkedIn hook is usually too long; rewrite it.\n- **Blog \u002F newsletter -> X:** pick the single most quotable claim as the hook, then thread the supporting beats. Do not summarize the whole piece.\n- **YouTube script -> X:** lead with the video's payoff, not its intro. \"Here's what I found\" beats \"In this video\".\n- **Carousel \u002F listicle -> thread:** one item per tweet, each with its own micro-hook, not a wall.\n- **Instagram \u002F TikTok caption -> X:** strip emoji density and hashtag blocks; X reads them as noise.\n\n## Hard rules\n\nGlobal voice rules: see root `SKILL.md` Voice rules. Additional skill-specific rules:\n\n- Keep the source's **claim and facts** intact. Repurposing changes the delivery, never the meaning or the numbers.\n- The new first line must stop the scroll on its own. If it needs line two, rewrite it.\n- Never paste the source verbatim and trim. Rebuild the hook and rhythm from the spine.\n- One specific number where the source offers one. Keep it.\n- Do not hard-sell the user's product. One natural mention max.\n\n## Anti-patterns (skill will refuse)\n\n- Copy-pasting the source with light edits (that is not repurposing).\n- Keeping the source platform's artifacts (\"link in bio\", \"smash subscribe\", hashtag walls).\n- ALL CAPS first line for intensity. Carry it with word choice.\n- Em dashes above the cap (more than one in a tweet), or an em dash swapped for a period.\n- \"The result?\" \u002F \"Here's what\" reveal bridges and staccato stacks added during the rewrite.\n- Rule-of-three lists without specifics.\n- \"leverage\", \"fundamentally\", \"game-changer\", \"deep dive\".\n- An external link in the tweet body (offer a reply).\n- Meta throat-clearing (\"I originally posted this on...\").\n\n## Resources\n\n- `..\u002F..\u002Freferences\u002Fhook-formulas.md` - the 11 X formula skeletons to re-hook with\n- `..\u002F..\u002Freferences\u002Falgorithm-heuristics.md` - 2026 X ranking rules (length, timing, signals)\n\n## Related skills\n\n- `x-post-writer` - write a fresh tweet from scratch\n- `x-thread-builder` - structure a multi-tweet thread (repurposer hands long builds here)\n- `x-humanizer` - scrub AI tells, plus `--mode audit` to review the result\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fsergebulaev\u002Fx-skills\u002Fskills\u002Fx-repurposer",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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill x-repurposer",{"tool":71,"command":72},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill x-repurposer",{"tool":74,"command":75},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill x-repurposer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Fx-skills\u002Fskills\u002Fx-repurposer\u002FSKILL.md",true,[],[80,90,98,106,114,122],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":89},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":89},"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":89},"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":89},"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":89},"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",[],[]]