[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M95BPW1NHSE7VBPZE9HCZY":3,"skill-same:01M6M95BPW1NHSE7VBPZE9HCZY":120},{"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":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6M95BPW1NHSE7VBPZE9HCZY","suede-clip-to-guide",null,"Suede AI Clip to Guide Skills. Use when creating short-to-long content and asked to \"turn this clip into a guide funnel\": select a rights-supported moment, score fit, draft the bridge, approval bundle and measurement plan. NOT FOR: rendering (suede-video), social calendars (suede-social), full guide writing (suede-copy), paid ads (suede-ad-creative), or publication without exact-content and identity approval.","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\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-clip-to-guide\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体","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,50,51],"suede clip to guide","guide","clip","Publication","writing","paid","when","for","measurement","rendering","fit","long","full","social","use","bridge","short","select","ads","plan","Video","paid ads","identity","2026-11-10 10:12:30",false,"---\nname: suede-clip-to-guide\ndescription: \"Suede AI Clip to Guide Skills. Use when creating short-to-long content and asked to \\\"turn this clip into a guide funnel\\\": select a rights-supported moment, score fit, draft the bridge, approval bundle and measurement plan. NOT FOR: rendering (suede-video), social calendars (suede-social), full guide writing (suede-copy), paid ads (suede-ad-creative), or publication without exact-content and identity approval.\"\nmetadata:\n  display-name: \"Suede AI Clip to Guide Skills\"\n  version: 1.1.0\n---\n\n# Suede AI Clip to Guide Skills\n\nRead [the worked delivery contract](references\u002Fworked-contract.md) for a concrete\ninput, expected artifact, failure response and validation example.\n\n## Compatibility\n\nRequires source video or timestamped transcript, rights evidence and guide URL\u002Fdraft; Python 3 for the bundled package validator. Browser\u002Faccount access is needed only for authorized platform verification or publication.\n\nBuild one evidence-backed path from a video moment to a deeper written asset.\nTreat the clip as the attention layer and the guide as the authority layer. Do\nnot assume the pattern performs; test the bridge against the account baseline.\n\n## Default Success Blueprint\n\nUse this as the recommended pattern when the rights, source, claim, platform,\nand approval gates pass:\n\n```text\nUseful guide with one promise\n        ↓\nSelf-contained video moment\n        ↓\nRights route + 8\u002F10 moment score\n        ↓\nClip hook + source credit + subtitles\n        ↓\nPost explains why the moment matters\n        ↓\nOne explicit bridge to the guide\n        ↓\nMax Effort\u002FFleet: dual certainty gate\n        ↓\nExact-content approval\n        ↓\nPublic readback + clip-to-guide measurement\n        ↓\nKeep, revise, or stop from the observed result\n```\n\nPrefer this blueprint when:\n\n- a guide already answers the natural next question created by the clip;\n- the goal is deeper understanding, bookmarks, qualified replies, leads, or\n  authority rather than raw views alone;\n- the selected moment passes the 8\u002F10 score and claim-support threshold;\n- the rights route and current platform sequence are recorded;\n- the account can observe at least one clip metric and one guide-transition or\n  campaign metric.\n\nDo not use it when:\n\n- the guide is thin, unrelated, unpublished without a stable draft, or has no\n  specific promise;\n- the clip needs missing context, distorts the source, or exists only because\n  it is popular;\n- third-party reuse is blocked or the accountable fair-use decision is absent;\n- the platform cannot preserve the source, clip, and guide bridge in a verified\n  sequence;\n- the idea is complete in the short post and the guide would add no depth.\n\nFor a first test, build three distinct packages only when three moments pass all\ngates. Compare them with the account's recent comparable posts. Keep the pattern\nonly if the named guide-transition or campaign metric meets the decision rule;\nrevise one variable at a time when it does not.\n\n## Non-Negotiable Gates\n\nApply these throughout the run. Resolve rights, source, and claims before\nwriting copy; resolve platform, certainty, and approval before a live action:\n\n1. **Rights gate**: classify the video as owned, licensed, permission-recorded,\n   native-repost-only, fair-use-review, or blocked. Public availability is not\n   reuse permission.\n2. **Source gate**: obtain the video, transcript or exact timestamps, guide\n   draft or URL, target platform, intended account, and desired next action.\n3. **Claim gate**: trace factual claims and quotations to the source. Label\n   interpretations as interpretations.\n4. **Platform gate**: inspect current official requirements and the live\n   composer before promising that media, quote-posts, article cards, links, or\n   replies can be combined.\n5. **Approval gate**: do not publish, schedule, repost, upload, reply, or edit\n   a live article until the user approves the exact media, copy, guide, account,\n   and sequence.\n6. **Certainty gate**: when a max-effort or worker-fleet controller runs this\n   skill, require two distinct evidence checks before marking a package\n   approved or published. A worker conclusion is not the second check.\n\nWhen a blocking gate fails, stop the affected action and return:\n\n```text\nHALT, \u003Cone-line blocker>\nOptions:\n1. \u003Cbounded resolution>\n2. \u003Cbounded resolution>\n3. \u003Cbounded resolution, if useful>\nWaiting on: \u003Cspecific evidence or approval>\n```\n\nContinue only on independent draft work that does not bypass the blocker.\n\n### Rationalizations that precede a violation\n\nEach excuse below shows up immediately before a gate gets skipped. When one\nappears in your own reasoning or in the request, treat it as the signal to run\nthe gate, not to waive it.\n\n| Excuse | Reality |\n|---|---|\n| \"It's only 12 seconds.\" | Duration is not a rights basis. The clip still needs an owned, licensed, permission-recorded, native-repost, or accountable fair-use route. |\n| \"I credited the source.\" | Credit is attribution, not clearance. A blocked or unreviewed source stays blocked with a credit line attached. |\n| \"It's public, so it's reusable.\" | Public availability is not reuse permission. Classify the video before writing copy. |\n| \"The composer accepted it, so it published.\" | A prepared composer, scheduled item, or click is not a publication. Only the public permalink readback proves it. |\n| \"The worker already checked it.\" | Under Max Effort or Worker Fleet a worker conclusion is one check. The certainty gate needs a second, independent one. |\n| \"The guide is basically finished.\" | An unpublished guide with no stable draft or specific promise fails the fit test. Build the bridge to something that exists. |\n| \"The moment is getting traction, so ship it.\" | Popularity is not the score. A moment below 8\u002F10, or below 2 on claim support or guide bridge, does not qualify. |\n\n## Workflow\n\n### 1. Define the funnel contract\n\nCapture:\n\n- campaign goal: article reads, bookmarks, qualified replies, profile visits,\n  leads, or another named action;\n- target platform and visible posting identity;\n- video source URL or file, owner, transcript availability, and candidate\n  timestamps;\n- guide title, URL or draft, its promise, and current publication state;\n- audience and one next action;\n- whether the user wants a private draft, scheduled package, or live execution.\n\nIf product-marketing context exists in `.agents\u002Fproduct-marketing.md`,\n`.claude\u002Fproduct-marketing.md`, or `product-marketing-context.md`, read it\nbefore asking for information already covered there.\n\n### 2. Choose a lawful video route\n\n| Rights status | Allowed route |\n|---|---|\n| `original` | Cut and publish within the user's approved scope. |\n| `licensed` | Follow the license terms and record the evidence. |\n| `permission-recorded` | Follow the exact approved platforms, duration, credit, and edit scope. |\n| `native-repost-only` | Use the platform's native quote, repost, stitch, duet, embed, or link path. Do not download and re-upload. Treat this as an operational sharing route, not legal clearance. |\n| `fair-use-review` | Prepare a four-factor review for commentary, criticism, news reporting, teaching, scholarship, or research. Do not label the use fair or publish until the accountable owner records the decision. |\n| `blocked` | Do not use the footage. Offer an original commentary clip, a permission request, or a source link instead. |\n\nFor any source that is not original, licensed, or permission-recorded, read\n[references\u002Fthird-party-video-rights.md](references\u002Fthird-party-video-rights.md).\nDo not infer fair use, ownership, or permission. Shortness, credit, a public\nsource, or added commentary alone does not settle fair use. Do not remove\nwatermarks, attribution, or provenance. Prefer a native repost with added\nanalysis or create an original camera or screen-recorded response that\nsummarizes the idea without copying the footage.\n\n### 3. Establish the guide anchor\n\nThe long-form asset must have:\n\n- one specific promise that the clip can honestly introduce;\n- a title and stable draft or URL;\n- enough depth to reward the transition from short to long;\n- sources for material factual claims;\n- one next action that matches the campaign goal.\n\n**Make the guide findable, not only clickable.** Platform-hosted articles (X\nArticles, LinkedIn articles) borrow the platform's audience; an owned guide on\nthe brand's domain is the asset that ranks and gets cited in AI answers after\nthe post stops circulating. When the guide is owned, check that it:\n\n- opens with a two- or three-sentence direct answer to the question the clip\n  raises, under a heading phrased as that question;\n- embeds the clip (or the original source, when reuse is native-only) with a\n  text transcript or a timestamped summary on the page;\n- carries `Article` JSON-LD, plus `VideoObject` with name, description,\n  thumbnailUrl, uploadDate, and duration when the video is hosted or embedded\n  on the page, validated before publish;\n- has a named author with a short bio, and links each factual claim to its\n  primary source.\n\nWhen the guide lives only on a platform, say so in the decision snapshot and\nrecommend an owned canonical copy. Route schema and indexing checks to\n`suede-seo-audit` and AI answer visibility to `suede-ai-seo`.\n\nIf the guide does not exist, return a brief and route the full draft to\n`suede-copy` and the portfolio decision to `suede-content-strategy`. Resume this\nskill after the guide has a reviewable draft. Do not fabricate a live URL.\n\n### 4. Score candidate moments\n\nScore each candidate from 0 to 2 on five dimensions:\n\n| Dimension | 0 | 1 | 2 |\n|---|---|---|---|\n| Opening clarity | Premise is missing | Premise arrives late | Premise is clear in 1–3 seconds |\n| Standalone value | Needs surrounding context | Partly self-contained | Complete useful idea or story |\n| Guide bridge | Unrelated | Adjacent | Naturally creates the next question the guide answers |\n| Claim support | Unverifiable or misleading | Needs qualification | Directly supported and correctly framed |\n| Audience fit | No named audience fit | Broad fit | Solves a named audience problem |\n\nSelect a moment only when it scores at least 8\u002F10, claim support is 2, guide\nbridge is 2, and the rights gate passes. If none qualify, return the scorecard\nand request a better source instead of forcing a clip.\n\n### 5. Build the package\n\nRead [references\u002Fpackage-template.md](references\u002Fpackage-template.md) and\nproduce:\n\n1. **Decision snapshot**: goal, audience, platform, identity, and chosen\n   sequence.\n2. **Source and rights record**: owner, source, evidence, transcript excerpt,\n   permitted route, jurisdiction, and any four-factor review.\n3. **Guide anchor**: exact title, promise, URL or draft state, and the question\n   it answers after the clip.\n4. **Clip brief**: in\u002Fout timestamps, target duration, exact opening, subtitle\n   text, on-screen credit, ending bridge, and export owner.\n5. **Funnel post**: exact text with four jobs:\n   - hook the video moment;\n   - explain why it matters;\n   - bridge to the deeper guide;\n   - give one specific next action.\n6. **Publish sequence**: one of the verified patterns below.\n7. **Measurement plan**: baseline, observation window, and decision rule.\n8. **Certainty record**: execution mode, two check owners or processes,\n   direct evidence, contradictions, and final verdict.\n9. **Approval bundle**: exact media, post copy, guide, identity, and sequence.\n\nDo not pad the post with generic setup, unsupported performance language, or\nmultiple competing calls to action.\n\n### 6. Choose a verified sequence\n\nUse one:\n\n- **Anchor-first**: publish or verify the guide, then publish the clip-led post\n  that references it.\n- **Clip-first**: publish the clip, then place the guide in the platform's\n  verified companion location, such as a first reply or supported link field.\n- **Native-repost**: quote or repost the third-party source with original\n  analysis and a guide bridge; do not re-upload the source media.\n- **X native video plus owned Article card**: when the account owns an X\n  Article and has a lawful basis to use the video as native media, publish a\n  fresh post from the approved account with the exact approved copy, attach\n  the video, and put the owned Article's status URL at the end so X renders the\n  Article as the quoted card. Do not quote, repost, or inherit the third\n  party's post, caption, replies, or engagement context; preserve source credit\n  on the video. If the Quote composer accepts the video but leaves publishing\n  disabled, use this fresh-post construction or report the blocker. Never\n  substitute a quote of the third party's post. After publishing, confirm the\n  live post shows both the native video and the Article card.\n\nDo not assume a quote-post can also carry new media. Verify the current composer\nand choose the smallest sequence that preserves the clip, guide, and source\ncredit.\n\n### 7. Run the dual certainty gate when required\n\nRecord `execution_mode` as `standard`, `max-effort`, or `worker-fleet`. Standard\nmode may record `certainty_status: not-required`. Max Effort and Worker Fleet\nmust run both checks and may not mark a package `approved` or `published` until\n`certainty_status: proved`. Record one package version, timestamp, or content\nhash so both checks evaluate the same unchanged artifact.\n\n**Check 1: production proof**\n\n- Reopen the video or transcript at the selected timestamps.\n- Match the quotation, claim framing, rights evidence, moment score, guide\n  promise, bridge, exact copy, identity, sequence, and one CTA to the package.\n- Run the package validator for a saved artifact.\n- In Fleet mode, the fleet worker's acceptance-criteria self-check may satisfy\n  this check, but remains provisional.\n\n**Check 2: independent proof**\n\n- Inspect the source evidence and assembled package directly; do not review\n  only Check 1's summary.\n- Use a different failure lens, evidence source, or acceptance criterion and\n  try to disprove the rights route, factual framing, guide fit, platform\n  sequence, and approval readiness.\n- In Max Effort with useful parallel work, keep the producer and adversarial\n  reviewer separate. For one atomic Max Effort job, perform a fresh second pass\n  after reloading the source evidence.\n- In Fleet mode, the controller must perform this check and mark the worker\n  output `accepted`, `rejected`, or `fix brief`. A second worker or repeated\n  self-check does not replace controller review.\n\nUse only:\n\n- `PROVED`: both checks pass with direct evidence and every contradiction is\n  resolved;\n- `UNPROVED`: a check is incomplete, indirect, or disagrees with the other;\n- `BLOCKED`: access, authority, rights, or platform state prevents a required\n  check.\n\nIf either check is not `PROVED`, keep publication unapproved, use the halt\nformat, and name the smallest fix or evidence needed. The dual check raises\nconfidence; it does not guarantee truth, create legal clearance, or replace\nthe live readback. A material change to the media, timestamps, rights evidence,\nguide, copy, identity, sequence, or CTA resets `certainty_status` to `pending`\nand requires both checks again.\n\n### 8. Require exact-content approval\n\nBefore a live action, show:\n\n```text\nAccount:\nPlatform:\nMedia:\nSource\u002Frights status:\nGuide title and URL:\nExact post text:\nPublish sequence:\n```\n\nApproval is valid only for that bundle. If the media, copy, guide URL, account,\nor sequence changes materially, show the changed bundle and obtain approval\nagain. Verify the visible identity immediately before acting and fail closed on\nan account mismatch, login challenge, or ambiguous composer.\n\n### 9. Verify completion\n\nFor a saved package, run:\n\n```bash\npython3 \u002Fpath\u002Fto\u002Fsuede-clip-to-guide\u002Fscripts\u002Fvalidate_package.py path\u002Fto\u002Fclip-to-guide-package.md\n```\n\nFor a live run, also read back:\n\n- the final public permalink;\n- visible posting identity;\n- rendered post text and media or native source reference;\n- guide URL and publication state;\n- timestamp and any platform warning.\n\nDo not claim publication from a click alone. A complete live run needs the\npublic readback. A draft-only run is complete when the package validator passes\nand the approval state is reported as `draft`.\n\n## Measurement\n\nChoose the smallest comparable window the account can support. Record:\n\n- clip retention or completion where exposed;\n- guide opens or link clicks where exposed;\n- bookmarks, saves, qualified replies, and profile visits;\n- the exact campaign action;\n- a comparable recent baseline.\n\nWhen the platform exposes compatible denominators, calculate:\n\n```text\nguide transition rate = verified guide opens \u002F clip-post impressions\nqualified action rate = named qualified actions \u002F verified guide opens\n```\n\nIf compatible denominators are unavailable, report the available counts\nseparately. Do not combine mismatched platform windows or call clicks article\nreads.\n\nChange one variable per next test: moment, opening, bridge, sequence, or CTA.\nDo not report causal lift from an unpaired or tiny sample.\n\n## Boundaries\n\n- Do not download, clip, or re-upload third-party footage without a recorded\n  rights basis or an accountable fair-use decision.\n- Do not give legal clearance or label uncertain reuse as fair use.\n- Do not invent transcripts, timestamps, permissions, URLs, performance,\n  audience demand, or platform capabilities.\n- Do not publish or schedule without exact-content approval and visible-identity\n  verification.\n- Do not alter a source quote to make the hook stronger.\n- Do not describe the campaign as successful until current analytics support\n  the named decision rule.\n- Do not call a Max Effort or Fleet package certain, approved, or publishable\n  when either required check is `UNPROVED` or `BLOCKED`.\n\n## Routing\n\n- Need full video editing, generation, captions, color, or exports -> use\n  `suede-video`, then return here for the funnel package.\n- Need a general platform plan, calendar, account audit, listening, or\n  engagement program -> use `suede-social`.\n- Need the long-form guide written -> use `suede-copy`; use\n  `suede-content-strategy` for pillars and portfolio priority.\n- Need paid variants -> use `suede-ad-creative`.\n- Running many packages through parallel agents (for example an Agent Studio\n  fleet) -> record `execution_mode: worker-fleet` and keep the controller's\n  independent Check 2 here; the certainty record stays in this skill.\n- From those skills, route a video-to-long-form bridge, moment score, rights\n  route, exact approval bundle, and readback back to `suede-clip-to-guide`.\n","# Suede AI Clip to Guide Skills\n\nRead [the worked delivery contract](references\u002Fworked-contract.md) for a concrete\ninput, expected artifact, failure response and validation example.\n\n## Compatibility\n\nRequires source video or timestamped transcript, rights evidence and guide URL\u002Fdraft; Python 3 for the bundled package validator. Browser\u002Faccount access is needed only for authorized platform verification or publication.\n\nBuild one evidence-backed path from a video moment to a deeper written asset.\nTreat the clip as the attention layer and the guide as the authority layer. Do\nnot assume the pattern performs; test the bridge against the account baseline.\n\n## Default Success Blueprint\n\nUse this as the recommended pattern when the rights, source, claim, platform,\nand approval gates pass:\n\n```text\nUseful guide with one promise\n        ↓\nSelf-contained video moment\n        ↓\nRights route + 8\u002F10 moment score\n        ↓\nClip hook + source credit + subtitles\n        ↓\nPost explains why the moment matters\n        ↓\nOne explicit bridge to the guide\n        ↓\nMax Effort\u002FFleet: dual certainty gate\n        ↓\nExact-content approval\n        ↓\nPublic readback + clip-to-guide measurement\n        ↓\nKeep, revise, or stop from the observed result\n```\n\nPrefer this blueprint when:\n\n- a guide already answers the natural next question created by the clip;\n- the goal is deeper understanding, bookmarks, qualified replies, leads, or\n  authority rather than raw views alone;\n- the selected moment passes the 8\u002F10 score and claim-support threshold;\n- the rights route and current platform sequence are recorded;\n- the account can observe at least one clip metric and one guide-transition or\n  campaign metric.\n\nDo not use it when:\n\n- the guide is thin, unrelated, unpublished without a stable draft, or has no\n  specific promise;\n- the clip needs missing context, distorts the source, or exists only because\n  it is popular;\n- third-party reuse is blocked or the accountable fair-use decision is absent;\n- the platform cannot preserve the source, clip, and guide bridge in a verified\n  sequence;\n- the idea is complete in the short post and the guide would add no depth.\n\nFor a first test, build three distinct packages only when three moments pass all\ngates. Compare them with the account's recent comparable posts. Keep the pattern\nonly if the named guide-transition or campaign metric meets the decision rule;\nrevise one variable at a time when it does not.\n\n## Non-Negotiable Gates\n\nApply these throughout the run. Resolve rights, source, and claims before\nwriting copy; resolve platform, certainty, and approval before a live action:\n\n1. **Rights gate**: classify the video as owned, licensed, permission-recorded,\n   native-repost-only, fair-use-review, or blocked. Public availability is not\n   reuse permission.\n2. **Source gate**: obtain the video, transcript or exact timestamps, guide\n   draft or URL, target platform, intended account, and desired next action.\n3. **Claim gate**: trace factual claims and quotations to the source. Label\n   interpretations as interpretations.\n4. **Platform gate**: inspect current official requirements and the live\n   composer before promising that media, quote-posts, article cards, links, or\n   replies can be combined.\n5. **Approval gate**: do not publish, schedule, repost, upload, reply, or edit\n   a live article until the user approves the exact media, copy, guide, account,\n   and sequence.\n6. **Certainty gate**: when a max-effort or worker-fleet controller runs this\n   skill, require two distinct evidence checks before marking a package\n   approved or published. A worker conclusion is not the second check.\n\nWhen a blocking gate fails, stop the affected action and return:\n\n```text\nHALT, \u003Cone-line blocker>\nOptions:\n1. \u003Cbounded resolution>\n2. \u003Cbounded resolution>\n3. \u003Cbounded resolution, if useful>\nWaiting on: \u003Cspecific evidence or approval>\n```\n\nContinue only on independent draft work that does not bypass the blocker.\n\n### Rationalizations that precede a violation\n\nEach excuse below shows up immediately before a gate gets skipped. When one\nappears in your own reasoning or in the request, treat it as the signal to run\nthe gate, not to waive it.\n\n| Excuse | Reality |\n|---|---|\n| \"It's only 12 seconds.\" | Duration is not a rights basis. The clip still needs an owned, licensed, permission-recorded, native-repost, or accountable fair-use route. |\n| \"I credited the source.\" | Credit is attribution, not clearance. A blocked or unreviewed source stays blocked with a credit line attached. |\n| \"It's public, so it's reusable.\" | Public availability is not reuse permission. Classify the video before writing copy. |\n| \"The composer accepted it, so it published.\" | A prepared composer, scheduled item, or click is not a publication. Only the public permalink readback proves it. |\n| \"The worker already checked it.\" | Under Max Effort or Worker Fleet a worker conclusion is one check. The certainty gate needs a second, independent one. |\n| \"The guide is basically finished.\" | An unpublished guide with no stable draft or specific promise fails the fit test. Build the bridge to something that exists. |\n| \"The moment is getting traction, so ship it.\" | Popularity is not the score. A moment below 8\u002F10, or below 2 on claim support or guide bridge, does not qualify. |\n\n## Workflow\n\n### 1. Define the funnel contract\n\nCapture:\n\n- campaign goal: article reads, bookmarks, qualified replies, profile visits,\n  leads, or another named action;\n- target platform and visible posting identity;\n- video source URL or file, owner, transcript availability, and candidate\n  timestamps;\n- guide title, URL or draft, its promise, and current publication state;\n- audience and one next action;\n- whether the user wants a private draft, scheduled package, or live execution.\n\nIf product-marketing context exists in `.agents\u002Fproduct-marketing.md`,\n`.claude\u002Fproduct-marketing.md`, or `product-marketing-context.md`, read it\nbefore asking for information already covered there.\n\n### 2. Choose a lawful video route\n\n| Rights status | Allowed route |\n|---|---|\n| `original` | Cut and publish within the user's approved scope. |\n| `licensed` | Follow the license terms and record the evidence. |\n| `permission-recorded` | Follow the exact approved platforms, duration, credit, and edit scope. |\n| `native-repost-only` | Use the platform's native quote, repost, stitch, duet, embed, or link path. Do not download and re-upload. Treat this as an operational sharing route, not legal clearance. |\n| `fair-use-review` | Prepare a four-factor review for commentary, criticism, news reporting, teaching, scholarship, or research. Do not label the use fair or publish until the accountable owner records the decision. |\n| `blocked` | Do not use the footage. Offer an original commentary clip, a permission request, or a source link instead. |\n\nFor any source that is not original, licensed, or permission-recorded, read\n[references\u002Fthird-party-video-rights.md](references\u002Fthird-party-video-rights.md).\nDo not infer fair use, ownership, or permission. Shortness, credit, a public\nsource, or added commentary alone does not settle fair use. Do not remove\nwatermarks, attribution, or provenance. Prefer a native repost with added\nanalysis or create an original camera or screen-recorded response that\nsummarizes the idea without copying the footage.\n\n### 3. Establish the guide anchor\n\nThe long-form asset must have:\n\n- one specific promise that the clip can honestly introduce;\n- a title and stable draft or URL;\n- enough depth to reward the transition from short to long;\n- sources for material factual claims;\n- one next action that matches the campaign goal.\n\n**Make the guide findable, not only clickable.** Platform-hosted articles (X\nArticles, LinkedIn articles) borrow the platform's audience; an owned guide on\nthe brand's domain is the asset that ranks and gets cited in AI answers after\nthe post stops circulating. When the guide is owned, check that it:\n\n- opens with a two- or three-sentence direct answer to the question the clip\n  raises, under a heading phrased as that question;\n- embeds the clip (or the original source, when reuse is native-only) with a\n  text transcript or a timestamped summary on the page;\n- carries `Article` JSON-LD, plus `VideoObject` with name, description,\n  thumbnailUrl, uploadDate, and duration when the video is hosted or embedded\n  on the page, validated before publish;\n- has a named author with a short bio, and links each factual claim to its\n  primary source.\n\nWhen the guide lives only on a platform, say so in the decision snapshot and\nrecommend an owned canonical copy. Route schema and indexing checks to\n`suede-seo-audit` and AI answer visibility to `suede-ai-seo`.\n\nIf the guide does not exist, return a brief and route the full draft to\n`suede-copy` and the portfolio decision to `suede-content-strategy`. Resume this\nskill after the guide has a reviewable draft. Do not fabricate a live URL.\n\n### 4. Score candidate moments\n\nScore each candidate from 0 to 2 on five dimensions:\n\n| Dimension | 0 | 1 | 2 |\n|---|---|---|---|\n| Opening clarity | Premise is missing | Premise arrives late | Premise is clear in 1–3 seconds |\n| Standalone value | Needs surrounding context | Partly self-contained | Complete useful idea or story |\n| Guide bridge | Unrelated | Adjacent | Naturally creates the next question the guide answers |\n| Claim support | Unverifiable or misleading | Needs qualification | Directly supported and correctly framed |\n| Audience fit | No named audience fit | Broad fit | Solves a named audience problem |\n\nSelect a moment only when it scores at least 8\u002F10, claim support is 2, guide\nbridge is 2, and the rights gate passes. If none qualify, return the scorecard\nand request a better source instead of forcing a clip.\n\n### 5. Build the package\n\nRead [references\u002Fpackage-template.md](references\u002Fpackage-template.md) and\nproduce:\n\n1. **Decision snapshot**: goal, audience, platform, identity, and chosen\n   sequence.\n2. **Source and rights record**: owner, source, evidence, transcript excerpt,\n   permitted route, jurisdiction, and any four-factor review.\n3. **Guide anchor**: exact title, promise, URL or draft state, and the question\n   it answers after the clip.\n4. **Clip brief**: in\u002Fout timestamps, target duration, exact opening, subtitle\n   text, on-screen credit, ending bridge, and export owner.\n5. **Funnel post**: exact text with four jobs:\n   - hook the video moment;\n   - explain why it matters;\n   - bridge to the deeper guide;\n   - give one specific next action.\n6. **Publish sequence**: one of the verified patterns below.\n7. **Measurement plan**: baseline, observation window, and decision rule.\n8. **Certainty record**: execution mode, two check owners or processes,\n   direct evidence, contradictions, and final verdict.\n9. **Approval bundle**: exact media, post copy, guide, identity, and sequence.\n\nDo not pad the post with generic setup, unsupported performance language, or\nmultiple competing calls to action.\n\n### 6. Choose a verified sequence\n\nUse one:\n\n- **Anchor-first**: publish or verify the guide, then publish the clip-led post\n  that references it.\n- **Clip-first**: publish the clip, then place the guide in the platform's\n  verified companion location, such as a first reply or supported link field.\n- **Native-repost**: quote or repost the third-party source with original\n  analysis and a guide bridge; do not re-upload the source media.\n- **X native video plus owned Article card**: when the account owns an X\n  Article and has a lawful basis to use the video as native media, publish a\n  fresh post from the approved account with the exact approved copy, attach\n  the video, and put the owned Article's status URL at the end so X renders the\n  Article as the quoted card. Do not quote, repost, or inherit the third\n  party's post, caption, replies, or engagement context; preserve source credit\n  on the video. If the Quote composer accepts the video but leaves publishing\n  disabled, use this fresh-post construction or report the blocker. Never\n  substitute a quote of the third party's post. After publishing, confirm the\n  live post shows both the native video and the Article card.\n\nDo not assume a quote-post can also carry new media. Verify the current composer\nand choose the smallest sequence that preserves the clip, guide, and source\ncredit.\n\n### 7. Run the dual certainty gate when required\n\nRecord `execution_mode` as `standard`, `max-effort`, or `worker-fleet`. Standard\nmode may record `certainty_status: not-required`. Max Effort and Worker Fleet\nmust run both checks and may not mark a package `approved` or `published` until\n`certainty_status: proved`. Record one package version, timestamp, or content\nhash so both checks evaluate the same unchanged artifact.\n\n**Check 1: production proof**\n\n- Reopen the video or transcript at the selected timestamps.\n- Match the quotation, claim framing, rights evidence, moment score, guide\n  promise, bridge, exact copy, identity, sequence, and one CTA to the package.\n- Run the package validator for a saved artifact.\n- In Fleet mode, the fleet worker's acceptance-criteria self-check may satisfy\n  this check, but remains provisional.\n\n**Check 2: independent proof**\n\n- Inspect the source evidence and assembled package directly; do not review\n  only Check 1's summary.\n- Use a different failure lens, evidence source, or acceptance criterion and\n  try to disprove the rights route, factual framing, guide fit, platform\n  sequence, and approval readiness.\n- In Max Effort with useful parallel work, keep the producer and adversarial\n  reviewer separate. For one atomic Max Effort job, perform a fresh second pass\n  after reloading the source evidence.\n- In Fleet mode, the controller must perform this check and mark the worker\n  output `accepted`, `rejected`, or `fix brief`. A second worker or repeated\n  self-check does not replace controller review.\n\nUse only:\n\n- `PROVED`: both checks pass with direct evidence and every contradiction is\n  resolved;\n- `UNPROVED`: a check is incomplete, indirect, or disagrees with the other;\n- `BLOCKED`: access, authority, rights, or platform state prevents a required\n  check.\n\nIf either check is not `PROVED`, keep publication unapproved, use the halt\nformat, and name the smallest fix or evidence needed. The dual check raises\nconfidence; it does not guarantee truth, create legal clearance, or replace\nthe live readback. A material change to the media, timestamps, rights evidence,\nguide, copy, identity, sequence, or CTA resets `certainty_status` to `pending`\nand requires both checks again.\n\n### 8. Require exact-content approval\n\nBefore a live action, show:\n\n```text\nAccount:\nPlatform:\nMedia:\nSource\u002Frights status:\nGuide title and URL:\nExact post text:\nPublish sequence:\n```\n\nApproval is valid only for that bundle. If the media, copy, guide URL, account,\nor sequence changes materially, show the changed bundle and obtain approval\nagain. Verify the visible identity immediately before acting and fail closed on\nan account mismatch, login challenge, or ambiguous composer.\n\n### 9. Verify completion\n\nFor a saved package, run:\n\n```bash\npython3 \u002Fpath\u002Fto\u002Fsuede-clip-to-guide\u002Fscripts\u002Fvalidate_package.py path\u002Fto\u002Fclip-to-guide-package.md\n```\n\nFor a live run, also read back:\n\n- the final public permalink;\n- visible posting identity;\n- rendered post text and media or native source reference;\n- guide URL and publication state;\n- timestamp and any platform warning.\n\nDo not claim publication from a click alone. A complete live run needs the\npublic readback. A draft-only run is complete when the package validator passes\nand the approval state is reported as `draft`.\n\n## Measurement\n\nChoose the smallest comparable window the account can support. Record:\n\n- clip retention or completion where exposed;\n- guide opens or link clicks where exposed;\n- bookmarks, saves, qualified replies, and profile visits;\n- the exact campaign action;\n- a comparable recent baseline.\n\nWhen the platform exposes compatible denominators, calculate:\n\n```text\nguide transition rate = verified guide opens \u002F clip-post impressions\nqualified action rate = named qualified actions \u002F verified guide opens\n```\n\nIf compatible denominators are unavailable, report the available counts\nseparately. Do not combine mismatched platform windows or call clicks article\nreads.\n\nChange one variable per next test: moment, opening, bridge, sequence, or CTA.\nDo not report causal lift from an unpaired or tiny sample.\n\n## Boundaries\n\n- Do not download, clip, or re-upload third-party footage without a recorded\n  rights basis or an accountable fair-use decision.\n- Do not give legal clearance or label uncertain reuse as fair use.\n- Do not invent transcripts, timestamps, permissions, URLs, performance,\n  audience demand, or platform capabilities.\n- Do not publish or schedule without exact-content approval and visible-identity\n  verification.\n- Do not alter a source quote to make the hook stronger.\n- Do not describe the campaign as successful until current analytics support\n  the named decision rule.\n- Do not call a Max Effort or Fleet package certain, approved, or publishable\n  when either required check is `UNPROVED` or `BLOCKED`.\n\n## Routing\n\n- Need full video editing, generation, captions, color, or exports -> use\n  `suede-video`, then return here for the funnel package.\n- Need a general platform plan, calendar, account audit, listening, or\n  engagement program -> use `suede-social`.\n- Need the long-form guide written -> use `suede-copy`; use\n  `suede-content-strategy` for pillars and portfolio priority.\n- Need paid variants -> use `suede-ad-creative`.\n- Running many packages through parallel agents (for example an Agent Studio\n  fleet) -> record `execution_mode: worker-fleet` and keep the controller's\n  independent Check 2 here; the certainty record stays in this skill.\n- From those skills, route a video-to-long-form bridge, moment score, rights\n  route, exact approval bundle, and readback back to `suede-clip-to-guide`.\n",{"name":5,"metadata":57,"description":7},{"version":58,"display-name":59},"1.1.0","Suede AI Clip to Guide Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-clip-to-guide",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":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-clip-to-guide",{"tool":76,"command":77},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-clip-to-guide",{"tool":79,"command":80},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-clip-to-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-clip-to-guide\u002FSKILL.md",true,[84,90,94,98,102,106,110,114],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"agents\u002Fopenai.yaml","REFERENCE","参考文档",420,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-clip-to-guide\u002Fagents\u002Fopenai.yaml",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"CARD.md",4632,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-clip-to-guide\u002FCARD.md",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",8899,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-clip-to-guide\u002Fevals\u002Fevals.json",{"path":99,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fexample-package.md",4439,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-clip-to-guide\u002Freferences\u002Fexample-package.md",{"path":103,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fpackage-template.md",3053,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-clip-to-guide\u002Freferences\u002Fpackage-template.md",{"path":107,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fthird-party-video-rights.md",3106,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-clip-to-guide\u002Freferences\u002Fthird-party-video-rights.md",{"path":111,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fworked-contract.md",2050,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-clip-to-guide\u002Freferences\u002Fworked-contract.md",{"path":115,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Fvalidate_package.py","SCRIPT","脚本",8518,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-clip-to-guide\u002Fscripts\u002Fvalidate_package.py",[121,131,139,147,155,163],{"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":125,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":130},"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":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":130},"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":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":130},"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":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":151,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":130},"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":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":159,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":130},"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":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":130},"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",[],[]]