agentsclimarketplace
Sign in

Postking brand voice

Skill bitsandtea/postking-skills/skills/postking-brand-voice

List and apply saved PostKing voice profiles when generating or rewriting content, and run the de-slop / humanize / AI-detection pass on any text.From its SKILL.md

Install
npx -y skills add bitsandtea/postking-skills --skill postking-brand-voice

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 2 commands, including `pking voice list` and 1 more.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

5.0 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

Brand Voice & Quality

Keep generated and rewritten content on-brand and human-sounding — list saved voice profiles, apply one to a generation or rewrite, and run a de-slop / AI-detection pass before it ships.

Voice-profile creation is web-only. Building a new voice profile (from a writing sample, imported social posts, or a deep voice for a key author) happens in the PostKing dashboard's voice-profiles page — there is no MCP tool to create, extract, or import a voice. This skill covers what comes after: listing an existing profile and applying it.

When to Use

Use this skill when a user wants existing content rewritten in a specific saved brand voice, wants a voiceId to pass into another skill's generation call, or wants a de-slop/AI-detection pass to make text read as human before it ships.

When NOT to Use

Not for creating a new voice profile — that's web-only, done in the PostKing dashboard. Not for generating original content from scratch — that's postking-social/postking, postking-seo, postking-storylines, or postking-reddit, each of which accepts a voiceId from this skill as a parameter.

Minimal tool subset

This skill needs only these 5 tools out of PostKing's 200+:

  • list_voices — list saved voice profiles with their IDs.
  • rewrite_with_voice — rewrite arbitrary text in a specific saved voice.
  • rewrite_text — general rewrite, optionally applying a voice profile.
  • humanize_text — de-slop pass: rewrites and swaps AI-tell words/phrases to reduce AI-detection signals.
  • check_ai_content — score how AI-detectable a piece of text reads.

Prerequisites

  1. Authenticated with credits — see the postking-getting-started skill.
  2. A brand already onboarded — see the postking-getting-started skill.

Voices get applied downstream in the postking skill (posts, blogs, landing pages, repurposing), the postking-seo skill (article writing), and the postking-storylines skill (campaign drafts).

Procedure

"Rewrite this in our brand voice and make sure it doesn't read as AI-written."

  1. Build a voice (dashboard only, one-time). If no voice profile exists yet, tell the user to build one in the PostKing dashboard's voice-profiles page (from a writing sample, imported social posts, or a deep author voice) — there is no MCP tool for this step.
  2. List voices. list_voices({}) — get the profileId for the voice to use.
  3. Apply at generation time (preferred). Pass that voice id as the voice/voiceProfileId param directly on generate_post, generate_blog_post, generate_landing_page, repurpose_content, or reddit_rewrite — no separate rewrite pass needed. These tools live in the postking, postking-seo, postking-storylines, and postking-reddit skills.
  4. Apply to existing text. rewrite_with_voice({ profileId, text, platform }) — or rewrite_text({ text, voice: profileId, platform }) for a lighter-touch pass.
  5. De-slop / humanize. humanize_text({ text, platform }) — strips AI-tell words and clichés and reduces AI-detection signals. Run this after voice rewriting, right before the text ships.
  6. Score it. check_ai_content({ text }) — returns an AI-detection score + analysis. If the score is poor, re-run humanize_text and check again.

CLI fast path

pking voice list lists saved voices (equivalent to list_voices). Beyond that, the MCP path above is primary — do not assume additional pking flags exist for rewrite/humanize without checking pking --help first.

Expected Output

Content rewritten in a chosen brand voice, then de-slopped for lower AI-detection signal, with a check_ai_content score confirming the result reads as human.

Pitfalls

  • list_voices returns empty — no voice profile exists yet; build one in the PostKing dashboard (creation is web-only, not available via MCP).
  • INSUFFICIENT_CREDITS — surface the checkoutUrl from the error envelope and stop, or hand off to the postking-getting-started skill's billing section (billing_list_packs → billing_topup).
  • RATE_LIMITED — back off using the retryAfter value from the error envelope before retrying.
  • UNAUTHORIZED — re-run the login flow described in the postking-getting-started skill.

Verification

  • list_voices({}) should return successfully; a non-empty result confirms at least one profile exists to reference.
  • After humanize_text, check_ai_content({ text }) on the result should return an improved (lower AI-likelihood) score than the original.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most marketing audience skills give in ~1.1k tokens

Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07

  • Apply Poppins font to headingsin 41 of 690, across 6 files
  • Apply Lora font to body textin 41 of 690, across 6 files
  • Use Arial fallback for headingsin 39 of 690, across 4 files
  • Use Georgia fallback for body textin 39 of 690, across 4 files
  • Maintain text hierarchy and formattingin 39 of 690, across 4 files
  • Use accent colors for non-text shapesin 38 of 690, across 3 files
  • Use RGB values for precise color matchingin 38 of 690, across 3 files
  • Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
  • Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
  • Use active voice instead of passive voicein 26 of 690, across 10 files
  • Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
  • Prioritize clarity over clevernessin 22 of 690, across 8 files

Said here and by no other author read

  • back off using retryAfter value when rate limited
  • list saved voice profiles to get profile id
  • apply voice at generation time if possible
  • use rewrite_with_voice for existing text
  • use rewrite_text for lighter-touch rewrites
  • run humanize_text right before text ships

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.