agentleFS
nirholasnirholas/XActions/skills/creator-monetization/SKILL.md

creator-monetization

Skill648 starsChanged 9 months agoApache-2.0View on GitHub

Manages X/Twitter creator monetization features including ad revenue analytics, subscription management, tipping, and creator dashboard insights. Tracks earnings, analyzes monetization performance, and optimizes for revenue. Use when users want to check earnings, manage subscriptions, optimize monetization, or analyze ad revenue on X.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use src/autoPlugReplies.js to promote subscription on viral tweets

    line 67
  2. Distinctive:

    Only organic impressions count (not promoted/ad views)

    line 81

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Creator Monetization

Browser console scripts for managing and analyzing X/Twitter creator monetization features.

Script Selection

GoalFileNavigate to
Creator dashboard analyticssrc/creatorStudio.jsx.com/i/monetization
Subscription managementsrc/subscriptionManager.jsx.com/i/monetization
Content performance for monetizationsrc/tweetPerformance.jsx.com/USERNAME
Audience demographicssrc/audienceDemographics.jsx.com/USERNAME/followers

Creator Studio

File: src/creatorStudio.js

Scrapes and analyzes creator monetization data from X's dashboard.

Features

  • Ad revenue tracking (daily/weekly/monthly)
  • Impression and engagement rate for monetized content
  • Subscriber count and revenue
  • Tipping analytics
  • Monetization eligibility check

Eligibility Requirements

FeatureRequirements
Ad Revenue SharingPremium + 500 followers + 5M organic impressions (90 days)
SubscriptionsPremium + 500 followers
TippingAny account
Media StudioPremium

DOM Selectors

ElementSelector
Monetization nava[href="/i/monetization"]
Revenue display[data-testid="revenueAmount"]
Analytics tabs[role="tab"]
Subscription info[data-testid="subscriptionInfo"]
Earnings chart[data-testid="earningsChart"]

Monetization Strategy

Maximizing ad revenue

  1. src/tweetPerformance.js -- identify high-impression content types
  2. src/tweetScheduleOptimizer.js -- post at peak times for maximum reach
  3. src/contentRepurposer.js -- multiply high-performing content
  4. Focus on original tweets, not replies (replies don't earn ad revenue)
  5. Threads generate more impressions than single tweets

Growing subscriptions

  1. src/audienceDemographics.js -- understand who your audience is
  2. Post subscriber-only previews with src/postThread.js
  3. Use src/autoPlugReplies.js to promote subscription on viral tweets
  4. Track subscriber growth with src/followerGrowthTracker.js

Content that earns

Content TypeRevenue PotentialWhy
Threads (5+ tweets)HighMultiple impressions per reader
Hot takes/opinionsHighEngagement-driven reach
Tutorials/how-tosMediumBookmarks + shares
Reply threadsNoneReplies excluded from ad sharing

Notes

  • Ad revenue is paid monthly with a minimum threshold
  • Revenue data may lag 24-48 hours behind real-time
  • Only organic impressions count (not promoted/ad views)
  • Creator dashboard is only accessible to eligible accounts

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.