newmanxbt/normans-skills

x-content-optimizer

Audit and optimize tweets, X articles, and threads for X's recommendation algorithm.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/newmanxbt/normans-skills --skill x-content-optimizer

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

X Optimizer

Audit content against X's recommendation algorithm (Phoenix/Grok-based) and provide optimization suggestions.

Workflow

Input Content → Algorithm Audit → Issue Report → Fact Check → Suggested Revision → User Approval → Final Output

Step 1: Receive Content

Accept content in any format:

  • Direct text paste
  • Markdown file
  • Multiple tweets (thread)

Identify content type:

  • Single Tweet: Under 280 chars, one post
  • X Article: Long-form native content
  • Thread: Multiple connected tweets

Step 2: Algorithm Audit

Reference: algorithm-rules.md

Audit Categories

A. Positive Signal Potential

SignalCheck
FavoriteEmotional resonance or valuable insight?
ReplyDiscussion hook or question?
RepostShare-worthy content?
DwellDepth to hold attention?
ClickCuriosity-inducing hook?

B. Negative Signal Risk

SignalCheck
Not InterestedRelevant to target audience?
Mute/BlockRespectful, not spammy?
ReportPolicy compliant?

C. Learned Penalties

FactorCheck
External LinksCore value IN content, not behind link?
ClickbaitPayoff matches promise?

D. Format & Structure

  • Hook strength (first line/50 chars)
  • Content completeness
  • Engagement driver (CTA/question)
  • Readability (line breaks, emphasis)

Step 3: Generate Audit Report

Format:

## Audit Report

### Score Summary
- Positive Signal Potential: [HIGH/MEDIUM/LOW]
- Negative Signal Risk: [HIGH/MEDIUM/LOW]
- Overall Algorithm Fit: [EXCELLENT/GOOD/NEEDS WORK/POOR]

### Issues Found
1. [Issue]: [Explanation]
   - Impact: [Which signal affected]
   - Fix: [Specific suggestion]

2. [Issue]: [Explanation]
   ...

### Strengths
- [What works well]

Step 4: Fact Check

CRITICAL: Before adding or suggesting any factual information (numbers, dates, statistics, claims about products/companies), you MUST:

  1. Identify factual claims in the content that need verification
  2. Search and verify using WebSearch tool
  3. Only include verified facts in the optimized version
  4. Remove or flag unverifiable claims - never fabricate data

Examples requiring verification:

  • Product launch dates ("X was released in...")
  • Statistics ("X% of users...")
  • Company announcements ("Company just launched...")
  • Performance metrics ("reduces time by X%")

If no verifiable source exists, either:

  • Remove the claim entirely
  • Replace with qualitative language ("significantly improves" instead of fake percentages)
  • Ask user if they have a source

Step 5: Generate Optimized Version

Provide complete rewritten version addressing all issues.

Format:

## Optimized Version

[Full rewritten content]

### Changes Made
1. [Change]: [Why it improves algorithm score]
2. [Change]: [Why it improves algorithm score]

Step 6: Offer One-Click Apply

If content is from a file:

Would you like me to apply these changes to the file?

If direct text:

Here's your optimized content ready to copy.

Content-Specific Guidelines

Single Tweet

  • Hook in first 50 chars (preview visibility)
  • Core value delivered completely
  • End with engagement driver
  • External links: provide context first

X Article

  • Title: curiosity + specific value
  • Opening: validate the click
  • Body: structured sections
  • Closing: summary + CTA
  • Advantage: keeps users on platform (dwell time)

Thread

  • Tweet 1: Standalone hook (must work alone)
  • Tweet 2-3: Engagement point (question)
  • Middle: Value delivery
  • Final: CTA (repost, follow)
  • Each tweet: Complete and independent

Quick Reference

High-Impact Improvements

  1. Add question/discussion hook → ↑ Reply
  2. Add quotable statement → ↑ Repost
  3. Strengthen opening hook → ↑ Click, Dwell
  4. Remove/contextualize external links → ↑ Dwell Time
  5. Add specific data/examples → ↑ Credibility, Share

Common Issues

IssueImpactFix
Weak hookLow click/dwellRewrite first line
Link-only valueUser leaves platformAdd value IN content
No engagement driverLow replyAdd question/CTA
Wall of textLow dwellAdd line breaks
Off-topic"Not interested" signalClarify audience fit

관련 작업