[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M9EJN5QSDTP7S03T3DT146":3,"skill-same:01M6M9EJN5QSDTP7S03T3DT146":89},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6M9EJN5QSDTP7S03T3DT146","suede-sync-packaging",null,"Prepare a song for sync review: scene fit, supervisor one-sheet, asset checklist, lyric flags, mood tags, AI disclosure, and open clearance questions. Use when asked to \"make a sync one-sheet\" or package a track for film, TV, ads, games, trailers, or creator campaigns. Drafts pitch materials with open clearance questions labeled. NOT FOR: rights investigations or transfer packages (use suede-rights-passport), folder linting (use suede-release-linter), or rollouts (use suede-campaign-in-a-box).","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-sync-packaging\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"sync","suede sync packaging","packaging","when","review","track","lyric","song","drafts","make","asset","linting","pitch","flags","rollouts","campaign","linter","ads","open","release","packages","2026-11-10 10:12:30",false,"---\nname: suede-sync-packaging\ndescription: \"Prepare a song for sync review: scene fit, supervisor one-sheet, asset checklist, lyric flags, mood tags, AI disclosure, and open clearance questions. Use when asked to \\\"make a sync one-sheet\\\" or package a track for film, TV, ads, games, trailers, or creator campaigns. Drafts pitch materials with open clearance questions labeled. NOT FOR: rights investigations or transfer packages (use suede-rights-passport), folder linting (use suede-release-linter), or rollouts (use suede-campaign-in-a-box).\"\nmetadata:\n  display-name: \"Suede AI Sync Packaging Skills\"\n---\n\n# Suede AI Sync Packaging Skills\n\n## Compatibility\n\nUses supplied track facts, lyrics, rights evidence, and a confirmed master path. Media inspection needs an available local viewer or supplied timecodes; no distributor or outreach integration is required.\n\nFor a concrete input, expected handoff, and failure check, read\n[the worked handoff](references\u002Fworked-handoff.md).\n\n## Gate policy\n\nEvery check and verdict here is advice to the user, not a control on the agent.\nRun the checks, report results honestly, and complete what the user asked. A\nfailed gate changes the report, never the work. The one exception: a finding\nthat risks data loss, credential exposure, a legal or rights violation, a\npayment mistake, or irreversible public damage. Pause, name the risk, give the\noptions, and let the user choose.\n\n**Core principle:** a sync package makes a track easy to evaluate; it never\nasserts the track is cleared. Confirmed facts and open clearance questions\ntravel in separate, labeled piles, every time.\n\n## Input contract\n\nProvide at minimum:\n\n- **Track**: title, artist, featuring credits if any\n- **Target world**: film \u002F TV \u002F ads \u002F games \u002F trailers \u002F creator campaigns \u002F brand brief (or \"general sync\")\n- **Available assets**: which of master, instrumental, clean, stems, lyrics, credits, splits currently exist\n- **Rights status**: what is confirmed vs. unknown (sample clearance, ownership splits, publishing assignment, one-stop or not)\n- **AI involvement**: none, or which elements used generative AI (vocals, instrumentation, composition, lyrics, post-production)\n\nOptional but useful: reference sync placements the artist admires, mood or\nscene keywords, existing pitches or supervisor feedback.\n\nIf no rights status is provided, treat every clearance question as open. If AI\ninvolvement is not stated, it is an open clearance question too.\n\nRead `references\u002Fsync-norms.md` for deliverable specs, one-stop, and why AI\ninvolvement now sits in the clearance pile.\n\n## Hard gates\n\nDo not rationalize past these:\n\n1. **Never claim or imply clearance.** A rights fact appears as confirmed only\n   when the user supplies the confirmation (signed split sheet, executed\n   license, rights-holder statement). Anything else stays OPEN or UNKNOWN. You\n   organize the questions; you never answer them.\n2. **Never resolve a rights question yourself.** If ownership, splits, samples,\n   or publishing are unclear, mark the item UNKNOWN. Do not infer, average, or\n   assume. Route the gap to suede-rights-passport (audit mode).\n3. **Asset checklist before pitch copy.** Do not write one-sheet or pitch-email\n   copy until the instrumental\u002Fclean asset checklist is filled in: every\n   version marked exists \u002F missing \u002F unknown, with at minimum a confirmed\n   master file path. Missing instrumental or clean versions are flagged in the\n   one-sheet, not glossed.\n4. **Unresolved sample = pause and put it to the user.** Uncleared samples are\n   a legal-risk finding: mark sample status \"OPEN: recommend not pitching\n   until cleared,\" tell the user exactly what is unresolved, and let them\n   decide whether pitch copy is still drafted. If they proceed, the OPEN flag\n   stays embedded in the one-sheet and pitch materials.\n5. **Lyric flags are mandatory.** Screen the lyrics and flag profanity, brand\n   and product names, artist name-drops, violence, drugs and alcohol, sexual\n   content, religious and political content, and date-stamped references. If\n   no lyrics are supplied, write \"Lyric flags: not screened, lyrics not\n   provided.\" A lyric surprise in review kills the placement.\n6. **Sync fit is an assessment, not a compliment.** \"No clear scene fit for the\n   stated target world\" is a valid, useful finding: say it plainly and say why.\n   Never pad the scene-fit list to reach three; two real fits beat three, and\n   one real fit beats two. Never call a track a placement candidate when the\n   asset checklist or the clearance questions say it cannot be pitched yet. The\n   supervisor will find the weak angle faster than the artist will.\n\n## Package workflow\n\n1. Identify the track, artist, genre, mood, tempo, lyric themes, versions,\n   existing assets, and target sync world.\n2. Build the sync angle: scene fit; emotional use; trailer or montage fit;\n   brand fit; game or sports fit; creator campaign fit: assessed, not flattered\n   (hard gate 6).\n3. Fill the asset checklist: master file; instrumental; clean version; stems\n   if available; lyrics; credits; splits; sample status; contact path;\n   public\u002Fprivate links. Each item: exists \u002F missing \u002F unknown.\n4. Screen lyrics and write the lyric flags (hard gate 5).\n5. Separate confirmed rights facts from open clearance questions (hard gates\n   1-2).\n6. Write the one-sheet and pitch email only if gates 3-4 pass.\n7. Second pass: re-read the draft against the one-sheet contract, field by\n   field, before it ships. Confirm every field is present; confirm the\n   rights-status line contains only facts the user supplied; confirm every OPEN\n   or UNKNOWN item from the checklist survived into the copy verbatim rather\n   than softened; confirm no banned adjective from the copy gate came back; and\n   confirm the scene-fit list is as long as the real fits, not padded to three.\n   Fix what fails, then re-read once more.\n8. Stop at a clean review package. No promo CTA, placement promise, clearance\n   claim, or outreach claim.\n\n## One-sheet contract\n\nThe one-sheet is supervisor-facing. It contains exactly these fields:\n\n```text\nTrack \u002F artist \u002F featuring:\nLength \u002F tempo \u002F key (if known):\nGenre and mood tags:\nSounds like: (era and energy references; never copy a protected identity)\nScene fits: (top 3, one line each)\nLyric themes:\nLyric flags:\nVersions available: (master \u002F instrumental \u002F clean \u002F stems)\nAI involvement: (none, or per element; only what the user supplied)\nRights status: (one line, confirmed facts only; one-stop yes \u002F no \u002F unknown)\nOpen clearance questions:\nContact path:\nPublic link:\n```\n\nThe rights-status line states only confirmed facts and names the open\nquestions. Never compress \"unknown\" into silence.\n\n## Failure modes\n\n- **Missing master or instrumental**: flag in the asset checklist as a blocker.\n  Do not complete the sync angle without at minimum a confirmed master file\n  path.\n- **Unresolved sample**: sample status is \"OPEN, do not pitch until cleared.\"\n  No pitch copy (hard gate 4).\n- **Unknown splits or ownership**: flag in clearance questions. The package can\n  be built but must carry the caveat: \"Rights holder confirmation required\n  before placement.\"\n- **No contact path**: the package is complete but note: \"No contact path\n  identified: supervisor cannot follow up.\"\n- **Scope creep**: if the request becomes a promo funnel, placement promise, or\n  clearance claim, stop and restate the boundary: \"This skill prepares\n  review-ready materials. It does not clear rights, confirm placement, or\n  generate outreach.\"\n\n## Red flags: stop\n\nIf any of these appear in your reasoning, stop and re-read the hard gates:\n\n- \"The artist says it's cleared.\" A claim is not clearance. Status stays\n  UNCONFIRMED with a clearance question attached.\n- \"We'll sort splits later.\" Splits sort before pitching, or the gap ships as\n  an open question. Never silently.\n- \"The supervisor is waiting: skip the instrumental check.\" The checklist is\n  the package. Skipping it ships a track no one can license.\n- \"It's a small indie film, nobody checks samples.\" Sample status is binary:\n  cleared with proof, or OPEN.\n- \"Soften the sample note so the one-sheet reads better.\" Hidden risk reads\n  worse in a licensing call.\n\n## Public copy gate\n\nBefore outputting one-sheet copy, pitch email, captions, DMs, press angles,\nsite copy, bios, CTAs, or review language, run the Suede AI anti-slop line\nedit; `suede-deslop` owns that pattern list in full. Name the actor and keep the\nconcrete track artifact.\n\nSync copy has its own cliché attractor that a general anti-slop pass does not\ncatch, because the sentences are clean: they just say nothing. These are\nbanned in one-sheet and pitch copy:\n\n`cinematic` · `anthemic` · `haunting` · `soaring` · `driving` · `epic` ·\n`ethereal` · `raw and honest` · `infectious` · `cuts through the mix` ·\n`builds to an emotional payoff` · `perfect for the moment when the hero…`\n\nReplace a banned word with a **concrete musical fact drawn from the facts the\nuser supplied**: tempo, key, instrumentation, an arrangement turn (\"drums drop\nout at 1:48, vocal and room noise only\"), or a quoted lyric line. Never a\nsynonym, and never a fact you inferred: if the input contract did not supply it,\nleave it out rather than invent it. The substitution is descriptive copy only:\nit may never introduce rights, ownership, or clearance language, which stays\ngoverned by hard gates 1-2 and 5. A supervisor skims twelve one-sheets an hour;\nthe concrete one is the one they can picture against a scene.\n\n## Output\n\n```text\nSync positioning:\nBest scenes:\nMood tags:\nLyric flags:\nAsset checklist: (each item exists \u002F missing \u002F unknown)\nConfirmed rights facts:\nAI involvement:\nClearance questions:\nOne-sheet: (per the one-sheet contract above)\nPitch email: (only if hard gates 3-4 pass)\nNext review step:\n```\n\n## Routing\n\n- Rights gaps, missing provenance, or undocumented human authorship →\n  **suede-rights-passport** (audit mode, then package).\n- This grows into a release campaign → **suede-campaign-in-a-box**.\n- Release folder or metadata gaps → **suede-release-linter**.\n- Standalone public copy beyond the one-sheet → **suede-copy**.\n\nFamily order: suede-release-linter (files) → suede-rights-passport (audit, then\npackage) → suede-sync-packaging (pitch); this skill is step 3.\n","# Suede AI Sync Packaging Skills\n\n## Compatibility\n\nUses supplied track facts, lyrics, rights evidence, and a confirmed master path. Media inspection needs an available local viewer or supplied timecodes; no distributor or outreach integration is required.\n\nFor a concrete input, expected handoff, and failure check, read\n[the worked handoff](references\u002Fworked-handoff.md).\n\n## Gate policy\n\nEvery check and verdict here is advice to the user, not a control on the agent.\nRun the checks, report results honestly, and complete what the user asked. A\nfailed gate changes the report, never the work. The one exception: a finding\nthat risks data loss, credential exposure, a legal or rights violation, a\npayment mistake, or irreversible public damage. Pause, name the risk, give the\noptions, and let the user choose.\n\n**Core principle:** a sync package makes a track easy to evaluate; it never\nasserts the track is cleared. Confirmed facts and open clearance questions\ntravel in separate, labeled piles, every time.\n\n## Input contract\n\nProvide at minimum:\n\n- **Track**: title, artist, featuring credits if any\n- **Target world**: film \u002F TV \u002F ads \u002F games \u002F trailers \u002F creator campaigns \u002F brand brief (or \"general sync\")\n- **Available assets**: which of master, instrumental, clean, stems, lyrics, credits, splits currently exist\n- **Rights status**: what is confirmed vs. unknown (sample clearance, ownership splits, publishing assignment, one-stop or not)\n- **AI involvement**: none, or which elements used generative AI (vocals, instrumentation, composition, lyrics, post-production)\n\nOptional but useful: reference sync placements the artist admires, mood or\nscene keywords, existing pitches or supervisor feedback.\n\nIf no rights status is provided, treat every clearance question as open. If AI\ninvolvement is not stated, it is an open clearance question too.\n\nRead `references\u002Fsync-norms.md` for deliverable specs, one-stop, and why AI\ninvolvement now sits in the clearance pile.\n\n## Hard gates\n\nDo not rationalize past these:\n\n1. **Never claim or imply clearance.** A rights fact appears as confirmed only\n   when the user supplies the confirmation (signed split sheet, executed\n   license, rights-holder statement). Anything else stays OPEN or UNKNOWN. You\n   organize the questions; you never answer them.\n2. **Never resolve a rights question yourself.** If ownership, splits, samples,\n   or publishing are unclear, mark the item UNKNOWN. Do not infer, average, or\n   assume. Route the gap to suede-rights-passport (audit mode).\n3. **Asset checklist before pitch copy.** Do not write one-sheet or pitch-email\n   copy until the instrumental\u002Fclean asset checklist is filled in: every\n   version marked exists \u002F missing \u002F unknown, with at minimum a confirmed\n   master file path. Missing instrumental or clean versions are flagged in the\n   one-sheet, not glossed.\n4. **Unresolved sample = pause and put it to the user.** Uncleared samples are\n   a legal-risk finding: mark sample status \"OPEN: recommend not pitching\n   until cleared,\" tell the user exactly what is unresolved, and let them\n   decide whether pitch copy is still drafted. If they proceed, the OPEN flag\n   stays embedded in the one-sheet and pitch materials.\n5. **Lyric flags are mandatory.** Screen the lyrics and flag profanity, brand\n   and product names, artist name-drops, violence, drugs and alcohol, sexual\n   content, religious and political content, and date-stamped references. If\n   no lyrics are supplied, write \"Lyric flags: not screened, lyrics not\n   provided.\" A lyric surprise in review kills the placement.\n6. **Sync fit is an assessment, not a compliment.** \"No clear scene fit for the\n   stated target world\" is a valid, useful finding: say it plainly and say why.\n   Never pad the scene-fit list to reach three; two real fits beat three, and\n   one real fit beats two. Never call a track a placement candidate when the\n   asset checklist or the clearance questions say it cannot be pitched yet. The\n   supervisor will find the weak angle faster than the artist will.\n\n## Package workflow\n\n1. Identify the track, artist, genre, mood, tempo, lyric themes, versions,\n   existing assets, and target sync world.\n2. Build the sync angle: scene fit; emotional use; trailer or montage fit;\n   brand fit; game or sports fit; creator campaign fit: assessed, not flattered\n   (hard gate 6).\n3. Fill the asset checklist: master file; instrumental; clean version; stems\n   if available; lyrics; credits; splits; sample status; contact path;\n   public\u002Fprivate links. Each item: exists \u002F missing \u002F unknown.\n4. Screen lyrics and write the lyric flags (hard gate 5).\n5. Separate confirmed rights facts from open clearance questions (hard gates\n   1-2).\n6. Write the one-sheet and pitch email only if gates 3-4 pass.\n7. Second pass: re-read the draft against the one-sheet contract, field by\n   field, before it ships. Confirm every field is present; confirm the\n   rights-status line contains only facts the user supplied; confirm every OPEN\n   or UNKNOWN item from the checklist survived into the copy verbatim rather\n   than softened; confirm no banned adjective from the copy gate came back; and\n   confirm the scene-fit list is as long as the real fits, not padded to three.\n   Fix what fails, then re-read once more.\n8. Stop at a clean review package. No promo CTA, placement promise, clearance\n   claim, or outreach claim.\n\n## One-sheet contract\n\nThe one-sheet is supervisor-facing. It contains exactly these fields:\n\n```text\nTrack \u002F artist \u002F featuring:\nLength \u002F tempo \u002F key (if known):\nGenre and mood tags:\nSounds like: (era and energy references; never copy a protected identity)\nScene fits: (top 3, one line each)\nLyric themes:\nLyric flags:\nVersions available: (master \u002F instrumental \u002F clean \u002F stems)\nAI involvement: (none, or per element; only what the user supplied)\nRights status: (one line, confirmed facts only; one-stop yes \u002F no \u002F unknown)\nOpen clearance questions:\nContact path:\nPublic link:\n```\n\nThe rights-status line states only confirmed facts and names the open\nquestions. Never compress \"unknown\" into silence.\n\n## Failure modes\n\n- **Missing master or instrumental**: flag in the asset checklist as a blocker.\n  Do not complete the sync angle without at minimum a confirmed master file\n  path.\n- **Unresolved sample**: sample status is \"OPEN, do not pitch until cleared.\"\n  No pitch copy (hard gate 4).\n- **Unknown splits or ownership**: flag in clearance questions. The package can\n  be built but must carry the caveat: \"Rights holder confirmation required\n  before placement.\"\n- **No contact path**: the package is complete but note: \"No contact path\n  identified: supervisor cannot follow up.\"\n- **Scope creep**: if the request becomes a promo funnel, placement promise, or\n  clearance claim, stop and restate the boundary: \"This skill prepares\n  review-ready materials. It does not clear rights, confirm placement, or\n  generate outreach.\"\n\n## Red flags: stop\n\nIf any of these appear in your reasoning, stop and re-read the hard gates:\n\n- \"The artist says it's cleared.\" A claim is not clearance. Status stays\n  UNCONFIRMED with a clearance question attached.\n- \"We'll sort splits later.\" Splits sort before pitching, or the gap ships as\n  an open question. Never silently.\n- \"The supervisor is waiting: skip the instrumental check.\" The checklist is\n  the package. Skipping it ships a track no one can license.\n- \"It's a small indie film, nobody checks samples.\" Sample status is binary:\n  cleared with proof, or OPEN.\n- \"Soften the sample note so the one-sheet reads better.\" Hidden risk reads\n  worse in a licensing call.\n\n## Public copy gate\n\nBefore outputting one-sheet copy, pitch email, captions, DMs, press angles,\nsite copy, bios, CTAs, or review language, run the Suede AI anti-slop line\nedit; `suede-deslop` owns that pattern list in full. Name the actor and keep the\nconcrete track artifact.\n\nSync copy has its own cliché attractor that a general anti-slop pass does not\ncatch, because the sentences are clean: they just say nothing. These are\nbanned in one-sheet and pitch copy:\n\n`cinematic` · `anthemic` · `haunting` · `soaring` · `driving` · `epic` ·\n`ethereal` · `raw and honest` · `infectious` · `cuts through the mix` ·\n`builds to an emotional payoff` · `perfect for the moment when the hero…`\n\nReplace a banned word with a **concrete musical fact drawn from the facts the\nuser supplied**: tempo, key, instrumentation, an arrangement turn (\"drums drop\nout at 1:48, vocal and room noise only\"), or a quoted lyric line. Never a\nsynonym, and never a fact you inferred: if the input contract did not supply it,\nleave it out rather than invent it. The substitution is descriptive copy only:\nit may never introduce rights, ownership, or clearance language, which stays\ngoverned by hard gates 1-2 and 5. A supervisor skims twelve one-sheets an hour;\nthe concrete one is the one they can picture against a scene.\n\n## Output\n\n```text\nSync positioning:\nBest scenes:\nMood tags:\nLyric flags:\nAsset checklist: (each item exists \u002F missing \u002F unknown)\nConfirmed rights facts:\nAI involvement:\nClearance questions:\nOne-sheet: (per the one-sheet contract above)\nPitch email: (only if hard gates 3-4 pass)\nNext review step:\n```\n\n## Routing\n\n- Rights gaps, missing provenance, or undocumented human authorship →\n  **suede-rights-passport** (audit mode, then package).\n- This grows into a release campaign → **suede-campaign-in-a-box**.\n- Release folder or metadata gaps → **suede-release-linter**.\n- Standalone public copy beyond the one-sheet → **suede-copy**.\n\nFamily order: suede-release-linter (files) → suede-rights-passport (audit, then\npackage) → suede-sync-packaging (pitch); this skill is step 3.\n",{"name":5,"metadata":45,"description":7},{"display-name":46},"Suede AI Sync Packaging Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-sync-packaging",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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-sync-packaging",{"tool":63,"command":64},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-sync-packaging",{"tool":66,"command":67},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-sync-packaging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-sync-packaging\u002FSKILL.md",true,[71,77,81,85],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"agents\u002Fopenai.yaml","REFERENCE","参考文档",420,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-sync-packaging\u002Fagents\u002Fopenai.yaml",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"CARD.md",4706,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-sync-packaging\u002FCARD.md",{"path":82,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fsync-norms.md",3256,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-sync-packaging\u002Freferences\u002Fsync-norms.md",{"path":86,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fworked-handoff.md",1765,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-sync-packaging\u002Freferences\u002Fworked-handoff.md",[90,100,108,116,124,132],{"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":94,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":99},"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":99},"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":99},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":99},"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":99},"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":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":99},"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",[],[]]