From plumai-skills
Foundation skill for PlumAI API. Sets up authentication, API base URL, plan awareness, and MCP server configuration. Read this skill first before using any other PlumAI skill.
How this skill is triggered — by the user, by Claude, or both
Slash command
/plumai-skills:plumai-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
PlumAI is an AI-powered content intelligence platform. Users generate SEO-optimized articles from discovered topics, with automatic translations, keyword research, and content quality scoring.
PlumAI is an AI-powered content intelligence platform. Users generate SEO-optimized articles from discovered topics, with automatic translations, keyword research, and content quality scoring.
All API calls require a PlumAI API key.
API key format: gn_ followed by 64 hex characters (67 characters total).
Header: Authorization: Bearer gn_...
Base URL: https://api.plumai.io/api/v1
Get your API key: https://plumai.io/dashboard/settings
GET /v1/account
Authorization: Bearer gn_...
Returns plan info, credit usage, and canGenerate flag.
If @plumai/mcp is connected, use the plumai:execute tool instead of raw HTTP calls. It handles auth and base URL automatically.
Setup:
{
"mcpServers": {
"plumai": {
"command": "npx",
"args": ["@plumai/mcp"],
"env": {
"PLUMAI_API_KEY": "gn_..."
}
}
}
}
When MCP is connected, skills reference only method + path. The MCP server handles:
| Plan | Articles/Month | Topic Discovery | API Access |
|---|---|---|---|
| Free | 3 | 5 topics | No |
| Starter | 10 | 20 topics | No |
| Pro | 50 | Unlimited | Yes |
| Ultra | 200 | Unlimited | Yes |
API access requires Pro or Ultra plan.
| Code | Language |
|---|---|
| en | English |
| hi | Hindi |
| es | Spanish |
| fr | French |
| ar | Arabic |
| pt-BR | Portuguese (Brazil) |
| pt-PT | Portuguese (Portugal) |
| ru | Russian |
| de | German |
When creating an API key, users select scopes:
| Scope | Permits |
|---|---|
articles:read | List, get, search articles |
articles:write | Generate articles, update status |
topics:read | List, get, search topics |
topics:write | Discover topics, keyword research |
jobs:read | Check job status |
| Status | Error Code | Agent Action |
|---|---|---|
| 400 | VALIDATION_ERROR | Fix request parameters |
| 401 | UNAUTHORIZED | Check API key is valid and included |
| 402 | PAYMENT_REQUIRED | User needs to upgrade plan |
| 403 | CREDIT_LIMIT_REACHED | No remaining credits — inform user |
| 403 | SCOPE_DENIED | API key missing required scope |
| 404 | NOT_FOUND | Resource doesn't exist or wrong owner |
| 409 | ARTICLE_EXISTS | Article already exists for topic+language |
| 409 | JOB_IN_PROGRESS | Generation already queued |
| 429 | RATE_LIMITED | Too many requests — wait and retry |
| 503 | SERVICE_BUSY | Temporary — retry after a moment |
npx claudepluginhub andginja/plumai-skills --plugin plumai-skillsConfig-driven SEO content pipeline with dashboard, multi-agent queue, token budgets, and research→write→audit→publish workflow. Supports StoryBrand/Cialdini/JTBD frameworks. Use for batch article generation or scaled publishing.
Automates Kontent AI operations via Composio's toolkit using Rube MCP. Discovers tool schemas, manages connections, and executes workflows. Essential for managing Kontent AI through Claude.
You are running the Blog Engine content generation pipeline. Your job is to produce one complete, publish-ready blog article from a keyword in the pipeline. Follow every step exactly and in order.