[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MKX6GSZ3PWVXCZ7452B1Z1":3,"skill-same:01M6MKX6GSZ3PWVXCZ7452B1Z1":79},{"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":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6MKX6GSZ3PWVXCZ7452B1Z1","turn-this-into-a-thread",null,"Turn a long idea, transcript, article or rambling draft into a Twitter thread where every tweet earns the next one. Use when someone asks for a thread, asks to break something long into tweets, or has a piece of writing too long for one post. Do not use it for LinkedIn, which has no threads, and do not pad a small idea into a long thread.","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\u002Fprateeks367\u002Fvoicemoat-skills\u002Fskills\u002Fturn-this-into-a-thread\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","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],"thread","turn this into a thread","long","when","break","for","too long","which","threads","it","post","writing","article","draft","next","do","idea","use","linkedin","twitter","transcript","2026-11-10 10:12:30",false,"---\nname: turn-this-into-a-thread\ndescription: Turn a long idea, transcript, article or rambling draft into a Twitter thread where every tweet earns the next one. Use when someone asks for a thread, asks to break something long into tweets, or has a piece of writing too long for one post. Do not use it for LinkedIn, which has no threads, and do not pad a small idea into a long thread.\n---\n\n# Turn this into a thread\n\nMost threads fail for one of two reasons. Either they are an article chopped\ninto tweet-sized pieces, so no individual tweet is worth reading, or they are a\nsmall idea stretched to eleven tweets because the writer thought longer meant\nbetter.\n\nA thread works when each tweet would be a decent post on its own, and the order\nmakes it better.\n\n## Step 1: decide whether it should be a thread at all\n\nAsk what the idea actually is, in one sentence.\n\nIf the answer is a single point with one piece of support, it is a post. Say so\nand offer to write that instead. A three-tweet thread that should have been one\ntweet loses readers at tweet two and looks like padding.\n\nThreads earn their length when there is a genuine sequence: steps, a story with\nturns, several distinct points under one argument, or a list where each item\nstands alone.\n\n## Step 2: find the spine\n\nBefore writing tweets, write the skeleton. One line per beat, in order. Usually\nfive to nine beats. If you cannot fill seven without repeating yourself, the\nthread is shorter than you thought, and that is good news.\n\nCheck the order does something. If the beats could be shuffled with no loss, it\nis a list, not a thread, and it should be labelled as one so readers know they\ncan dip in.\n\n## Step 3: write it\n\n**The first tweet is the whole thread's job interview.** It has to make sense\nalone and promise something specific. Not \"a thread on writing\" but the actual\nclaim. Never open with \"A thread ?\" as the substance; the reader can see it is\na thread.\n\n**Every following tweet must survive alone.** No tweet should begin with a word\nthat only makes sense if you read the last one. Someone will land on tweet\nfive, and quoting it should not embarrass them.\n\n**One idea per tweet.** Two ideas in a tweet means one of them is wasted.\n\n**Land it.** The last tweet closes the loop opened by the first. If it ends\nwith a call to action, keep it to one, and only if it is honest.\n\n## Step 4: format it properly\n\nSeparate each tweet with a line containing only three dashes:\n\n```\nFirst tweet text.\n\n---\n\nSecond tweet text.\n```\n\nThat is the separator VoiceMoat uses to chain a thread, and it also just reads\ncleanly if the person is posting by hand.\n\nNumber the tweets only if the order is genuinely instructional. Numbering a\nstory makes it feel like homework.\n\n## What changes when VoiceMoat is connected\n\n- `get_voice_profile` means the thread sounds like your Twitter voice\n  specifically, which in VoiceMoat is a separate trained profile from your\n  LinkedIn one. Threads written in a LinkedIn register are a common and\n  obvious failure.\n- `score_voice_match` scores the drafted thread against that profile.\n- `improve_post` accepts a thread rather than treating it as one long post, so\n  the improvement pass respects the tweet boundaries instead of rewriting\n  across them.\n- `publish_post` posts the thread as a genuinely chained thread, splitting on\n  that three-dash separator and replying each part to the one before, behind a\n  preview and a one-time confirmation. `schedule_post` queues it the same way.\n\nNever make the second call on your own. Show the person the exact preview the\nfirst call returns and wait for a clear yes before you send the one-time code\nback. Never make both calls in one step. The assistant may show the preview as\na card with its own Post now or Schedule button. A press on that button is the\nperson's yes and sends the code itself, so do not send it again.\n\nVoiceMoat is at voicemoat.com. The connector needs the Pro or Enterprise plan.\n","# Turn this into a thread\n\nMost threads fail for one of two reasons. Either they are an article chopped\ninto tweet-sized pieces, so no individual tweet is worth reading, or they are a\nsmall idea stretched to eleven tweets because the writer thought longer meant\nbetter.\n\nA thread works when each tweet would be a decent post on its own, and the order\nmakes it better.\n\n## Step 1: decide whether it should be a thread at all\n\nAsk what the idea actually is, in one sentence.\n\nIf the answer is a single point with one piece of support, it is a post. Say so\nand offer to write that instead. A three-tweet thread that should have been one\ntweet loses readers at tweet two and looks like padding.\n\nThreads earn their length when there is a genuine sequence: steps, a story with\nturns, several distinct points under one argument, or a list where each item\nstands alone.\n\n## Step 2: find the spine\n\nBefore writing tweets, write the skeleton. One line per beat, in order. Usually\nfive to nine beats. If you cannot fill seven without repeating yourself, the\nthread is shorter than you thought, and that is good news.\n\nCheck the order does something. If the beats could be shuffled with no loss, it\nis a list, not a thread, and it should be labelled as one so readers know they\ncan dip in.\n\n## Step 3: write it\n\n**The first tweet is the whole thread's job interview.** It has to make sense\nalone and promise something specific. Not \"a thread on writing\" but the actual\nclaim. Never open with \"A thread ?\" as the substance; the reader can see it is\na thread.\n\n**Every following tweet must survive alone.** No tweet should begin with a word\nthat only makes sense if you read the last one. Someone will land on tweet\nfive, and quoting it should not embarrass them.\n\n**One idea per tweet.** Two ideas in a tweet means one of them is wasted.\n\n**Land it.** The last tweet closes the loop opened by the first. If it ends\nwith a call to action, keep it to one, and only if it is honest.\n\n## Step 4: format it properly\n\nSeparate each tweet with a line containing only three dashes:\n\n```\nFirst tweet text.\n\n---\n\nSecond tweet text.\n```\n\nThat is the separator VoiceMoat uses to chain a thread, and it also just reads\ncleanly if the person is posting by hand.\n\nNumber the tweets only if the order is genuinely instructional. Numbering a\nstory makes it feel like homework.\n\n## What changes when VoiceMoat is connected\n\n- `get_voice_profile` means the thread sounds like your Twitter voice\n  specifically, which in VoiceMoat is a separate trained profile from your\n  LinkedIn one. Threads written in a LinkedIn register are a common and\n  obvious failure.\n- `score_voice_match` scores the drafted thread against that profile.\n- `improve_post` accepts a thread rather than treating it as one long post, so\n  the improvement pass respects the tweet boundaries instead of rewriting\n  across them.\n- `publish_post` posts the thread as a genuinely chained thread, splitting on\n  that three-dash separator and replying each part to the one before, behind a\n  preview and a one-time confirmation. `schedule_post` queues it the same way.\n\nNever make the second call on your own. Show the person the exact preview the\nfirst call returns and wait for a clear yes before you send the one-time code\nback. Never make both calls in one step. The assistant may show the preview as\na card with its own Post now or Schedule button. A press on that button is the\nperson's yes and sends the code itself, so do not send it again.\n\nVoiceMoat is at voicemoat.com. The connector needs the Pro or Enterprise plan.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fprateeks367\u002Fvoicemoat-skills\u002Fskills\u002Fturn-this-into-a-thread",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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill turn-this-into-a-thread",{"tool":71,"command":72},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill turn-this-into-a-thread",{"tool":74,"command":75},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill turn-this-into-a-thread","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fprateeks367\u002Fvoicemoat-skills\u002Fskills\u002Fturn-this-into-a-thread\u002FSKILL.md",true,[],[80,90,98,106,114,122],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":89},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":89},"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":89},"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":89},"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":89},"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",[],[]]