[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MHY2X8PWP44RYR3A3D22SQ":3,"skill-same:01M6MHY2X8PWP44RYR3A3D22SQ":74},{"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":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6MHY2X8PWP44RYR3A3D22SQ","upwork-application-session",null,"Use when the user wants to search Upwork, qualify roles, draft proposals, submit applications, or continue an active Upwork application session. This skill uses a Chrome CDP workflow, payload JSON files, sequential browser actions, connect-budget tracking, and final success confirmation through Upwork proposal URLs.","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\u002Fklajdikkolaj\u002Fupwork-autopilot\u002Fskills\u002Fupwork-application-session\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"upwork application session","application","session","when","workflow","qualify","proposal","submit","active","cdp","files","payload","proposals","confirmation","continue","applications","Budget","actions","search","browser","connect","2026-11-10 10:12:30",false,"---\nname: upwork-application-session\ndescription: Use when the user wants to search Upwork, qualify roles, draft proposals, submit applications, or continue an active Upwork application session. This skill uses a Chrome CDP workflow, payload JSON files, sequential browser actions, connect-budget tracking, and final success confirmation through Upwork proposal URLs.\n---\n\n# Upwork Application Session\n\nUse this skill for real Upwork application work. Prefer the Chrome CDP path. Only use Atlas if JavaScript execution is confirmed to work there.\n\n## Read first\n\n- First try `..\u002F..\u002Fconfig\u002Fapplicant-profile.local.md`\n- If that file does not exist in the cache copy, fall back to `$HOME\u002Fplugins\u002Fupwork-autopilot\u002Fconfig\u002Fapplicant-profile.local.md`\n- If that file does not exist, run `node ..\u002F..\u002Fscripts\u002Fsetup-applicant-profile.mjs`\n- Then read `..\u002F..\u002Fconfig\u002Fsearch-profile.local.json` if it exists\n- If that file does not exist in the cache copy, fall back to `$HOME\u002Fplugins\u002Fupwork-autopilot\u002Fconfig\u002Fsearch-profile.local.json`\n- If the local search profile does not exist, use `..\u002F..\u002Fconfig\u002Fsearch-profile.template.json`\n- `..\u002F..\u002Freferences\u002Fsearch-strategy.md`\n\n## Non-negotiables\n\n- Start every cover letter with `Hi,`\n- Tone: friendly, professional, specific, low-fluff.\n- Never invent project examples, metrics, portfolio URLs, or domain history.\n- Never include email, phone, Telegram, WhatsApp, Calendly, or any off-platform contact detail in a proposal.\n- Never attach the CV in this workflow.\n- Do not parallelize browser actions against the live Upwork session.\n- Stop when available Connects drop below `15`.\n- Skip jobs that are already applied, blocked by hard geography, citizenship, or security constraints, or clearly below the user's floor.\n\n## Setup\n\n1. Run `..\u002F..\u002Fscripts\u002Fbootstrap.sh` once from the plugin root.\n2. Ensure the applicant profile exists. If it does not, run `node ..\u002F..\u002Fscripts\u002Fsetup-applicant-profile.mjs`.\n2. Run `..\u002F..\u002Fscripts\u002Flaunch-controlled-chrome.sh` by default to reuse the user's normal logged-in Chrome profile.\n3. If the user explicitly wants a clean browser state, run `..\u002F..\u002Fscripts\u002Flaunch-isolated-chrome.sh` instead.\n4. Ask the user to log into Upwork only if the chosen browser mode is not already signed in.\n5. Run `node ..\u002F..\u002Fscripts\u002Fupwork-session-probe.mjs` to confirm login state.\n6. Export a log path before submissions, for example:\n\n```bash\nexport UPWORK_AUTOPILOT_LOG=$HOME\u002F.codex\u002Fupwork-autopilot\u002Flogs\u002F$(date +%F).jsonl\n```\n\n## Search and qualification\n\n- List search results:\n\n```bash\nnode ..\u002F..\u002Fscripts\u002Fupwork-search-plan.mjs\n```\n\n- A raw keyword is converted into the default filtered Upwork search URL.\n- A full Upwork search URL is accepted as-is.\n- If `upwork-search-plan.mjs` returns multiple URLs, iterate them sequentially.\n- To open a result and inspect the full job page:\n\n```bash\nnode ..\u002F..\u002Fscripts\u002Fupwork-search-inspect.mjs '\u003Csearch-url-or-keyword>' detail 0\n```\n\n- To probe the apply flow for a specific job:\n\n```bash\nnode ..\u002F..\u002Fscripts\u002Fupwork-apply-probe.mjs '\u003Cjob-url>'\n```\n\nApply only if all of these hold:\n\n- the client is payment verified\n- the role is technically relevant\n- the rate is compatible with the user's floor\n- there is no hard location block\n- the role is not already applied\n- any requested proof, portfolio examples, or niche experience can be answered honestly from the profile or current context\n\n## Proposal writing\n\nCreate a payload JSON file with `apply_patch`. The scripts fill fields in DOM order.\n\n```json\n{\n  \"textareas\": [\n    \"Hi,\\n\\n...\"\n  ],\n  \"inputs\": []\n}\n```\n\nRules:\n\n- Before drafting, extract the actual deliverable, stack, client pain point, any written questions, and any request for examples or proof.\n- First paragraph: open casually and directly, and name the actual problem or fit in plain language within the first 2 sentences.\n- Default structure: 3 to 5 short paragraphs in natural prose, not a bullet-heavy sales pitch.\n- Weave relevant experience into the paragraphs instead of defaulting to bullets.\n- Use bullets only when the client explicitly asks for list-style answers or when multiple written questions are easier to answer that way.\n- Proof section: use relevant project evidence from the profile only when it actually matches the post.\n- When the applicant profile includes named project examples, prefer dropping 1 to 3 of the strongest ones naturally into the prose instead of listing every example.\n- If the applicant profile includes `Differentiators to mention when relevant`, use at most 1 or 2 that genuinely strengthen this specific job. Do not force them into unrelated proposals.\n- Closing: use the profile's `Preferred closing CTA` when present, or a close natural variant of it.\n- If the client asks for project examples, case studies, metrics, URLs, or niche background, answer with the closest truthful match from the profile.\n- If the profile does not contain the proof the client is asking for, stop and ask the user for the missing details before submitting. Do not guess.\n- Keep the proposal usually around `220` to `320` words unless the page asks multiple written questions.\n- Answer written questions directly in field order. Do not dodge them with generic sales copy.\n- Use conversational phrasing and contractions when natural. Avoid templated buzzwords, generic praise, AI-sounding filler, and overly heavy systems language unless the post clearly calls for it.\n- If the applicant profile states tone or structure preferences, follow those over the generic defaults in this file.\n- The first line must begin with `Hi,`\n\n## Submission\n\nRun:\n\n```bash\nnode ..\u002F..\u002Fscripts\u002Fupwork-submit-proposal.mjs '\u003Cproposal-url>' \u002Fabs\u002Fpath\u002Fto\u002Fpayload.json\n```\n\nSuccess is confirmed only when the final URL contains `?success`.\n\nThe submit script:\n\n- fills visible `textarea` fields in order\n- fills visible text, url, email, and number inputs in order\n- clicks `Submit a proposal`\n- extracts the success URL and proposal ID\n- appends a JSONL log entry if `UPWORK_AUTOPILOT_LOG` is set\n\n## Failure handling\n\n- If the page opens a video interview flow, skip unless the user explicitly wants that path.\n- If the apply button is disabled, read the probe output before deciding whether to skip.\n- If the form asks for required information that is missing from the profile, stop and ask the user before submitting.\n- If `net::ERR_ABORTED` appears, another command touched the same Upwork tab. Resume with single-threaded browser actions only.\n- If login, CAPTCHA, or 2FA appears, hand control to the user and resume after confirmation.\n","# Upwork Application Session\n\nUse this skill for real Upwork application work. Prefer the Chrome CDP path. Only use Atlas if JavaScript execution is confirmed to work there.\n\n## Read first\n\n- First try `..\u002F..\u002Fconfig\u002Fapplicant-profile.local.md`\n- If that file does not exist in the cache copy, fall back to `$HOME\u002Fplugins\u002Fupwork-autopilot\u002Fconfig\u002Fapplicant-profile.local.md`\n- If that file does not exist, run `node ..\u002F..\u002Fscripts\u002Fsetup-applicant-profile.mjs`\n- Then read `..\u002F..\u002Fconfig\u002Fsearch-profile.local.json` if it exists\n- If that file does not exist in the cache copy, fall back to `$HOME\u002Fplugins\u002Fupwork-autopilot\u002Fconfig\u002Fsearch-profile.local.json`\n- If the local search profile does not exist, use `..\u002F..\u002Fconfig\u002Fsearch-profile.template.json`\n- `..\u002F..\u002Freferences\u002Fsearch-strategy.md`\n\n## Non-negotiables\n\n- Start every cover letter with `Hi,`\n- Tone: friendly, professional, specific, low-fluff.\n- Never invent project examples, metrics, portfolio URLs, or domain history.\n- Never include email, phone, Telegram, WhatsApp, Calendly, or any off-platform contact detail in a proposal.\n- Never attach the CV in this workflow.\n- Do not parallelize browser actions against the live Upwork session.\n- Stop when available Connects drop below `15`.\n- Skip jobs that are already applied, blocked by hard geography, citizenship, or security constraints, or clearly below the user's floor.\n\n## Setup\n\n1. Run `..\u002F..\u002Fscripts\u002Fbootstrap.sh` once from the plugin root.\n2. Ensure the applicant profile exists. If it does not, run `node ..\u002F..\u002Fscripts\u002Fsetup-applicant-profile.mjs`.\n2. Run `..\u002F..\u002Fscripts\u002Flaunch-controlled-chrome.sh` by default to reuse the user's normal logged-in Chrome profile.\n3. If the user explicitly wants a clean browser state, run `..\u002F..\u002Fscripts\u002Flaunch-isolated-chrome.sh` instead.\n4. Ask the user to log into Upwork only if the chosen browser mode is not already signed in.\n5. Run `node ..\u002F..\u002Fscripts\u002Fupwork-session-probe.mjs` to confirm login state.\n6. Export a log path before submissions, for example:\n\n```bash\nexport UPWORK_AUTOPILOT_LOG=$HOME\u002F.codex\u002Fupwork-autopilot\u002Flogs\u002F$(date +%F).jsonl\n```\n\n## Search and qualification\n\n- List search results:\n\n```bash\nnode ..\u002F..\u002Fscripts\u002Fupwork-search-plan.mjs\n```\n\n- A raw keyword is converted into the default filtered Upwork search URL.\n- A full Upwork search URL is accepted as-is.\n- If `upwork-search-plan.mjs` returns multiple URLs, iterate them sequentially.\n- To open a result and inspect the full job page:\n\n```bash\nnode ..\u002F..\u002Fscripts\u002Fupwork-search-inspect.mjs '\u003Csearch-url-or-keyword>' detail 0\n```\n\n- To probe the apply flow for a specific job:\n\n```bash\nnode ..\u002F..\u002Fscripts\u002Fupwork-apply-probe.mjs '\u003Cjob-url>'\n```\n\nApply only if all of these hold:\n\n- the client is payment verified\n- the role is technically relevant\n- the rate is compatible with the user's floor\n- there is no hard location block\n- the role is not already applied\n- any requested proof, portfolio examples, or niche experience can be answered honestly from the profile or current context\n\n## Proposal writing\n\nCreate a payload JSON file with `apply_patch`. The scripts fill fields in DOM order.\n\n```json\n{\n  \"textareas\": [\n    \"Hi,\\n\\n...\"\n  ],\n  \"inputs\": []\n}\n```\n\nRules:\n\n- Before drafting, extract the actual deliverable, stack, client pain point, any written questions, and any request for examples or proof.\n- First paragraph: open casually and directly, and name the actual problem or fit in plain language within the first 2 sentences.\n- Default structure: 3 to 5 short paragraphs in natural prose, not a bullet-heavy sales pitch.\n- Weave relevant experience into the paragraphs instead of defaulting to bullets.\n- Use bullets only when the client explicitly asks for list-style answers or when multiple written questions are easier to answer that way.\n- Proof section: use relevant project evidence from the profile only when it actually matches the post.\n- When the applicant profile includes named project examples, prefer dropping 1 to 3 of the strongest ones naturally into the prose instead of listing every example.\n- If the applicant profile includes `Differentiators to mention when relevant`, use at most 1 or 2 that genuinely strengthen this specific job. Do not force them into unrelated proposals.\n- Closing: use the profile's `Preferred closing CTA` when present, or a close natural variant of it.\n- If the client asks for project examples, case studies, metrics, URLs, or niche background, answer with the closest truthful match from the profile.\n- If the profile does not contain the proof the client is asking for, stop and ask the user for the missing details before submitting. Do not guess.\n- Keep the proposal usually around `220` to `320` words unless the page asks multiple written questions.\n- Answer written questions directly in field order. Do not dodge them with generic sales copy.\n- Use conversational phrasing and contractions when natural. Avoid templated buzzwords, generic praise, AI-sounding filler, and overly heavy systems language unless the post clearly calls for it.\n- If the applicant profile states tone or structure preferences, follow those over the generic defaults in this file.\n- The first line must begin with `Hi,`\n\n## Submission\n\nRun:\n\n```bash\nnode ..\u002F..\u002Fscripts\u002Fupwork-submit-proposal.mjs '\u003Cproposal-url>' \u002Fabs\u002Fpath\u002Fto\u002Fpayload.json\n```\n\nSuccess is confirmed only when the final URL contains `?success`.\n\nThe submit script:\n\n- fills visible `textarea` fields in order\n- fills visible text, url, email, and number inputs in order\n- clicks `Submit a proposal`\n- extracts the success URL and proposal ID\n- appends a JSONL log entry if `UPWORK_AUTOPILOT_LOG` is set\n\n## Failure handling\n\n- If the page opens a video interview flow, skip unless the user explicitly wants that path.\n- If the apply button is disabled, read the probe output before deciding whether to skip.\n- If the form asks for required information that is missing from the profile, stop and ask the user before submitting.\n- If `net::ERR_ABORTED` appears, another command touched the same Upwork tab. Resume with single-threaded browser actions only.\n- If login, CAPTCHA, or 2FA appears, hand control to the user and resume after confirmation.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fklajdikkolaj\u002Fupwork-autopilot\u002Fskills\u002Fupwork-application-session",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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill upwork-application-session",{"tool":66,"command":67},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill upwork-application-session",{"tool":69,"command":70},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill upwork-application-session","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fklajdikkolaj\u002Fupwork-autopilot\u002Fskills\u002Fupwork-application-session\u002FSKILL.md",true,[],[75,85,93,101,109,117],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":84},"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":84},"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":84},"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":84},"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":84},"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":84},"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",[],[]]