[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JC56B1KBHK5BF6J3DFNPJQ":3,"skill-same:01M6JC56B1KBHK5BF6J3DFNPJQ":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6JC56B1KBHK5BF6J3DFNPJQ","crosspost",null,"Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fcontent\u002Fcrosspost\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"threads","content","posts","content distribution","multi","distribution","distribute","platform","across","cross-platform","social","patterns","bluesky","never","use","user","linkedin","engine","2026-11-10 10:12:30",false,"---\nname: crosspost\ndescription: Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.\norigin: ECC\n---\n\n# Crosspost\n\nDistribute content across platforms without turning it into the same fake post in four costumes.\n\n## When to Activate\n\n- the user wants to publish the same underlying idea across multiple platforms\n- a launch, update, release, or essay needs platform-specific versions\n- the user says \"crosspost\", \"post this everywhere\", or \"adapt this for X and LinkedIn\"\n\n## Core Rules\n\n1. Do not publish identical copy across platforms.\n2. Preserve the author's voice across platforms.\n3. Adapt for constraints, not stereotypes.\n4. One post should still be about one thing.\n5. Do not invent a CTA, question, or moral if the source did not earn one.\n\n## Workflow\n\n### Step 1: Start with the Primary Version\n\nPick the strongest source version first:\n- the original X post\n- the original article\n- the launch note\n- the thread\n- the memo or changelog\n\nUse `content-engine` first if the source still needs voice shaping.\n\n### Step 2: Capture the Voice Fingerprint\n\nRun `brand-voice` first if the source voice is not already captured in the current session.\n\nReuse the resulting `VOICE PROFILE` directly.\nDo not build a second ad hoc voice checklist here unless the user explicitly wants a fresh override for this campaign.\n\n### Step 3: Adapt by Platform Constraint\n\n### X\n\n- keep it compressed\n- lead with the sharpest claim or artifact\n- use a thread only when a single post would collapse the argument\n- avoid hashtags and generic filler\n\n### LinkedIn\n\n- add only the context needed for people outside the niche\n- do not turn it into a fake founder-reflection post\n- do not add a closing question just because it is LinkedIn\n- do not force a polished \"professional tone\" if the author is naturally sharper\n\n### Threads\n\n- keep it readable and direct\n- do not write fake hyper-casual creator copy\n- do not paste the LinkedIn version and shorten it\n\n### Bluesky\n\n- keep it concise\n- preserve the author's cadence\n- do not rely on hashtags or feed-gaming language\n\n## Posting Order\n\nDefault:\n1. post the strongest native version first\n2. adapt for the secondary platforms\n3. stagger timing only if the user wants sequencing help\n\nDo not add cross-platform references unless useful. Most of the time, the post should stand on its own.\n\n## Banned Patterns\n\nDelete and rewrite any of these:\n- \"Excited to share\"\n- \"Here's what I learned\"\n- \"What do you think?\"\n- \"link in bio\" unless that is literally true\n- generic \"professional takeaway\" paragraphs that were not in the source\n\n## Output Format\n\nReturn:\n- the primary platform version\n- adapted variants for each requested platform\n- a short note on what changed and why\n- any publishing constraint the user still needs to resolve\n\n## Quality Gate\n\nBefore delivering:\n- each version reads like the same author under different constraints\n- no platform version feels padded or sanitized\n- no copy is duplicated verbatim across platforms\n- any extra context added for LinkedIn or newsletter use is actually necessary\n\n## Related Skills\n\n- `brand-voice` for reusable source-derived voice capture\n- `content-engine` for voice capture and source shaping\n- `x-api` for X publishing workflows\n","# Crosspost\n\nDistribute content across platforms without turning it into the same fake post in four costumes.\n\n## When to Activate\n\n- the user wants to publish the same underlying idea across multiple platforms\n- a launch, update, release, or essay needs platform-specific versions\n- the user says \"crosspost\", \"post this everywhere\", or \"adapt this for X and LinkedIn\"\n\n## Core Rules\n\n1. Do not publish identical copy across platforms.\n2. Preserve the author's voice across platforms.\n3. Adapt for constraints, not stereotypes.\n4. One post should still be about one thing.\n5. Do not invent a CTA, question, or moral if the source did not earn one.\n\n## Workflow\n\n### Step 1: Start with the Primary Version\n\nPick the strongest source version first:\n- the original X post\n- the original article\n- the launch note\n- the thread\n- the memo or changelog\n\nUse `content-engine` first if the source still needs voice shaping.\n\n### Step 2: Capture the Voice Fingerprint\n\nRun `brand-voice` first if the source voice is not already captured in the current session.\n\nReuse the resulting `VOICE PROFILE` directly.\nDo not build a second ad hoc voice checklist here unless the user explicitly wants a fresh override for this campaign.\n\n### Step 3: Adapt by Platform Constraint\n\n### X\n\n- keep it compressed\n- lead with the sharpest claim or artifact\n- use a thread only when a single post would collapse the argument\n- avoid hashtags and generic filler\n\n### LinkedIn\n\n- add only the context needed for people outside the niche\n- do not turn it into a fake founder-reflection post\n- do not add a closing question just because it is LinkedIn\n- do not force a polished \"professional tone\" if the author is naturally sharper\n\n### Threads\n\n- keep it readable and direct\n- do not write fake hyper-casual creator copy\n- do not paste the LinkedIn version and shorten it\n\n### Bluesky\n\n- keep it concise\n- preserve the author's cadence\n- do not rely on hashtags or feed-gaming language\n\n## Posting Order\n\nDefault:\n1. post the strongest native version first\n2. adapt for the secondary platforms\n3. stagger timing only if the user wants sequencing help\n\nDo not add cross-platform references unless useful. Most of the time, the post should stand on its own.\n\n## Banned Patterns\n\nDelete and rewrite any of these:\n- \"Excited to share\"\n- \"Here's what I learned\"\n- \"What do you think?\"\n- \"link in bio\" unless that is literally true\n- generic \"professional takeaway\" paragraphs that were not in the source\n\n## Output Format\n\nReturn:\n- the primary platform version\n- adapted variants for each requested platform\n- a short note on what changed and why\n- any publishing constraint the user still needs to resolve\n\n## Quality Gate\n\nBefore delivering:\n- each version reads like the same author under different constraints\n- no platform version feels padded or sanitized\n- no copy is duplicated verbatim across platforms\n- any extra context added for LinkedIn or newsletter use is actually necessary\n\n## Related Skills\n\n- `brand-voice` for reusable source-derived voice capture\n- `content-engine` for voice capture and source shaping\n- `x-api` for X publishing workflows\n",{"name":5,"origin":46,"description":7},"ECC","master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Fcontent\u002Fcrosspost",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add S3YED\u002Fappie-kit --skill crosspost",{"tool":61,"command":62},"bunx","bunx skills add S3YED\u002Fappie-kit --skill crosspost",{"tool":64,"command":65},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill crosspost","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fcontent\u002Fcrosspost\u002FSKILL.md",true,[],[70,102,137,163,194,218],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":83,"publishedAt":41},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[76,79,82],{"categoryNo":77,"categoryName":78,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":80,"categoryName":81,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101],"music","ai music","humanizer","visualization","Tools","Audio","hermes","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","generation","feature","ai music generation","music generation",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":116,"publishedAt":41},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[108,111],{"categoryNo":109,"categoryName":110,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136],"design","agentic","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","ui","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":145,"publishedAt":41},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[143,144],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},[118,146,122,147,148,149,124,150,151,152,153,154,155,156,157,158,159,160,161,162],"elements","agentic webdesign agent elements","MCP","ai agent","registry","search","streaming","open source","open","Bash","plan","subagent","edit","install","input","lock","source",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":173,"publishedAt":41},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[169,172],{"categoryNo":170,"categoryName":171,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193],"deployment","vercel deployment","vercel","macos","cli","linux","windows","deploy","vercel deploy","REST","api","site","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":201,"publishedAt":41},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[200],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[202,203,204,205,206,207,208,209,210,211,212,213,214,215,38,216,217],"workflows","quality","software","software quality workflows","review","tdd","workflow","commit","debugging","code","debugger","pre-commit","investigation","code simplification","simplification","for",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":222,"categories":223,"keywords":231,"publishedAt":41},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[224,227,230],{"categoryNo":225,"categoryName":226,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":228,"categoryName":229,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[232,233,234,235,236,237,238,239,177,240,241,124,242,180,243,211,244,245,34,246],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","writing","safe","typescript","react components","modular","refactor","simplify","test-driven-development"]