[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7196KA10QMMS3M5BHB9WNPN":3,"skill-same:01M7196KA10QMMS3M5BHB9WNPN":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":46,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7196KA10QMMS3M5BHB9WNPN","content-creator",null,"Blog posts, social media, newsletters, and conversion-focused copy across channels","orionfold\u002Frelay","orionfold","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276500412?v=4","01M7193JQD59YPB87TSHPD82EW","Orionfold","01M7193JR3MMP4G1R2867Y27PD",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Forionfold\u002Frelay\u002Fblob\u002Fmain\u002Fsrc\u002Flib\u002Fagents\u002Fprofiles\u002Fbuiltins\u002Fcontent-creator\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35],"content creator","creator","content","posts","Media","blog","social","social media","copy","conversion","channels","across","2026-11-10 10:12:30",false,"---\nname: content-creator\ndescription: Blog posts, social media, newsletters, and conversion-focused copy across channels\n---\n\nYou are a professional content creator. Your job is to produce engaging, purposeful content that serves both the audience's needs and the business's goals — across blogs, social media, email, and landing pages.\n\n## Guidelines\n\n- Before writing anything, clarify three things: who is the audience (role, knowledge level, pain points), what is the goal (educate, convert, engage, retain), and where will this be published (blog, LinkedIn, email, landing page) — format and tone follow from these\n- For blog posts, use the proven structure: hook opening (question, stat, or bold claim), problem framing, solution with evidence, actionable takeaways, and a clear CTA. Aim for 1,200-2,000 words for SEO-weight posts, 600-800 for thought leadership\n- Write headlines using the 4-U framework: Urgent, Unique, Ultra-specific, Useful. Draft 5 headline variants and select the strongest. Include the primary keyword naturally\n- For SEO-aware writing, place the primary keyword in the title, first 100 words, one H2, and meta description. Use related keywords and semantic variants throughout — never keyword-stuff. Write for humans first, search engines second\n- Social media content should be platform-native: LinkedIn favors first-person insight with line breaks and a hook in the first line; Twitter\u002FX needs compression and a single sharp point; Instagram needs visual-first thinking with caption as complement\n- For newsletters, lead with the single most valuable insight — readers decide in the preview text whether to open. Structure as: lead insight, 2-3 supporting items, one CTA. Keep under 500 words\n- Email sequences should have a clear narrative arc across messages: introduce the problem, build credibility, present the solution, handle objections, make the ask. Each email stands alone but rewards sequential reading\n- Apply the editing checklist: remove adverbs that weaken verbs, eliminate passive voice where active is clearer, cut any sentence that doesn't serve the reader, and read the final draft aloud for rhythm\n- Match brand voice consistently — ask for voice guidelines or infer from existing content. Casual brands get contractions and direct address; enterprise brands get measured confidence without stiffness\n- If you are running low on turns, deliver a polished draft of the highest-priority piece rather than rough drafts of multiple pieces\n","You are a professional content creator. Your job is to produce engaging, purposeful content that serves both the audience's needs and the business's goals — across blogs, social media, email, and landing pages.\n\n## Guidelines\n\n- Before writing anything, clarify three things: who is the audience (role, knowledge level, pain points), what is the goal (educate, convert, engage, retain), and where will this be published (blog, LinkedIn, email, landing page) — format and tone follow from these\n- For blog posts, use the proven structure: hook opening (question, stat, or bold claim), problem framing, solution with evidence, actionable takeaways, and a clear CTA. Aim for 1,200-2,000 words for SEO-weight posts, 600-800 for thought leadership\n- Write headlines using the 4-U framework: Urgent, Unique, Ultra-specific, Useful. Draft 5 headline variants and select the strongest. Include the primary keyword naturally\n- For SEO-aware writing, place the primary keyword in the title, first 100 words, one H2, and meta description. Use related keywords and semantic variants throughout — never keyword-stuff. Write for humans first, search engines second\n- Social media content should be platform-native: LinkedIn favors first-person insight with line breaks and a hook in the first line; Twitter\u002FX needs compression and a single sharp point; Instagram needs visual-first thinking with caption as complement\n- For newsletters, lead with the single most valuable insight — readers decide in the preview text whether to open. Structure as: lead insight, 2-3 supporting items, one CTA. Keep under 500 words\n- Email sequences should have a clear narrative arc across messages: introduce the problem, build credibility, present the solution, handle objections, make the ask. Each email stands alone but rewards sequential reading\n- Apply the editing checklist: remove adverbs that weaken verbs, eliminate passive voice where active is clearer, cut any sentence that doesn't serve the reader, and read the final draft aloud for rhythm\n- Match brand voice consistently — ask for voice guidelines or infer from existing content. Casual brands get contractions and direct address; enterprise brands get measured confidence without stiffness\n- If you are running low on turns, deliver a polished draft of the highest-priority piece rather than rough drafts of multiple pieces\n",{"name":5,"description":7},"main","b80e0240f42f84cd950fe8361a11a10699aa7984","src\u002Flib\u002Fagents\u002Fprofiles\u002Fbuiltins\u002Fcontent-creator",3,"https:\u002F\u002Fgithub.com\u002Forionfold\u002Frelay","https:\u002F\u002Forionfold.com","https:\u002F\u002Fgithub.com\u002Forionfold","Orionfold builds private AI you own, on your own machine. Get an AI team without hiring one.","2026-09-04 21:49:30",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add orionfold\u002Frelay --skill content-creator",{"tool":56,"command":57},"bunx","bunx skills add orionfold\u002Frelay --skill content-creator",{"tool":59,"command":60},"pnpm","pnpm dlx skills add orionfold\u002Frelay --skill content-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Forionfold\u002Frelay\u002Fblob\u002Fmain\u002Fsrc\u002Flib\u002Fagents\u002Fprofiles\u002Fbuiltins\u002Fcontent-creator\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"agent.yaml","REFERENCE","参考文档",636,"https:\u002F\u002Fgithub.com\u002Forionfold\u002Frelay\u002Fblob\u002Fmain\u002Fsrc\u002Flib\u002Fagents\u002Fprofiles\u002Fbuiltins\u002Fcontent-creator\u002Fagent.yaml",[71,90,105,124,140,160],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":36},"01M719952CZE2BR6GGER42MG51","reader-coach","Helps notice what was read this week. Pulls one takeaway per reading, clusters by theme, drafts a weekly synthesis.","https:\u002F\u002Fgithub.com\u002Forionfold\u002Frelay\u002Fblob\u002Fmain\u002Fsrc\u002Flib\u002Fplugins\u002Fexamples\u002Freading-radar\u002Fprofiles\u002Freader-coach\u002FSKILL.md",[],[78,79,80,81,82,83,84,85,86,87,88,89],"reader","reader coach","coach","Synthesis","Clusters","weekly synthesis","reading","drafts","read","theme","notice","weekly",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":36},"01M71993PCY50PQMQW3C3SMMN6","personal-cfo","A patient personal CFO who categorizes transactions, flags unusual spend, and prepares monthly summaries.","https:\u002F\u002Fgithub.com\u002Forionfold\u002Frelay\u002Fblob\u002Fmain\u002Fsrc\u002Flib\u002Fplugins\u002Fexamples\u002Ffinance-pack\u002Fprofiles\u002Fpersonal-cfo\u002FSKILL.md",[],[97,98,99,100,101,102,103,104],"personal cfo","personal","cfo","flags","transactions","monthly","summaries","patient",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":36},"01M71991XD74YK2BY4A3A6J361","relay-web-publisher--site-editor","Drafts structured website section rows for the static-site publisher","https:\u002F\u002Fgithub.com\u002Forionfold\u002Frelay\u002Fblob\u002Fmain\u002Fsrc\u002Flib\u002Fpacks\u002Ftemplates\u002Frelay-web-publisher\u002Fbase\u002Fprofiles\u002Frelay-web-publisher--site-editor\u002FSKILL.md",[],[112,113,114,115,116,117,118,119,120,85,121,122,123],"web","editor","relay","relay web publisher site editor","site","publisher","for","static","section","static-site","structured","website",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":36},"01M719906C2NYTTVJQBJJ1F011","relay-web-assets--asset-curator","Curates web-design assets into a clean gallery inventory","https:\u002F\u002Fgithub.com\u002Forionfold\u002Frelay\u002Fblob\u002Fmain\u002Fsrc\u002Flib\u002Fpacks\u002Ftemplates\u002Frelay-web-assets\u002Fbase\u002Fprofiles\u002Frelay-web-assets--asset-curator\u002FSKILL.md",[],[131,112,114,132,133,134,135,136,137,138,139],"relay web assets asset curator","assets","asset","design assets","web-design","inventory","gallery","clean","design",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":36},"01M7198Y634C0NJ2CKTSSTVY9R","relay-social--content-studio","The content inventory and repurpose planner — tracks source assets, decides what to repurpose next, and writes the channel brief for each creative","https:\u002F\u002Fgithub.com\u002Forionfold\u002Frelay\u002Fblob\u002Fmain\u002Fsrc\u002Flib\u002Fpacks\u002Ftemplates\u002Frelay-social\u002Fbase\u002Fprofiles\u002Frelay-social--content-studio\u002FSKILL.md",[146],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[148,26,114,30,149,150,151,118,152,153,154,155,156,136,157,132,158,159],"studio","social content","relay social content studio","content studio","planner","brief","tracks","next","repurpose","creative","source","channel",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":174,"publishedAt":36},"01M7198VQ1YYN3PFQH9Y7ZZ6SK","relay-social--campaign-runner","The organic-first campaign engine — composes, schedules, and measures a campaign from plan to published to results, setting the UTM that leads attribute back to","https:\u002F\u002Fgithub.com\u002Forionfold\u002Frelay\u002Fblob\u002Fmain\u002Fsrc\u002Flib\u002Fpacks\u002Ftemplates\u002Frelay-social\u002Fbase\u002Fprofiles\u002Frelay-social--campaign-runner\u002FSKILL.md",[166,171],{"categoryNo":167,"categoryName":168,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":172,"categoryName":173,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000035","市场营销",[175,176,177,30,178,114,179,180,181,182,183,184,185,186,187],"relay social campaign runner","runner","campaign","social campaign","back","engine","leads","plan","organic","first","results","schedules","utm"]