[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M755M53F77ESH9MP259P68Q8":3,"skill-same:01M755M53F77ESH9MP259P68Q8":61},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M755M53F77ESH9MP259P68Q8","threads-style",null,"Use when drafting or editing a post for Threads (Meta): casual, conversational, reply-driven voice.","kuralle\u002Fkuralle-agents","kuralle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F289272678?v=4","01M755GAMJ4VQ7Q14J065W5ZAM","Kuralle","01M755GANGEX5147S8CJY0A72W",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkuralle\u002Fkuralle-agents\u002Fblob\u002Fmain\u002Fapps\u002Fexamples\u002Fmarketing-team\u002Fagent\u002Fsocial-media-coordinator\u002Fskills\u002Fthreads-style\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: threads-style\ndescription: \"Use when drafting or editing a post for Threads (Meta): casual, conversational, reply-driven voice.\"\n---\n\n# Threads voice & style\n\nWhen writing or editing a post for Threads:\n\n- Talk like a person, not a brand. Threads is casual, meme-fluent, and bold, closer to texting a smart friend than posting a press release. Lower polish than LinkedIn is a feature, not a bug.\n- Lead with something real: an observation, a small personal story, or a genuine question. A short story that ends in a question is a reliably strong opener.\n- Aim for one idea per post. The cap is 500 characters and you rarely need all of it; keep it light and skimmable with short paragraphs and line breaks.\n- Write to earn a reply, not a like. The algorithm rewards conversation, and replies and profile clicks weigh more than likes, but never beg for it (\"comment below 👇\", \"agree?\", \"let that sink in\"). Invite genuinely or not at all.\n- One topic tag at most: that's the platform limit, and tag-stuffing buys nothing. It can be a multi-word phrase. A little emoji is fine if it carries tone; no walls.\n- Make it native to Threads. Don't repost an X\u002FTwitter post verbatim; write for this audience, or use the post to react to and extend something published elsewhere.\n- No corporate voice, no announcement-speak, no engagement bait. This is a brand-awareness and conversation surface, not a place for pitches or product demos.\n\n## Structure\n\n1. Open: the relatable hook, the small story, or the question, on line one.\n2. Middle: the detail, the take, or the next story beat.\n3. Close: a light landing or a real, specific invitation to reply.\n\n## References\n\n- `references\u002Fbest-practices.md`: sourced pre-flight checklist of current Threads tactics.\n- `references\u002Fpost-specs.md`: character limit, topic-tag rules, media norms for quick lookup.\n- `references\u002Fbanned-words.json`: the words to avoid. The `lint_against_style` tool checks a draft against this list (surface `threads`), so run the tool rather than reading the file.\n\nGeneral prose quality (AI-tell phrases to avoid, plain-English word swaps) is covered by the `writing-quality` skill; apply it to every draft alongside this one.\n","# Threads voice & style\n\nWhen writing or editing a post for Threads:\n\n- Talk like a person, not a brand. Threads is casual, meme-fluent, and bold, closer to texting a smart friend than posting a press release. Lower polish than LinkedIn is a feature, not a bug.\n- Lead with something real: an observation, a small personal story, or a genuine question. A short story that ends in a question is a reliably strong opener.\n- Aim for one idea per post. The cap is 500 characters and you rarely need all of it; keep it light and skimmable with short paragraphs and line breaks.\n- Write to earn a reply, not a like. The algorithm rewards conversation, and replies and profile clicks weigh more than likes, but never beg for it (\"comment below 👇\", \"agree?\", \"let that sink in\"). Invite genuinely or not at all.\n- One topic tag at most: that's the platform limit, and tag-stuffing buys nothing. It can be a multi-word phrase. A little emoji is fine if it carries tone; no walls.\n- Make it native to Threads. Don't repost an X\u002FTwitter post verbatim; write for this audience, or use the post to react to and extend something published elsewhere.\n- No corporate voice, no announcement-speak, no engagement bait. This is a brand-awareness and conversation surface, not a place for pitches or product demos.\n\n## Structure\n\n1. Open: the relatable hook, the small story, or the question, on line one.\n2. Middle: the detail, the take, or the next story beat.\n3. Close: a light landing or a real, specific invitation to reply.\n\n## References\n\n- `references\u002Fbest-practices.md`: sourced pre-flight checklist of current Threads tactics.\n- `references\u002Fpost-specs.md`: character limit, topic-tag rules, media norms for quick lookup.\n- `references\u002Fbanned-words.json`: the words to avoid. The `lint_against_style` tool checks a draft against this list (surface `threads`), so run the tool rather than reading the file.\n\nGeneral prose quality (AI-tell phrases to avoid, plain-English word swaps) is covered by the `writing-quality` skill; apply it to every draft alongside this one.\n",{"name":5,"description":7},"main","dabc567fec8b44ddbbdd952a25aca59a3b5f2c37","apps\u002Fexamples\u002Fmarketing-team\u002Fagent\u002Fsocial-media-coordinator\u002Fskills\u002Fthreads-style",0,"https:\u002F\u002Fgithub.com\u002Fkuralle\u002Fkuralle-agents","https:\u002F\u002Fagents.kuralle.com","https:\u002F\u002Fgithub.com\u002Fkuralle","Operator-grade voice AI + unified inbox. Home of @kuralle-agents — the open-source TypeScript framework for conversational agents, text and voice.","2026-08-25 15:28:47",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add kuralle\u002Fkuralle-agents --skill threads-style",{"tool":39,"command":40},"bunx","bunx skills add kuralle\u002Fkuralle-agents --skill threads-style",{"tool":42,"command":43},"pnpm","pnpm dlx skills add kuralle\u002Fkuralle-agents --skill threads-style","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkuralle\u002Fkuralle-agents\u002Fblob\u002Fmain\u002Fapps\u002Fexamples\u002Fmarketing-team\u002Fagent\u002Fsocial-media-coordinator\u002Fskills\u002Fthreads-style\u002FSKILL.md",true,[47,53,57],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fbanned-words.json","REFERENCE","参考文档",266,"https:\u002F\u002Fgithub.com\u002Fkuralle\u002Fkuralle-agents\u002Fblob\u002Fmain\u002Fapps\u002Fexamples\u002Fmarketing-team\u002Fagent\u002Fsocial-media-coordinator\u002Fskills\u002Fthreads-style\u002Freferences\u002Fbanned-words.json",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fbest-practices.md",3999,"https:\u002F\u002Fgithub.com\u002Fkuralle\u002Fkuralle-agents\u002Fblob\u002Fmain\u002Fapps\u002Fexamples\u002Fmarketing-team\u002Fagent\u002Fsocial-media-coordinator\u002Fskills\u002Fthreads-style\u002Freferences\u002Fbest-practices.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fpost-specs.md",1562,"https:\u002F\u002Fgithub.com\u002Fkuralle\u002Fkuralle-agents\u002Fblob\u002Fmain\u002Fapps\u002Fexamples\u002Fmarketing-team\u002Fagent\u002Fsocial-media-coordinator\u002Fskills\u002Fthreads-style\u002Freferences\u002Fpost-specs.md",[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M755NPWVX10N22GJD578VS4X","kuralle-agents","Build, extend, or debug an agent with the Kuralle framework (`@kuralle-agents\u002F*`). Use this skill whenever the task touches `defineAgent`, `defineFlow`, `defineTool`, `createRuntime`, a `*.flow.json` definition, an agent folder compiled by `kuralle build`, a Kuralle skill or plugin, or a Kuralle deployment on Hono, Cloudflare Workers, or Next.js. Trigger it for any mention of Kuralle agents, flows, triage routing, durable tools, effect logs, session stores, agent handoffs, collect\u002Freply\u002Faction\u002Fdecide nodes, or the `kuralle` CLI — and also when the user asks to \"build an agent\", \"add a flow\", \"add a tool to the bot\", \"make the bot ask for X first\", or \"deploy the agent\", inside a repository that depends on `@kuralle-agents\u002Fcore`.","https:\u002F\u002Fgithub.com\u002Fkuralle\u002Fkuralle-agents\u002Fblob\u002Fmain\u002Fskills\u002Fkuralle-agents\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M755NNG5M3VDKH4KMXYS3TSJ","remotion-upgrade","Upgrade Remotion, and related packages","https:\u002F\u002Fgithub.com\u002Fkuralle\u002Fkuralle-agents\u002Fblob\u002Fmain\u002Fpackages\u002Fplugins\u002Ftest\u002Ffixtures\u002Fremotion-codex-plugin\u002Fskills\u002Fremotion-upgrade\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M755NMEVT5D0T8T8DS74MWB2","remotion-studio","Preview a Remotion video","https:\u002F\u002Fgithub.com\u002Fkuralle\u002Fkuralle-agents\u002Fblob\u002Fmain\u002Fpackages\u002Fplugins\u002Ftest\u002Ffixtures\u002Fremotion-codex-plugin\u002Fskills\u002Fremotion-studio\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M755NJ86P20N86R312JF0RC3","remotion-saas","Build an app with Remotion","https:\u002F\u002Fgithub.com\u002Fkuralle\u002Fkuralle-agents\u002Fblob\u002Fmain\u002Fpackages\u002Fplugins\u002Ftest\u002Ffixtures\u002Fremotion-codex-plugin\u002Fskills\u002Fremotion-saas\u002FSKILL.md",[],[],{"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":19},"01M755NH81TCSPKSMY1BPXRWA5","remotion-render","Export a Remotion video","https:\u002F\u002Fgithub.com\u002Fkuralle\u002Fkuralle-agents\u002Fblob\u002Fmain\u002Fpackages\u002Fplugins\u002Ftest\u002Ffixtures\u002Fremotion-codex-plugin\u002Fskills\u002Fremotion-render\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M755NFTJK7KMH4C1C83HTAK3","remotion-multimedia","Interacting with Mediabunny","https:\u002F\u002Fgithub.com\u002Fkuralle\u002Fkuralle-agents\u002Fblob\u002Fmain\u002Fpackages\u002Fplugins\u002Ftest\u002Ffixtures\u002Fremotion-codex-plugin\u002Fskills\u002Fremotion-multimedia\u002FSKILL.md",[],[]]