[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MKTXAPQF9EEGZ1R5DR7Y3E":3,"skill-same:01M6MKTXAPQF9EEGZ1R5DR7Y3E":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":18,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6MKTXAPQF9EEGZ1R5DR7Y3E","fix-my-ending",null,"Diagnose why a post's ending is not earning a reply, then rewrite it or remove it. Use when someone asks for a call to action, says nobody comments, asks how to end a post, or has closed with a question that reads as asking a favour. Do not bolt an engagement prompt onto a post that was already finished, and do not promise that a new ending will bring comments.","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\u002Ffix-my-ending\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"fix my ending","fix","my","end","new","when","for","action","earning","bring","how to","as","diagnose","promise","call","do","use","remove","bolt","question","why","how","2026-11-10 10:12:30",false,"---\nname: fix-my-ending\ndescription: Diagnose why a post's ending is not earning a reply, then rewrite it or remove it. Use when someone asks for a call to action, says nobody comments, asks how to end a post, or has closed with a question that reads as asking a favour. Do not bolt an engagement prompt onto a post that was already finished, and do not promise that a new ending will bring comments.\n---\n\n# Fix my ending\n\nThe ending is the part of a post most people write on autopilot. The body gets\ndrafted and redrafted, and then a closing question arrives out of habit,\nusually the same one they used last time.\n\nThat habit has a cost. A weak ending does not just fail to earn a reply. It\ntells the reader the post was an exercise, which is retroactive, and it reaches\nback over everything they just read.\n\n## Step 1: work out what the post is actually for\n\nEndings are not interchangeable, because posts are not. Before touching the\nlast line, say which of these the post is doing:\n\n- Being understood. The reader should leave knowing something.\n- Being argued with. The reader should leave with an opinion.\n- Being saved. The reader will want it again later.\n- Starting a conversation. The reader should reply.\n- Starting a private one. The reader should message.\n\nMost bad endings are a conversation ending stapled to a post that was never\nasking for a conversation.\n\n## Step 2: name the ending it currently has\n\n- **The favour ask.** \"Thoughts?\", \"Agree?\", \"What would you add?\" It asks the\n  reader to do work and gives them no reason to.\n- **The summary.** Repeats what they just read. Nobody rereads a post.\n- **The lesson.** Tells the reader what to feel about a story that already did\n  the telling.\n- **The pivot.** Swings into a pitch the post had not earned.\n- **The real question.** The reader already holds an opinion and has just been\n  given permission to say it.\n- **None.** The last line of the body is the ending, which is often right.\n\n## Step 3: the test for a closing question\n\nCould a stranger answer it in one sentence, without rereading the post, without\nlooking anything up, and without having to agree with you first?\n\nA no on any of those means the question is decoration. Questions that pass are\nalmost always about the reader's own experience rather than about your argument.\n\n## Step 4: rewrite from the purpose, not from a template\n\n- Name the disagreement you expect and invite it by name.\n- Ask for their version of the specific thing, not for their thoughts.\n- Ask for one concrete item. People answer \"what is the worst one you have\n  seen\" and ignore \"what do you think\".\n- End on the sharpest line in the post, moved to the bottom.\n- Stop mid-thought and leave the conclusion to them.\n\n## Step 5: know when to delete it\n\nStory posts usually end best on the last beat of the story. If the draft ends\nwith a story and then a paragraph explaining the story, the paragraph is the\nproblem and deleting it is the fix. Say so rather than rewriting it.\n\n## What this will not do\n\nIt will not promise comments. Whether people reply depends on who saw it, what\nelse was in the feed and whether they have anything to say, none of which the\nlast line controls.\n\nIt also will not write engagement bait. \"Comment YES for the template\" works in\nthe narrow sense of producing comments, and it teaches people that replying to\nyou is a transaction.\n\n## What changes when VoiceMoat is connected\n\nAn ending is the easiest place to slip into somebody else's register, because\nclosing lines are the most copied sentences on both platforms:\n\n- `get_voice_profile` gives the register you actually close in, held separately\n  for LinkedIn and for Twitter, so a LinkedIn sign-off is never judged against\n  how you end a tweet.\n- `score_voice_match` catches the specific failure this skill invites: a strong\n  ending that is strong in the voice of whoever popularised it.\n- `improve_post` runs the whole post again when the ending turns out to be\n  weak because the post never settled what it was for.\n\nVoiceMoat is at voicemoat.com. The connector needs the Pro or Enterprise plan.\n","# Fix my ending\n\nThe ending is the part of a post most people write on autopilot. The body gets\ndrafted and redrafted, and then a closing question arrives out of habit,\nusually the same one they used last time.\n\nThat habit has a cost. A weak ending does not just fail to earn a reply. It\ntells the reader the post was an exercise, which is retroactive, and it reaches\nback over everything they just read.\n\n## Step 1: work out what the post is actually for\n\nEndings are not interchangeable, because posts are not. Before touching the\nlast line, say which of these the post is doing:\n\n- Being understood. The reader should leave knowing something.\n- Being argued with. The reader should leave with an opinion.\n- Being saved. The reader will want it again later.\n- Starting a conversation. The reader should reply.\n- Starting a private one. The reader should message.\n\nMost bad endings are a conversation ending stapled to a post that was never\nasking for a conversation.\n\n## Step 2: name the ending it currently has\n\n- **The favour ask.** \"Thoughts?\", \"Agree?\", \"What would you add?\" It asks the\n  reader to do work and gives them no reason to.\n- **The summary.** Repeats what they just read. Nobody rereads a post.\n- **The lesson.** Tells the reader what to feel about a story that already did\n  the telling.\n- **The pivot.** Swings into a pitch the post had not earned.\n- **The real question.** The reader already holds an opinion and has just been\n  given permission to say it.\n- **None.** The last line of the body is the ending, which is often right.\n\n## Step 3: the test for a closing question\n\nCould a stranger answer it in one sentence, without rereading the post, without\nlooking anything up, and without having to agree with you first?\n\nA no on any of those means the question is decoration. Questions that pass are\nalmost always about the reader's own experience rather than about your argument.\n\n## Step 4: rewrite from the purpose, not from a template\n\n- Name the disagreement you expect and invite it by name.\n- Ask for their version of the specific thing, not for their thoughts.\n- Ask for one concrete item. People answer \"what is the worst one you have\n  seen\" and ignore \"what do you think\".\n- End on the sharpest line in the post, moved to the bottom.\n- Stop mid-thought and leave the conclusion to them.\n\n## Step 5: know when to delete it\n\nStory posts usually end best on the last beat of the story. If the draft ends\nwith a story and then a paragraph explaining the story, the paragraph is the\nproblem and deleting it is the fix. Say so rather than rewriting it.\n\n## What this will not do\n\nIt will not promise comments. Whether people reply depends on who saw it, what\nelse was in the feed and whether they have anything to say, none of which the\nlast line controls.\n\nIt also will not write engagement bait. \"Comment YES for the template\" works in\nthe narrow sense of producing comments, and it teaches people that replying to\nyou is a transaction.\n\n## What changes when VoiceMoat is connected\n\nAn ending is the easiest place to slip into somebody else's register, because\nclosing lines are the most copied sentences on both platforms:\n\n- `get_voice_profile` gives the register you actually close in, held separately\n  for LinkedIn and for Twitter, so a LinkedIn sign-off is never judged against\n  how you end a tweet.\n- `score_voice_match` catches the specific failure this skill invites: a strong\n  ending that is strong in the voice of whoever popularised it.\n- `improve_post` runs the whole post again when the ending turns out to be\n  weak because the post never settled what it was for.\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\u002Ffix-my-ending",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fix-my-ending",{"tool":62,"command":63},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fix-my-ending",{"tool":65,"command":66},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fix-my-ending","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fprateeks367\u002Fvoicemoat-skills\u002Fskills\u002Ffix-my-ending\u002FSKILL.md",true,[],[71,81,89,97,105,113],{"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":75,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":80},"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":80},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":80},"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":80},"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":80},"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":80},"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",[],[]]