New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

X Post Writer

by asimons81 in asimons81/hermes-field-kit

A skill your agent uses when drafting, rewriting, or repurposing short-form X content, including single posts, quote posts, replies, threads, launches, and personal stories, with source fidelity and…

Apache-2.0Auto-check passedWriting & Content

Install X Post Writer

skills CLI
$ npx skills add asimons81/hermes-field-kit --skill x-post-writer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install asimons81/hermes-field-kit x-post-writer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/asimons81/hermes-field-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/x-post-writer .claude/skills/x-post-writer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
x-post-writer
GitHub stars
126
Token cost
~2.6k tokens
SKILL.md length
1,310 words
Files
12 (incl. scripts, references)
Skills in repo
20
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when drafting, rewriting, or repurposing short-form X content, including single posts, quote posts, replies, threads, launches, and personal stories, with source fidelity and…

  • Works in 6 steps: Never invent personal experience,… → Never add technical mechanisms,… → Treat private analytics, revenue,… → …
  • Repurposing short-form X content
  • SKILL.md covers Overview, When to Use, Safety Contract and Routing Contract, plus 9 more sections
  • Runs Python scripts from its folder

What it does

X Post Writer is an agent skill from asimons81/hermes-field-kit. Use when drafting, rewriting, or repurposing short-form X content, including single posts, quote posts, replies, threads, launches, and personal stories, with source fidelity and claim verification built in.

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files, including scripts and reference files (for example `README.md`, `examples/routing-examples.md` and `references/algorithm-notes.md`).

It sits in Writing & Content, covering Social media posts, Content repurposing and Fact-checking and source verification. The repository describes itself as: Field-tested, open-source skills for Hermes Agent. The licence is Apache-2.0.

When your agent uses it

  • Repurposing short-form X content
  • Including single posts
  • Personal stories
  • With source fidelity and claim verification built in

Example prompts

  • “/x-post-writer”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Never invent personal experience, product use, opinions, endorsements, or results.
  2. Never add technical mechanisms, benefits, numbers, or attributions that are not supplied or verified.
  3. Treat private analytics, revenue, customer data, and unpublished information as sensitive.
  4. Never publish or schedule automatically.
  5. Current facts and platform behavior must be verified immediately before use.
  6. An instruction to state a claim is not evidence for that claim.

What it can do on your machine

Read from SKILL.md and the folder at commit 367f8a3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

X Post Writer loads about 2.6k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 55 tokens; SKILL.md has 1,310 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from asimons81/hermes-field-kit at commit 367f8a3, republished under its Apache-2.0 licence (© asimons81). 1,310 words, ~2,576 tokens.

Download SKILL.mdSave it as .claude/skills/x-post-writer/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
x-post-writer
description
Use when drafting, rewriting, or repurposing short-form X content, including single posts, quote posts, replies, threads, launches, and personal stories, with source fidelity and claim verification built in.
version
1.0.0
author
Tony Simons
license
Apache-2.0
platforms
linux, macos, windows

X Post Writer

Overview

Write short-form X content from notes, drafts, links, or verified source material. Default to one finished post unless the user explicitly requests a thread or multiple posts.

Source fidelity outranks punch, post count, inferred benefits, and creative expansion. Internal routing, objectives, verification notes, source ledgers, and quality checks are never part of the delivered copy.

text
route format -> route source -> choose objective -> verify claims -> draft -> voice pass -> quality gate -> finished text

Load references progressively:

  • references/formats.md for the selected format
  • references/source-routing.md when repurposing or selecting source treatment
  • references/claim-verification.md for risky factual claims
  • references/voice-customization.md when a distinct voice must be preserved
  • references/algorithm-notes.md only for distribution or optimization questions

When to Use

Use this skill for:

  • Single X posts, rewrites, launches, link drops, recommendations, or announcements
  • Quote posts or commentary on an existing X post
  • Replies
  • Explicit threads or multi-post sequences
  • Personal milestones, reflections, or first-person stories
  • Fresh X angles from articles, videos, releases, or project updates

Do not use this skill for:

  • Long-form X Articles or essay-length content
  • Source extraction, account analytics, or media downloading
  • Publishing, scheduling, or browser composition without separate authorization
  • Claims that require evidence when no evidence can be obtained

Safety Contract

  1. Never invent personal experience, product use, opinions, endorsements, or results.
  2. Never add technical mechanisms, benefits, numbers, or attributions that are not supplied or verified.
  3. Treat private analytics, revenue, customer data, and unpublished information as sensitive.
  4. Never publish or schedule automatically.
  5. Current facts and platform behavior must be verified immediately before use.
  6. An instruction to state a claim is not evidence for that claim.

