Analyze account performance, download videos, summarize fans, plan your next content, and build OnlyFans API integrations with your AI agent.
Built by OnlyFansAPI.com. Seven practical skills for Claude Code, Codex, and other agents that support Agent Skills.
Recommended: install through skills.sh. Run this from your project:
npx skills@latest add onlyfansapi/skillChoose the skills you want and the agent you use. Add --global for a user-wide
installation. Reload your agent if needed for newly installed skills to appear.
Already using
onlyfansapi-skill? Your installed copy still works. Read the one-time migration instructions before updating.
You can ask documentation questions and build integration code without credentials. To work with live data, create an OnlyFansAPI account, connect your creator account, and configure an API key in your agent's environment or secret store:
export ONLYFANSAPI_API_KEY="your_api_key_here"Keep the key out of source control and frontend code. You can also connect through the optional API MCP using OAuth. API calls and services such as summary generation and exports may consume credits; the skills follow your requested scope and budget.
With the account-health skill installed, ask:
Review my account over the last 30 days. Why did revenue change, and what should I investigate next?
The agent compares earnings, subscriber growth, and chatting ratios, then explains the evidence and next actions. Without account access, try the API docs skill:
Show me how to fetch new subscriber statistics with the OnlyFans API.
| Skill | Ask your agent | What you get |
|---|---|---|
| onlyfans-account-health | “Why did revenue dip this month?” | A period comparison, acquisition and chatting ratios, relevant country/top-fan data, and prioritized actions. |
| onlyfans-chat-summary | “Summarize this fan for the next chatter.” | A fan handover or conversation recap, with known facts and open questions. |
| onlyfans-content-planner | “What should I create next based on last month's message sales?” | Ranked content ideas and a production plan grounded in message and media performance. |
| Skill | Ask your agent | What you get |
|---|---|---|
| onlyfans-video-downloader | “Download this vault video into my project folder.” | Verified local files or a vault archive from your connected account, with completion status. |
| Skill | Ask your agent | What you get |
|---|---|---|
| onlyfansapi-skill | “Compare net earnings across my accounts.” | General API workflows covering authentication, analytics, messaging, media, and MCP. |
| onlyfans-api-docs | “Show me how to fetch new subscriber statistics.” | Relevant endpoints, verified request/response details, and usable examples. |
| onlyfans-ai-chatbot | “Build a bot that handles typing and PPV purchases without duplicate replies.” | A webhook-driven chatbot integration in your existing stack, with idempotency and focused checks. |
Every skill works independently. To select one directly, list the collection, or install all seven:
npx skills@latest add onlyfansapi/skill --skill onlyfans-account-health
npx skills@latest add onlyfansapi/skill --list
npx skills@latest add onlyfansapi/skill --skill '*'Prefer installing the whole collection as a plugin? Both plugins contain the same seven skills. Use one installation route per agent to avoid duplicate copies. If switching, preserve local customizations and remove the standalone copies after verifying that the plugin works. Installing a plugin does not migrate them automatically.
claude plugin marketplace add onlyfansapi/skill
claude plugin install onlyfansapi@onlyfansapi --scope userRun /reload-plugins in Claude Code when prompted, or start a new session. Invoke a
skill explicitly with its plugin namespace, such as
/onlyfansapi:onlyfans-account-health, or describe your task normally.
codex plugin marketplace add onlyfansapi/skill
codex plugin add onlyfansapi@onlyfansapiStart a new Codex session after installation so its bundled skills become available. Use a Codex surface with plugin support; other clients can use the skills.sh route.
These commands install from this repository's marketplace. They do not require a listing in an official plugin directory. Neither plugin bundles MCP connections or asks for an API key during installation.
When you invoke a skill in a compatible client, it offers to connect a relevant missing MCP server. It asks once per conversation across the skills, respects a decline, and continues useful documentation or REST work while setup is pending.
Installing a skill or plugin does not connect MCP or authorize live account changes. See the setup guide and MCP reference.
For skills installed through skills.sh, complete the migration below if needed, then run:
npx skills updateFor the Claude Code plugin:
claude plugin marketplace update onlyfansapi
claude plugin update onlyfansapi@onlyfansapiRun /reload-plugins when prompted or start a new session. For the Codex plugin:
codex plugin marketplace upgrade onlyfansapi
codex plugin add onlyfansapi@onlyfansapiStart a new Codex session after reinstalling. Update settings vary by client; do not assume a plugin updates automatically.
The original onlyfansapi-skill keeps its name and general functionality. Its
source moved from the root SKILL.md to skills/onlyfansapi-skill/SKILL.md, with
its references alongside it. Existing installed copies keep working.
The skills CLI records that source path. An update may say the original skill was deleted upstream and offer to remove the local copy. Decline removal and reinstall the general skill once in the same scope and for the same agent:
# Existing project installation: run from that project
npx skills@latest add onlyfansapi/skill --skill onlyfansapi-skill
# Existing global installation
npx skills@latest add onlyfansapi/skill --skill onlyfansapi-skill --globalChoose the same agent(s), review local customizations, and replace the existing copy when prompted. Update any raw links to the old root file. The six specialists are optional and are not installed automatically when you update the general skill.
Native plugin installation is a separate choice; it does not repair an old standalone installation's update path.
- OnlyFans API reference
- Machine-readable OpenAPI schema
- Build an OnlyFans AI chatbot
- OnlyFansAPI Console
The standalone skills and both plugins share the same skills/ directory. Keep the
two plugin manifest versions synchronized and bump them when publishing changes to
the bundled skills or plugin metadata. There is no root SKILL.md, so the skills
CLI can discover all seven skills normally.
