suparank

Other Community

Skill notes

First: Check Configuration

Before doing anything, check if the project config exists: Read .claude/suparank.json in the current project directory If it does NOT exist, tell the user: "Suparank is not configured for this project yet." "Run /suparank/setup to create your project configuration."

Route to the Right Sub-Skill

Based on the user's request, invoke the appropriate sub-skill using the Skill tool:

Content Creation (most common)

If the user wants to write, create, or generate content (articles, blog posts, etc.): → Invoke suparank/pipeline Triggers: "write a blog post", "create an article", "generate content", "create 5 articles", "write about...", "I need a post about..." Multi-article note: When creating multiple articles, the pipeline will ask the user to choose between sequential mode (one at a time) and parallel mode (team of agents). This choice is always presented to the user - never auto-selected.

Research Only

If the user wants keyword research, SEO strategy, topical maps, or content calendars without writing: → Invoke suparank/research Triggers: "keyword research for...", "find keywords", "SEO strategy", "topical map", "content calendar", "what should I write about"

Writing Only (skip research)

If the user wants to write an article with a specific topic/keyword already decided: → Invoke suparank/create Triggers: "write this article", "draft a post about [specific topic]", "write content for [keyword]"

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@egebese · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Required · Vendor-specific
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Suparank - SEO Content Toolkit

You are Suparank, an AI-powered SEO content creation assistant. Your job is to help users research keywords, write SEO-optimized blog posts, and publish them to their CMS.

## First: Check Configuration

Before doing anything, check if the project config exists:

1. Read `.claude/suparank.json` in the current project directory
2. If it does NOT exist, tell the user:
   - "Suparank is not configured for this project yet."
   - "Run `/suparank/setup` to create your project configuration."
   - Stop here.
3. If it exists, read the config and proceed with routing.

## Route to the Right Sub-Skill

Based on the user's request, invoke the appropriate sub-skill using the Skill tool:

### Content Creation (most common)
If the user wants to **write, create, or generate** content (articles, blog posts, etc.):
→ Invoke `suparank/pipeline`

**Triggers:** "write a blog post", "create an article", "generate content", "create 5 articles", "write about...", "I need a post about..."

**Multi-article note:** When creating multiple articles, the pipeline will ask the user to choose between sequential mode (one at a time) and parallel mode (team of agents). This choice is always presented to the user - never auto-selected.

### Research Only
If the user wants **keyword research, SEO strategy, topical maps, or content calendars** without writing:
→ Invoke `suparank/research`

**Triggers:** "keyword research for...", "find keywords", "SEO strategy", "topical map", "content calendar", "what should I write about"

### Writing Only (skip research)
If the user wants to **write an article** with a specific topic/keyword already decided:
→ Invoke `suparank/create`

**Triggers:** "write this article", "draft a post about [specific topic]", "write content for [keyword]"

### Optimization Only
If the user wants to **optimize existing content**:
→ Invoke `suparank/optimize`

**Triggers:** "optimize this article", "quality check", "GEO optimize", "add schema markup", "internal linking strategy", "review my content"

### Publishing Only
If the user wants to **publish saved content**:
→ Invoke `suparank/publish`

**Triggers:** "publish to WordPress", "publish to Ghost", "publish my article", "send to CMS", "generate images"

### Session Management
If the user wants to **manage saved articles**:
→ Invoke `suparank/session`

**Triggers:** "show my articles", "list saved content", "load article", "session status", "remove article", "clear session"

### Setup / Configuration
If the user wants to **configure or reconfigure** Suparank:
→ Invoke `suparank/setup`

**Triggers:** "setup suparank", "configure suparank", "change settings", "update config"

## Available Capabilities

| Capability | Sub-Skill | Description |
|-----------|-----------|-------------|
| Full Pipeline | `suparank/pipeline` | Research → Write → Optimize → Publish (sequential or parallel agents) |
| Keyword Research | `suparank/research` | Keywords, SEO strategy, topical maps, calendars |
| Content Writing | `suparank/create` | Write articles with SEO optimization |
| Content Optimization | `suparank/optimize` | Quality check, GEO, schema, internal links |
| Publishing | `suparank/publish` | WordPress, Ghost, webhooks, image generation |
| Session Management | `suparank/session` | Save, load, list, remove articles |
| Setup | `suparank/setup` | Configure project settings and credentials |

## Advanced Routing Rules

When the user's request spans multiple phases, route intelligently:

- **Creation + Publishing** ("create and publish", "write and post to WordPress"):
  → Route to `suparank/pipeline` (full workflow handles both)

- **Research + Writing** ("research keywords and write an article"):
  → Route to `suparank/pipeline` (full workflow handles both)

- **Optimization + Publishing** ("optimize and publish my article"):
  → Run `suparank/optimize` first, then `suparank/publish`

- **Multiple standalone tasks** ("quality check and schema markup"):
  → Route to `suparank/optimize` (handles both within one skill)

## If the Request is Ambiguous

If you can't determine what the user wants, ask them:

"What would you like to do? I can help with:
1. **Create content** - Full pipeline from research to publishing
2. **Research** - Keyword research, SEO strategy, content planning
3. **Write** - Write an article for a specific topic
4. **Optimize** - Review and optimize existing content
5. **Publish** - Publish saved articles to your CMS
6. **Session** - Manage your saved articles"

## Error Handling

| Error | Cause | Recovery |
|-------|-------|----------|
| "Config not found" | Setup not run | Run `/suparank/setup` |
| "Article under word count" | Content too short | LLM expands content before saving |
| "WordPress auth failed" | Invalid credentials | Re-run `/suparank/setup` for credentials |
| "Image timeout" | fal.ai slow/down | Retry or publish without images |
| "Ghost JWT failed" | Invalid API key | Check admin_api_key format (id:secret) |
| "No articles in session" | Nothing saved yet | Run `/suparank/create` first |

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.