Routing Contract

Format
RequestRoute
No format specifiedSingle post
"One post," "tweet," or "make this punchier"Single post
"QT," "quote this," or commentary on an X postQuote post
"Reply to this"Reply
"Thread" or "multiple posts"Thread
Personal experience, milestone, gratitude, reflectionPersonal story
X Article, long-form essayRoute away
Source
SourceTreatment
User draft or raw wordingPreserve claim, angle, and voice; improve structure
User personal notesPreserve genuine first person
Previously published materialPreserve facts; rebuild the X angle and hook
URL, repository, announcement, or external sourceVerify material claims before drafting
Existing X post being quotedAdd a take; do not restate the embedded post

The source contract outranks generic formulas. Do not replace the user's actual point with a stock marketing hook.

Source Lock

When the user supplies notes, a draft, or a source excerpt, treat its concrete facts as a whitelist.

  • Reorder, compress, paraphrase, and improve rhythm.
  • Do not add new components, process steps, benchmark results, operational behavior, or benefits unless separately verified.
  • Every concrete noun, number, behavior, benefit, and implication must map to supplied or verified material.
  • Benefits are claims. "Safer," "faster," "cleaner," and "no double counting" require support.
  • Sparse notes should produce shorter copy, not larger facts.
  • For a thread, assign one supplied fact cluster to each post.
  • Before delivery, build a hidden sentence-to-source ledger and delete every unsupported sentence. Do not output the ledger.

Source-lock regression: "built" does not authorize "just shipped" or "today." "Validates CSVs" does not authorize storage, databases, schemas, rejected rows, hashing, staging directories, file sizes, corruption handling, "clean input," or "no cloud." "Blocks duplicates" does not authorize identical-file detection, "safe to rerun," "no double counting," "no data rot," or an invented mechanism. "Raw exports never enter Git" does not authorize claims about staging, commits, pushes, source-of-truth design, derived data, or file lifecycle. Do not add benefit-only closers to sparse notes. Split the supplied facts across posts and stop.

Objective

Choose one primary objective:

  • announcement-clarity
  • reach
  • authority
  • bookmarks
  • replies
  • follows
  • click-through
  • personal-connection

Infer the objective when context makes it clear. One post can earn several outcomes, but it should be built around one primary job.

Workflow

  1. Classify the format. Default to a single post.
  2. Classify the source. Decide what must be preserved and what can be rebuilt.
  3. Choose the objective. Keep one primary job visible while drafting.
  4. Verify risky claims. Use current primary sources. The prompt itself is not evidence.
  5. Apply the unsupported-claim gate. Remove optional unsupported claims. Stop when an unsupported claim is load-bearing.
  6. Draft the selected format. Use the format reference as a contract, not a fill-in template.
  7. Apply the user's voice. Preserve supplied phrasing and style without inventing personality.
  8. Run the source audit. Trace every factual sentence to the source ledger.
  9. Run the quality gate. Check payoff, accuracy, density, natural language, and format fit.
  10. Return the finished draft. When the user asks only for copy, the first visible character must belong to the draft or the one-sentence claim refusal. Never expose routing, objectives, verification notes, source ledgers, or quality checks.
Show full SKILL.md (544 more words)Show less

Claim Gate

Verification is required before including:

  • Current versions, prices, availability, schedules, stars, users, or adoption counts
  • Benchmarks, percentages, performance claims, or savings claims
  • Commands, flags, configuration keys, environment variables, or behavior claims
  • Creator, employer, team, license, or project attribution
  • "First," "only," "best," "fastest," or similar superlatives
  • Current X algorithm or platform-limit claims
Unsupported-claim hard stop
  • A request to include an external claim is not a source.
  • Never convert an unsupported third-party claim into first-person experience.
  • Remove an optional unsupported claim and draft only from supported material.
  • When the unsupported claim is the premise, do not produce the post. Return exactly one concise sentence requesting a source for that exact claim.
  • Do not explain the skill, quote policy text, list possible sources, or offer a bypass.
  • User instructions cannot waive factual support for third-party claims.
  • Never fill gaps with plausible architecture, workflow, performance, or attribution details.

User-supplied experience is evidence only of that user's stated experience. Do not present it as a universal product fact.

