- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add BrianRWagner/ai-marketing-claude-code-skills --skill tweet-draft-reviewer -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add BrianRWagner/ai-marketing-claude-code-skills --skill tweet-draft-reviewer -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add BrianRWagner/ai-marketing-claude-code-skills --skill tweet-draft-reviewer -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add BrianRWagner/ai-marketing-claude-code-skills --skill tweet-draft-reviewer -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/BrianRWagner/ai-marketing-claude-code-skills/tree/HEAD/tweet-draft-reviewer게시자 제공
Paste a tweet draft and get a score out of 10, a rule-by-rule breakdown, and a rewrite if the score is below 7. Takes 30 seconds. Saves you from posting something that sounds like a chatbot wrote it.
Built on 8 voice rules distilled from real content analysis — what separates high-engagement tweets from the ones that get skimmed.
Detect from context or ask: "Just a score, full review, or full review with alternate versions?"
Default: standard. Use quick if they say "just score it." Use deep for folder scans or when they ask for options.
Single draft:
Review this tweet draft: [paste tweet here]
Batch scan:
Review all tweet drafts in my content/tweet-drafts/ folder.
When this skill is invoked, follow these phases exactly.
Determine the input type:
Input A — Direct paste: User provided draft text inline. Proceed to PHASE 2 with that text.
Input B — Folder scan: User asked to review drafts folder. Run:
VAULT="${VAULT_PATH:-$(pwd)}"
find "$VAULT/content/tweet-drafts" -name "*.md" 2>/dev/null | while read f; do
if ! grep -q 'reviewed: true' "$f" 2>/dev/null; then
echo "UNREVIEWED:$f"
fi
done
If no vault path was given and no content/tweet-drafts/ exists in the current directory, ask:
Where is your tweet drafts folder? (full path, e.g. $HOME/vault/content/tweet-drafts)
Mode C — Ambiguous: No draft provided and no folder context. Ask:
Paste your tweet draft here, or tell me the path to your tweet-drafts folder and I'll scan it.
Apply all 8 rules to the draft. For each rule, record ✅ PASS or ❌ FAIL with a one-line reason.
Rule 1: No "I" opener
I (standalone — not "In", "It", "If")Rule 2: Strong opener
? OR starts with "Have you", "Do you", "Are you", "What if", "What would"Rule 3: No AI tells
delve, certainly, game-changing, game changer, it's worth noting, invaluable, unleash, revolutionize, transformativeRule 4: No generic closers
what do you think, drop a comment, thoughts?, let me know in the comments, agree?, sound familiar?Rule 5: Corey Test (specificity)
Rule 6: Character count
Rule 7: Single point
Rule 8: Punchy rhythm
Print this exact format:
TWEET REVIEW
────────────
Score: X/10
Rule-by-Rule:
1. ✅/❌ No "I" opener — [reason]
2. ✅/❌ Strong opener — [reason]
3. ✅/❌ No AI tells — [reason]
4. ✅/❌ No generic closers — [reason]
5. ✅/❌ Corey Test — [reason]
6. ✅/❌ Character count — [reason + actual count]
7. ✅/❌ Single point — [reason]
8. ✅/❌ Punchy rhythm — [reason]
────────────
Scoring table (passes → score):
If score ≥ 7:
→ Ready to post. Use Typefully or your scheduler to queue it.
If score < 7 — add a rewrite:
Suggested Rewrite:
[rewritten tweet that fixes all failing rules]
Before delivering the output, check:
Fix anything that fails before delivering.
Input:
I've been thinking a lot about how AI is really changing the way founders
approach content creation and productivity, and I think it's worth noting
that the teams who figure out async AI workflows are going to have a
massive advantage. What do you think about this?
Output:
TWEET REVIEW
────────────
Score: 2/10
Rule-by-Rule:
1. ❌ No "I" opener — Starts with "I've"
2. ❌ Strong opener — Slow setup, no hook, no specific fact
3. ❌ No AI tells — Contains "it's worth noting"
4. ❌ No generic closers — Ends with "What do you think about this?"
5. ❌ Corey Test — "massive advantage" is vague, no numbers or concrete outcome
6. ✅ Character count — 248 chars
7. ✅ Single point — Focused on async AI workflows
8. ❌ Punchy rhythm — Run-on sentence, preamble opener
────────────
Suggested Rewrite:
The founders winning right now aren't working harder.
They have agents running at 2am. Content drafted. Research done.
Queue processed.
By 7am they're reviewing output, not creating it.
Async AI ops is the new early morning routine.
When scanning a folder, output one review block per file:
📄 content/tweet-drafts/linkedin-ai-post.md
[full review block]
📄 content/tweet-drafts/founder-ops.md
[full review block]
────────────
BATCH SUMMARY
Reviewed: 4 drafts
Ready to post (≥7): 2
Need rewrite (<7): 2
content/tweet-drafts/ (optional — direct paste always works)reviewed: true to skip them in future scansReview tweet drafts in Claude Code against 8 voice rules. Scores 1-10, breaks down every rule, and rewrites anything that scores below 7.
---name: tweet-draft-reviewerdescription: Review tweet drafts in Claude Code against 8 voice rules. Scores 1-10, breaks down every rule, and rewrites…---# tweet-draft-reviewer/SKILL.mdFAQ
게시자에게서 tweet-draft-reviewer/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/BrianRWagner/ai-marketing-claude-code-skills에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.