[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MKSWRTD6Q5ZGAF71SMHZ43":3,"skill-same:01M6MKSWRTD6Q5ZGAF71SMHZ43":69},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6MKSWRTD6Q5ZGAF71SMHZ43","audit-before-i-publish",null,"Run a finished draft through one pre-publish pass and rank what to fix. Use when someone says a post is ready, asks for a final check, asks whether to post something as it stands, or pastes a draft and asks what is wrong with it. Do not use it to write a post from nothing, do not rewrite a whole draft when one line is the problem, and do not predict performance.","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\u002Faudit-before-i-publish\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"audit","publish","audit before i publish","draft","when","predict","for","with","post","problem","rewrite","line","as","performance","do","ready","use","fix","write","check","run","2026-11-10 10:12:30",false,"---\nname: audit-before-i-publish\ndescription: Run a finished draft through one pre-publish pass and rank what to fix. Use when someone says a post is ready, asks for a final check, asks whether to post something as it stands, or pastes a draft and asks what is wrong with it. Do not use it to write a post from nothing, do not rewrite a whole draft when one line is the problem, and do not predict performance.\n---\n\n# Audit it before I publish\n\nEditing makes a draft better. An audit decides whether it is ready, which is a\ndifferent question with a different answer. Most drafts that get stuck do not\nneed another pass of polish. They need one specific thing fixed, and the job\nhere is to find which one and then stop. Work the steps in order.\n\n## Step 1: read it in the order a reader meets it\n\nThe author already knows what the post says, so they read it as a whole. Nobody\nelse does.\n\n- **The first line on its own**, everything else hidden. Does it make the second\n  line necessary? If the honest answer is \"it sets up the post\", that is a no.\n- **Whatever sits above the fold.** LinkedIn hides most of a post behind \"see\n  more\". Everything above that cut is the advert for the rest, so judge it as\n  an advert rather than as an introduction.\n\n## Step 2: check the claim before you check the craft\n\nThis comes first because it is the only failure that is expensive. A dull post\ncosts you one day. A wrong one costs you the reason people read you.\n\n- **Every number.** Can it be sourced, and would you be happy to name that\n  source in the comments? A figure everyone repeats is not a figure anyone\n  checked. If it will not hold, cut it or attribute it.\n- **Every story.** Is it yours, and did it happen the way it is written? A\n  secondhand anecdote told in the first person loses everyone who recognises it.\n- **The promise.** Does the opening commit to something the body delivers? A\n  hook the post does not pay off costs more than a flat hook, because the\n  reader who felt the gap does not come back.\n- **Anyone identifiable.** A colleague, a client, a number from inside a\n  company. Did they agree to be in it?\n\n## Step 3: check the shape\n\n- **One idea.** If there are two, the second is next week's post, not a\n  paragraph. Name it and take it out.\n- **The line breaks.** A wall of text loses readers who would have read the\n  same words with air around them.\n- **The length.** Long is fine when every paragraph earns its place, so never\n  say \"this is too long\". Say which paragraph is carrying nothing.\n\n## Step 4: check the ending, and be willing to leave it alone\n\nMost posts end by asking a question nobody answers. Name which ending this one\nhas before suggesting anything:\n\n- A real question the reader already has an opinion about\n- A generic prompt, the \"thoughts?\" ending, which reads as asking a favour\n- A summary that repeats what they just read\n- Nothing at all, which is more often right than people expect\n\nOnly propose a change when the current ending is actually costing something.\n\"Add a call to action\" is advice, not a diagnosis.\n\n## Step 5: check it still sounds like the person who wrote it\n\nRead it back for the tells: hedging that was not in the first draft, sentences\nall drifted to the same length, vocabulary this person does not use. Point at\nthe lines. \"It sounds a bit AI\" is not usable.\n\n## Step 6: rank, then stop\n\nGive at most three fixes, ordered by what they cost, and say which checks came\nback clean. Then say plainly whether you would post it as it stands, and be\nwilling to answer yes. An audit that always finds three problems is a habit,\nnot an audit.\n\n## What this will not do\n\nIt will not tell you whether the post will perform. Reach depends on timing,\naudience, format and luck as much as on the words, and a checklist implying\notherwise would be selling something.\n\nIt also will not give you a number. Reading a draft against five posts you\npasted is a read-through, not a measurement, and a score out of 100 would claim\na precision it does not have.\n\n## What changes when VoiceMoat is connected\n\nSteps 1 to 4 are craft, and craft is the same for everybody. Step 5 is the one\nthat needs to know you, and on its own it is guessing:\n\n- `get_voice_profile` returns a profile trained on your own published posts, held separately for LinkedIn and for Twitter, rather than a sketch\n  built from whatever you happened to paste.\n- `score_voice_match` checks the draft against that profile in two parts:\n  Style, how many of your measurable habits it matches (N of M checks), and\n  Stance, whether what it says fits your views (On voice, Check one line or\n  Off voice), with the lines that are off. The assistant may show it as a\n  card. This is the step the free version structurally cannot do, so it is\n  where the audit stops being an opinion.\n- `improve_post` takes the draft through a deeper pass on the occasions when\n  step 6 turns up three real fixes rather than one.\n- `publish_post` sends it once you are happy, behind a preview and a one-time\n  confirmation.\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","# Audit it before I publish\n\nEditing makes a draft better. An audit decides whether it is ready, which is a\ndifferent question with a different answer. Most drafts that get stuck do not\nneed another pass of polish. They need one specific thing fixed, and the job\nhere is to find which one and then stop. Work the steps in order.\n\n## Step 1: read it in the order a reader meets it\n\nThe author already knows what the post says, so they read it as a whole. Nobody\nelse does.\n\n- **The first line on its own**, everything else hidden. Does it make the second\n  line necessary? If the honest answer is \"it sets up the post\", that is a no.\n- **Whatever sits above the fold.** LinkedIn hides most of a post behind \"see\n  more\". Everything above that cut is the advert for the rest, so judge it as\n  an advert rather than as an introduction.\n\n## Step 2: check the claim before you check the craft\n\nThis comes first because it is the only failure that is expensive. A dull post\ncosts you one day. A wrong one costs you the reason people read you.\n\n- **Every number.** Can it be sourced, and would you be happy to name that\n  source in the comments? A figure everyone repeats is not a figure anyone\n  checked. If it will not hold, cut it or attribute it.\n- **Every story.** Is it yours, and did it happen the way it is written? A\n  secondhand anecdote told in the first person loses everyone who recognises it.\n- **The promise.** Does the opening commit to something the body delivers? A\n  hook the post does not pay off costs more than a flat hook, because the\n  reader who felt the gap does not come back.\n- **Anyone identifiable.** A colleague, a client, a number from inside a\n  company. Did they agree to be in it?\n\n## Step 3: check the shape\n\n- **One idea.** If there are two, the second is next week's post, not a\n  paragraph. Name it and take it out.\n- **The line breaks.** A wall of text loses readers who would have read the\n  same words with air around them.\n- **The length.** Long is fine when every paragraph earns its place, so never\n  say \"this is too long\". Say which paragraph is carrying nothing.\n\n## Step 4: check the ending, and be willing to leave it alone\n\nMost posts end by asking a question nobody answers. Name which ending this one\nhas before suggesting anything:\n\n- A real question the reader already has an opinion about\n- A generic prompt, the \"thoughts?\" ending, which reads as asking a favour\n- A summary that repeats what they just read\n- Nothing at all, which is more often right than people expect\n\nOnly propose a change when the current ending is actually costing something.\n\"Add a call to action\" is advice, not a diagnosis.\n\n## Step 5: check it still sounds like the person who wrote it\n\nRead it back for the tells: hedging that was not in the first draft, sentences\nall drifted to the same length, vocabulary this person does not use. Point at\nthe lines. \"It sounds a bit AI\" is not usable.\n\n## Step 6: rank, then stop\n\nGive at most three fixes, ordered by what they cost, and say which checks came\nback clean. Then say plainly whether you would post it as it stands, and be\nwilling to answer yes. An audit that always finds three problems is a habit,\nnot an audit.\n\n## What this will not do\n\nIt will not tell you whether the post will perform. Reach depends on timing,\naudience, format and luck as much as on the words, and a checklist implying\notherwise would be selling something.\n\nIt also will not give you a number. Reading a draft against five posts you\npasted is a read-through, not a measurement, and a score out of 100 would claim\na precision it does not have.\n\n## What changes when VoiceMoat is connected\n\nSteps 1 to 4 are craft, and craft is the same for everybody. Step 5 is the one\nthat needs to know you, and on its own it is guessing:\n\n- `get_voice_profile` returns a profile trained on your own published posts, held separately for LinkedIn and for Twitter, rather than a sketch\n  built from whatever you happened to paste.\n- `score_voice_match` checks the draft against that profile in two parts:\n  Style, how many of your measurable habits it matches (N of M checks), and\n  Stance, whether what it says fits your views (On voice, Check one line or\n  Off voice), with the lines that are off. The assistant may show it as a\n  card. This is the step the free version structurally cannot do, so it is\n  where the audit stops being an opinion.\n- `improve_post` takes the draft through a deeper pass on the occasions when\n  step 6 turns up three real fixes rather than one.\n- `publish_post` sends it once you are happy, behind a preview and a one-time\n  confirmation.\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\u002Faudit-before-i-publish",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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill audit-before-i-publish",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill audit-before-i-publish",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill audit-before-i-publish","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fprateeks367\u002Fvoicemoat-skills\u002Fskills\u002Faudit-before-i-publish\u002FSKILL.md",true,[],[70,80,88,96,104,112],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":79},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":79},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":79},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":79},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":79},"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":79},"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",[],[]]