tweet-draft-reviewer
by BrianRWagnertweet-draft-reviewer reviews tweet drafts in Claude Code with 8 voice rules, scores them 1-10, explains the result, and rewrites weak drafts below 7. Use it for fast tweet-draft-reviewer for Social Media checks, tighter feedback, and clearer tweet-draft-reviewer guide workflows.
This skill scores 78/100, which means it is a solid directory listing candidate with good practical value for users who want a structured tweet-draft review workflow. Directory users should see enough detail to understand how to trigger it, what it returns, and when it is most useful, though it is still somewhat narrow and would benefit from more adoption guidance.
- Clear triggerability: the SKILL.md gives explicit prompts for single-draft review and batch folder scanning.
- Strong operational clarity: it specifies a phased workflow, including intake modes and a concrete bash command for folder review.
- Good agent leverage: it returns a score, rule-by-rule breakdown, and rewrite guidance when drafts score below 7.
- Narrow fit: it is specialized for tweet drafts and may not generalize beyond short-form social content.
- Limited supporting assets: there are no scripts, references, resources, or install command, so users only have SKILL.md guidance to evaluate.
Overview of tweet-draft-reviewer skill
What tweet-draft-reviewer does
The tweet-draft-reviewer skill reviews a tweet draft in Claude Code, scores it from 1–10, explains the score against 8 voice rules, and rewrites weak drafts that score below 7. It is designed for fast editorial feedback on short-form social copy, not broad marketing strategy.
Who it is for
Use the tweet-draft-reviewer skill if you write tweets regularly, manage a social content workflow, or want a consistent quality check before posting. It is especially useful for creators and teams who need a repeatable review pass for tweet-draft-reviewer for Social Media content rather than a generic “make this better” prompt.
Why it is different
The main value is structure: a clear score, rule-by-rule diagnosis, and an automatic rewrite path when the draft underperforms. That makes tweet-draft-reviewer more decision-friendly than a freeform prompt because you can see whether the issue is clarity, tone, engagement, or voice fit.
How to Use tweet-draft-reviewer skill
Install and invoke
Install with:
npx skills add BrianRWagner/ai-marketing-skills --skill tweet-draft-reviewer
Then invoke it with either a pasted draft or a folder scan request. For a single post, use a direct prompt such as: Review this tweet draft: [paste tweet here]. For a batch workflow, point it at your drafts folder so the skill can locate unreviewed files.
Give it the right input
The skill works best when the draft is complete enough to judge voice and intent. Include the actual tweet text, not just a topic, and add any constraints that matter: audience, objective, product angle, or whether the post should sound personal, authoritative, or playful. A stronger tweet-draft-reviewer usage prompt looks like: Review this tweet draft for founders. Keep the tone sharp, avoid hype, and preserve the CTA.
Read the repo in the right order
Start with SKILL.md because it contains the actual operating instructions and intake flow. If you want to adapt the skill to your own system, inspect the sections around how it handles direct paste vs. folder review, then read any adjacent documentation in the repo for naming and workflow conventions. Since this repo has no helper files, the main value is understanding the exact review logic, not chasing extra assets.
Workflow tips that improve output
Use tweet-draft-reviewer on drafts that are close to publish-ready. If the draft is too rough, the score will be less useful because the rewrite may fix fundamentals instead of polishing voice. For best results, ask for one of two modes up front: a strict review for quality control, or a rewrite-focused pass when you want the skill to salvage a weak draft.
tweet-draft-reviewer skill FAQ
Is tweet-draft-reviewer only for Claude Code?
The repository is written as a Claude Code skill, so that is the most reliable environment for tweet-draft-reviewer. You can still use the underlying review logic as a prompt pattern elsewhere, but the install and intake behavior are designed around the skill format.
Is this better than a normal prompt?
Yes, if you want consistency. A normal prompt can review a tweet, but tweet-draft-reviewer gives you a repeatable score, named criteria, and a built-in rewrite threshold. That makes it easier to compare drafts over time and spot what keeps failing.
Is it beginner-friendly?
Yes, because the basic path is simple: paste a draft and ask for a review. The only real friction is knowing whether you want single-draft feedback or a folder scan. If you can provide the text and a clear goal, the skill is easy to use.
When should I not use it?
Do not use tweet-draft-reviewer if you need long-form strategy, campaign planning, or multi-channel content repurposing. It is optimized for short tweet review, so it is a poor fit when the main problem is messaging architecture rather than post-level quality.
How to Improve tweet-draft-reviewer skill
Start with a more specific draft brief
The biggest improvement comes from telling the skill what the tweet is supposed to achieve. Add audience, intent, and tone in the same request: Review this tweet draft for B2B SaaS founders. Goal: drive profile clicks. Tone: confident, not salesy. That gives tweet-draft-reviewer a better baseline for judging whether the voice actually fits.
Fix the usual failure modes
The most common weak inputs are vague topic lines, unfinished threads, and drafts with no discernible point of view. Those usually produce generic feedback. If the draft needs a strong stance, a concrete hook, or a clearer CTA, include that expectation so the review can score the right thing instead of optimizing the wrong dimension.
Iterate after the first review
Treat the first score as a diagnosis, then rerun the skill on your revised draft. If the rewrite feels too flat, ask for a stricter tone, tighter length, or a more opinionated angle. If you use tweet-draft-reviewer guide style iteration, you usually get better results by changing one variable at a time instead of asking for a total reset.
Use the rewrite as a test, not a final answer
When the skill rewrites a draft below 7, compare the rewrite against your original voice and audience goal. The best next step is often to merge the rewrite’s structure with your own phrasing. That keeps tweet-draft-reviewer useful as an editorial filter without making every post sound uniform.