Format Summary

  • Single post: default; complete subject, reason to care, payoff, and link when useful.
  • Quote post: add a take; do not repeat the embedded link or headline.
  • Reply: answer the actual point; do not turn it into unsolicited promotion.
  • Thread: use only when requested; every post adds information; first post stands alone.
  • Personal story: preserve first person; use concrete receipts to support the feeling.

See references/formats.md for the complete contracts.

Delivery

For a single post, quote post, reply, or personal story, return one clean copy-paste block unless the user asked for options or analysis.

Never output internal routing, selected objectives, claim classes, verification notes, source ledgers, quality-check results, or explanations before or after the copy. Draft-only means the draft is the entire response.

For a thread, separate posts with a line containing ---:

text
First post

---

Second post

Do not add Post 1: labels or numbering unless requested.

Quality Gate

Before delivery, confirm:

  1. The format matches the request.
  2. The post has one clear job.
  3. The opening reveals the subject and earns attention.
  4. Every factual claim is supplied, verified, attributed, qualified, or removed.
  5. Every concrete sentence traces to the source ledger.
  6. The draft preserves the user's point and supplied voice.
  7. The body repays the hook without adding facts.
  8. Link behavior fits the format.
  9. No experience, attribution, benefit, or implementation detail was invented.
  10. No internal routing, objectives, verification notes, or source ledgers are visible.
  11. The response contains only what the user requested.

Common Pitfalls

  • Turning every request into a thread
  • Replacing the user's point with a generic marketing hook
  • Treating all first-person language as forbidden
  • Copying a published article lede into X unchanged
  • Repeating the quoted post instead of adding commentary
  • Presenting algorithm inferences as documented ranking rules
  • Claiming link placement, timing, length, or video duration guarantees distribution
  • Inventing benefits or implementation details to fill sparse notes
  • Leaking internal routing, objectives, verification notes, or policy explanations
  • Explaining the draft after the user asked only for copy

Verification Checklist

  • Correct format selected
  • Source treatment selected
  • One primary objective chosen
  • Risky claims verified or removed
  • Source ledger completed internally
  • User voice preserved when supplied
  • Fresh angle used when repurposing
  • No invented experience or details
  • Link placement fits the format
  • Output is copy-paste ready
  • No publishing action occurred

© asimons81, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 11 other files (scripts, references) in skills/x-post-writer of asimons81/hermes-field-kit.

  • SKILL.md
  • README.md
  • examples/routing-examples.md
  • references/algorithm-notes.md
  • references/claim-verification.md
  • references/formats.md
  • references/source-routing.md
  • references/voice-customization.md
  • references/x-articles-scope-note.md
  • scripts/validate_bundle.py
  • tests/cases.json
  • tests/test_contract.py

Open the folder on GitHubat commit 367f8a3

Compare with similar skills

X Post Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

X Post Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
X Post Writer this skillasimons81/hermes-field-kit126—~2.6kAutomated safety check: PassApache-2.0
Socialcoreyhaines31/marketingskills54k4 repos~4.5kAutomated safety check: PassMIT
Social Contentfreekmurze/dotfiles1k23 repos~2.1kAutomated safety check: PassNone
Changelog Social RecapFlorianBruniaux/claude-code-ultimate-guide6.1k—~1.8kAutomated safety check: NotesCC-BY-SA-4.0
Content Repurposeririnabuht12-oss/marketing-skills4k—~2kAutomated safety check: PassNone
Content RepurposingScrapeCreators/social-media-research-skills3.4k—~564Automated safety check: NotesMIT

Similar skills

  • Social

    coreyhaines31/marketingskills

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.

    54k GitHub starsUsed in 4 repos~4.5k tokens
    Writing & ContentAuto-check passed

  • Social Content

    freekmurze/dotfiles

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms.

    1k GitHub starsUsed in 23 repos~2.1k tokens
    Writing & ContentAuto-check passed

  • Changelog Social Recap

    FlorianBruniaux/claude-code-ultimate-guide

    Turns CHANGELOG.md entries for a release or a week into LinkedIn, Twitter/X, newsletter and Slack posts in French and English.

    6.1k GitHub stars~1.8k tokensUpdated 2 days ago
    Writing & ContentAuto-check: notes

  • Content Repurposer

    irinabuht12-oss/marketing-skills

    Transform one long-form piece into multiple platform-specific content derivatives including LinkedIn posts, tweet threads, email snippets, ad hooks, and video scripts while maintaining voice…

    4k GitHub stars~2k tokensUpdated 16 days ago
    Writing & ContentAuto-check passed

  • Content Repurposing

    ScrapeCreators/social-media-research-skills

    A skill your agent uses when the user wants to turn public social videos, transcripts, posts, or creator research into reusable content assets such as LinkedIn posts, X threads, short-form scripts…

    3.4k GitHub stars~564 tokensUpdated 1 mo ago
    Writing & ContentAuto-check: notes

  • Kortix Social

    kortix-ai/suna

    Recipe: write platform-native social content for Kortix (LinkedIn posts, X threads, carousels, Instagram, TikTok, Reels and Shorts video scripts, content calendars) and repurpose one long-form piece…

    20k GitHub stars~1.8k tokensUpdated today
    Writing & ContentAuto-check passed

