marketing-x-content/SKILL.md
Use when writing X/Twitter posts, threads, or long-form articles from an idea, news item, article URL, or topic the user provides. Produces 2-3 variations with different hooks and formats for direct copy-paste into X.
npx skillsauth add paulund/ai marketing-x-contentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
references/x-style-guide.md before writing anything.writing plugin is available, run humanizer on each draft to strip AI patterns.Choose 2-3 of these for each piece of content:
When writing a thread (3-5 posts):
Keep threads to 3-5 posts. If the topic needs more, consider a long-form article instead.
Before presenting any draft, verify:
-) for lists, not bullet dots, no markdown that X cannot render| Topic | Reference | Load When |
| ----- | --------- | --------- |
| X Post Style | references/x-style-guide.md | Always — before writing any post or thread |
-) for any lists inside postswriting:humanizer on every draft if the writing plugin is availabledevelopment
Use when implementing any logic, fixing any bug, or changing any behaviour. Use when you need to prove code works, when a bug report arrives, or when modifying existing functionality. Do NOT use for config changes, data migrations, or dependency updates.
development
Use when starting a new feature, when requirements are unclear, when asked to write code without a clear spec, or before any non-trivial implementation. Do NOT use for trivial bug fixes or one-line changes.
development
Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters. Detects the stack from dependency files, fetches official documentation, implements following documented patterns, and cites sources for every framework-specific decision.
development
Use when preparing to ship a feature, release, or deployment. Use before merging to main, creating a release, or deploying to production. Do NOT use for CI-only changes or internal refactors that don't reach production.