[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MKVVQ5BF3MS0MC43RBT4W5":3,"skill-same:01M6MKVVQ5BF3MS0MC43RBT4W5":72},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6MKVVQ5BF3MS0MC43RBT4W5","get-my-team-posting",null,"Turn one company message into posts each colleague can publish in their own words, instead of six people posting the same paragraph. Use when a company wants employees posting, a launch needs internal support, or a team was handed copy to share. Do not write one post for everyone to paste, do not write in a voice they would not recognise, and never ask anyone to post what they disagree with.","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\u002Fget-my-team-posting\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"get my team posting","team","my","get","posting","post","when","company","for","can","paste","employees","posts","with","people","support","message","do","never","use","write","ask","publish","share","2026-11-10 10:12:30",false,"---\nname: get-my-team-posting\ndescription: Turn one company message into posts each colleague can publish in their own words, instead of six people posting the same paragraph. Use when a company wants employees posting, a launch needs internal support, or a team was handed copy to share. Do not write one post for everyone to paste, do not write in a voice they would not recognise, and never ask anyone to post what they disagree with.\n---\n\n# Get my team posting\n\nEmployee advocacy fails the same way every time. One person writes a good post,\nsends it to twelve colleagues, and by eleven in the morning the feed shows\ntwelve identical paragraphs with the same line breaks.\n\nEveryone can see what happened. The company has spent twelve people's\ncredibility to say one thing once, and the thing it actually communicated is\nthat none of them meant it.\n\n## Step 1: separate the message from the posts\n\nThe message is one sentence everybody agrees is true. That is the only part\nthat should be identical.\n\nThe posts are twelve different things. Write the message down first, on its\nown, and get agreement on it before anyone drafts anything.\n\n## Step 2: give each person their own angle\n\nAsk every person what they actually did or saw. Same message, different\nevidence:\n\n- The engineer who built the part that was hard\n- The person who took the support calls that led to it\n- The person who argued against it and changed their mind\n- The person who joined halfway and saw it with fresh eyes\n- The person who has to sell it and knows the objection\n\nSomebody who cannot answer this should not be posting about it. That is a\nperfectly good outcome and it is better than another paraphrase.\n\n## Step 3: write in their words, not the brand's\n\nAsk each person for two things they have already written. A Slack message is\nfine. An email is fine. Match that.\n\nThe brand voice is for the company account. A person posting in brand voice\nreads as the company using their face, which is the thing advocacy was supposed\nto avoid.\n\n## Step 4: stagger it\n\nSame message, same morning, same feed is the tell regardless of how different\nthe wording is. Spread it across days, and let people post at the time they\nnormally post.\n\n## Step 5: let them say no, and let them disagree\n\nA post somebody was told to publish reads like one. Make declining normal and\nsay so out loud, because people will assume otherwise.\n\nThe strongest advocacy posts usually contain something mildly inconvenient: the\nthing that took longer than expected, the feature that is not ready, the\ncustomer who pushed back. Allowing that is what makes the rest believable.\n\n## Step 6: what not to ask for\n\n- Do not organise a block of colleagues to comment on each other's posts. It is\n  visible, and it reads exactly as what it is.\n- Do not hand out a hashtag list.\n- Do not supply a link to paste in the first line without checking what the\n  company's own posting guidance says about links.\n- Do not ask anyone to post about a customer, a number or a roadmap item that\n  has not been cleared. Flag those and stop.\n\n## What this will not do\n\nIt will not write the same post twelve ways. If the only difference between\ntwelve drafts is word order, the answer is fewer posts, not more paraphrases.\n\nIt will not ghostwrite in a voice the person has not seen and approved. Every\ndraft goes to the person named on it before it goes anywhere else.\n\n## What changes when VoiceMoat is connected\n\nAdvocacy is a multi-person problem, which is the case a single voice profile\ncannot serve:\n\n- `list_profiles` returns the accounts on the team, so each draft is written\n  against the right person rather than against a house style.\n- `get_voice_profile` gives that person's own trained profile, which is the\n  difference between a post in their words and a post with their name on it.\n- `score_voice_match` scores each draft against its own author, so twelve posts\n  can be checked for sounding like twelve people rather than one.\n\nTeam seats are on the Enterprise plan.\n\nVoiceMoat is at voicemoat.com. The connector needs the Pro or Enterprise plan.\n","# Get my team posting\n\nEmployee advocacy fails the same way every time. One person writes a good post,\nsends it to twelve colleagues, and by eleven in the morning the feed shows\ntwelve identical paragraphs with the same line breaks.\n\nEveryone can see what happened. The company has spent twelve people's\ncredibility to say one thing once, and the thing it actually communicated is\nthat none of them meant it.\n\n## Step 1: separate the message from the posts\n\nThe message is one sentence everybody agrees is true. That is the only part\nthat should be identical.\n\nThe posts are twelve different things. Write the message down first, on its\nown, and get agreement on it before anyone drafts anything.\n\n## Step 2: give each person their own angle\n\nAsk every person what they actually did or saw. Same message, different\nevidence:\n\n- The engineer who built the part that was hard\n- The person who took the support calls that led to it\n- The person who argued against it and changed their mind\n- The person who joined halfway and saw it with fresh eyes\n- The person who has to sell it and knows the objection\n\nSomebody who cannot answer this should not be posting about it. That is a\nperfectly good outcome and it is better than another paraphrase.\n\n## Step 3: write in their words, not the brand's\n\nAsk each person for two things they have already written. A Slack message is\nfine. An email is fine. Match that.\n\nThe brand voice is for the company account. A person posting in brand voice\nreads as the company using their face, which is the thing advocacy was supposed\nto avoid.\n\n## Step 4: stagger it\n\nSame message, same morning, same feed is the tell regardless of how different\nthe wording is. Spread it across days, and let people post at the time they\nnormally post.\n\n## Step 5: let them say no, and let them disagree\n\nA post somebody was told to publish reads like one. Make declining normal and\nsay so out loud, because people will assume otherwise.\n\nThe strongest advocacy posts usually contain something mildly inconvenient: the\nthing that took longer than expected, the feature that is not ready, the\ncustomer who pushed back. Allowing that is what makes the rest believable.\n\n## Step 6: what not to ask for\n\n- Do not organise a block of colleagues to comment on each other's posts. It is\n  visible, and it reads exactly as what it is.\n- Do not hand out a hashtag list.\n- Do not supply a link to paste in the first line without checking what the\n  company's own posting guidance says about links.\n- Do not ask anyone to post about a customer, a number or a roadmap item that\n  has not been cleared. Flag those and stop.\n\n## What this will not do\n\nIt will not write the same post twelve ways. If the only difference between\ntwelve drafts is word order, the answer is fewer posts, not more paraphrases.\n\nIt will not ghostwrite in a voice the person has not seen and approved. Every\ndraft goes to the person named on it before it goes anywhere else.\n\n## What changes when VoiceMoat is connected\n\nAdvocacy is a multi-person problem, which is the case a single voice profile\ncannot serve:\n\n- `list_profiles` returns the accounts on the team, so each draft is written\n  against the right person rather than against a house style.\n- `get_voice_profile` gives that person's own trained profile, which is the\n  difference between a post in their words and a post with their name on it.\n- `score_voice_match` scores each draft against its own author, so twelve posts\n  can be checked for sounding like twelve people rather than one.\n\nTeam seats are on the Enterprise plan.\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\u002Fget-my-team-posting",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill get-my-team-posting",{"tool":64,"command":65},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill get-my-team-posting",{"tool":67,"command":68},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill get-my-team-posting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fprateeks367\u002Fvoicemoat-skills\u002Fskills\u002Fget-my-team-posting\u002FSKILL.md",true,[],[73,83,91,99,107,115],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":82},"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":82},"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":82},"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":82},"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":82},"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":82},"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",[],[]]