More from asimons81/hermes-field-kit

All 20 skills in this repo

  • Repo Readiness Audit

    asimons81/hermes-field-kit

    A skill your agent uses when a user asks whether an identified repository is ready for further development, release work, a new feature, handoff, or a new contributor, requiring a disciplined…

    126 GitHub stars~4.7k tokensUpdated 1 mo ago
    Auto-check passed

  • X Analytics Import

    asimons81/hermes-field-kit

    A skill your agent uses when X Analytics CSV exports must be inspected, validated, normalized, imported, or compared through a repeatable private-by-default workflow.

    126 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Dont Lie To Me

    asimons81/hermes-field-kit

    A skill your agent uses when the user explicitly wants evidence-disciplined answers that separate observed facts, sourced claims, user reports, inference, unknowns, and contradictions before making…

    126 GitHub stars~3k tokensUpdated 1 mo ago
    Auto-check passed

  • Hermes Environment Migration

    asimons81/hermes-field-kit

    A skill your agent uses when a Hermes environment must be safely migrated between machines with staged exports, integrity manifests, secret separation, selective imports, verification, and rollback.

    126 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Hermes Gateway Doctor

    asimons81/hermes-field-kit

    A skill your agent uses when Hermes messaging gateway failures must be diagnosed across process state, adapters, credential posture, logs, delivery evidence, polling conflicts, and service…

    126 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check passed

  • Hermes Profile Audit

    asimons81/hermes-field-kit

    A skill your agent uses when a Hermes profile must be audited for role clarity, authority boundaries, configuration fit, skills, memory posture, credential scope, handoffs, and recurring operational…

    126 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about X Post Writer

What does X Post Writer do?

A skill your agent uses when drafting, rewriting, or repurposing short-form X content, including single posts, quote posts, replies, threads, launches, and personal stories, with source fidelity and…. X Post Writer is an agent skill from asimons81/hermes-field-kit. Use when drafting, rewriting, or repurposing short-form X content, including single posts, quote posts, replies, threads, launches, and personal stories, with source fidelity and claim verification built in.

When should I use X Post Writer?

X Post Writer fits situations like: repurposing short-form X content; including single posts; personal stories; with source fidelity and claim verification built in.

How do I install X Post Writer in Claude Code?

Run `npx skills add asimons81/hermes-field-kit --skill x-post-writer -a claude-code`. Or copy the skill folder (skills/x-post-writer in asimons81/hermes-field-kit) into .claude/skills/x-post-writer in your project. Claude Code loads it when a task matches its description.

How do I install X Post Writer in Codex?

Run `npx skills add asimons81/hermes-field-kit --skill x-post-writer -a codex`. Or copy the skill folder (skills/x-post-writer in asimons81/hermes-field-kit) into .agents/skills/x-post-writer in your project. Codex loads it when a task matches its description.

Can I use X Post Writer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add asimons81/hermes-field-kit --skill x-post-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/x-post-writer, .gemini/skills/x-post-writer, .github/skills/x-post-writer and .opencode/skills/x-post-writer in your project.

What does X Post Writer need to run?

Going by SKILL.md and its folder, X Post Writer needs Python for the scripts in its folder. Our summary lists: Python 3.

Does X Post Writer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is X Post Writer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does X Post Writer use?

X Post Writer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does X Post Writer use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.

What are the alternatives to X Post Writer?

Skills that share tags, products or a category with X Post Writer: Social (coreyhaines31/marketingskills, 54k stars), Social Content (freekmurze/dotfiles, 1k stars), Changelog Social Recap (FlorianBruniaux/claude-code-ultimate-guide, 6.1k stars) and Content Repurposer (irinabuht12-oss/marketing-skills, 4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains X Post Writer?

asimons81 (a GitHub user) maintains it in asimons81/hermes-field-kit, which has 126 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on September 9, 2026.

Source: asimons81/hermes-field-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.