Agent skill

Pre Publish Post Assistant

Pre-publish assistant for new blog posts. An agent skill from nicepkg/ai-workflow.

Install Pre Publish Post Assistant

skills CLI

$ npx skills add nicepkg/ai-workflow --skill pre-publish-post-assistant -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow pre-publish-post-assistant --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant .claude/skills/pre-publish-post-assistant && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "pre-publish-post-assistant" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant into .claude/skills/pre-publish-post-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-publish-post-assistant", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add nicepkg/ai-workflow --skill pre-publish-post-assistant -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow pre-publish-post-assistant --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant .agents/skills/pre-publish-post-assistant && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "pre-publish-post-assistant" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant into .agents/skills/pre-publish-post-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-publish-post-assistant", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nicepkg/ai-workflow --skill pre-publish-post-assistant -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow pre-publish-post-assistant --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant .cursor/skills/pre-publish-post-assistant && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "pre-publish-post-assistant" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant into .cursor/skills/pre-publish-post-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-publish-post-assistant", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/nicepkg/ai-workflow.git --path workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nicepkg/ai-workflow --skill pre-publish-post-assistant -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow pre-publish-post-assistant --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant .gemini/skills/pre-publish-post-assistant && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "pre-publish-post-assistant" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant into .gemini/skills/pre-publish-post-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-publish-post-assistant", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install nicepkg/ai-workflow pre-publish-post-assistant

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add nicepkg/ai-workflow --skill pre-publish-post-assistant -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant .github/skills/pre-publish-post-assistant && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "pre-publish-post-assistant" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant into .github/skills/pre-publish-post-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-publish-post-assistant", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nicepkg/ai-workflow --skill pre-publish-post-assistant -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow pre-publish-post-assistant --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant .opencode/skills/pre-publish-post-assistant && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "pre-publish-post-assistant" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant into .opencode/skills/pre-publish-post-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-publish-post-assistant", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: pre-publish-post-assistant
GitHub stars: 285
Token cost: ~1.7k tokens
SKILL.md length: 424 words
Files: 1
Skills in repo: 61
Repo updated: Jan 20, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Pre-publish assistant for new blog posts. An agent skill from nicepkg/ai-workflow.

Works in 5 steps: Analyze Content → Load Taxonomy → Match & Score → …
The user wants to classify a new post with categories and tags
SKILL.md covers Purpose, When to Use This Skill, Key Principles and Input Formats, plus 6 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pre Publish Post Assistant is an agent skill from nicepkg/ai-workflow. Pre-publish assistant for new blog posts. Use when the user wants to classify a new post with categories and tags, generate SEO metadata (title, description, focus keyphrase), or get intelligent suggestions with rationale. Works with draft content (file path, URL, or text) and suggests from existing taxonomy to maintain balanced distribution.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Blog and article writing. The repository describes itself as: 🚀 170+ pre-built skills for Claude Code, Cursor, Codex & 14+ AI tools. Stop re-teaching your AI the same things. One command → instant domain expertise. Marketing, SEO, Trading… The licence is MIT.

When your agent uses it

The user wants to classify a new post with categories and tags
Generate SEO metadata (title
Focus keyphrase)
Get intelligent suggestions with rationale

Example prompts

“/pre-publish-post-assistant”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Analyze Content
Load Taxonomy
Match & Score
Generate SEO
Present with Rationale

What it can do on your machine

Read from SKILL.md and the folder at commit d167b41. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pre Publish Post Assistant loads about 1.7k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 424 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~93
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nicepkg/ai-workflow at commit d167b41, republished under its MIT licence (© nicepkg). 424 words, ~1,683 tokens.

Download SKILL.mdSave it as .claude/skills/pre-publish-post-assistant/SKILL.md (or your agent's skills folder).

name: pre-publish-post-assistant
description: Pre-publish assistant for new blog posts. Use when the user wants to classify a new post with categories and tags, generate SEO metadata (title, description, focus keyphrase), or get intelligent suggestions with rationale. Works with draft content (file path, URL, or text) and suggests from existing taxonomy to maintain balanced distribution.

Pre-publish Post Assistant Skill

Purpose

This skill helps prepare blog posts for publication by providing intelligent suggestions for:

Categories - From existing site categories, with distribution awareness
Tags - From existing tags, avoiding tag pollution
SEO Metadata - Title, meta description, and focus keyphrase

All suggestions include rationale explaining the reasoning.

When to Use This Skill

User says "classify this post" or "suggest categories/tags"
User asks to "prepare this post for publishing"
User wants "SEO suggestions" for a draft
User provides a draft post and asks for taxonomy suggestions
User mentions "new blog post" and needs categorization help

Key Principles

Category Selection

Limit to 1-2 categories per post (primary + optional secondary)
Prefer categories with moderate post counts (avoid over/under-populated)
Match content theme, not just keywords
Consider category hierarchy if applicable

Tag Selection

Limit to 3-5 tags per post
Only use existing tags (no new tag creation unless explicitly requested)
Avoid tag pollution (tags with only 1-2 posts are low value)
Prefer tags that group related content meaningfully
Consider tag search potential

SEO Metadata

Title: 50-60 characters, include primary keyword, compelling
Meta Description: 150-160 characters, summarize value proposition, include CTA
Focus Keyphrase: 2-4 words, searchable, relevant to content

Input Formats

The skill accepts draft content in multiple formats:

# File path
"Classify this post: /path/to/draft.md"

# URL (for already-published posts needing optimization)
"Suggest tags for https://example.com/my-post/"

# Inline text
"Here's my draft: [content]... What categories fit?"

Data Sources

Categories and Tags

Can be retrieved from:

WordPress GraphQL - Live data from WP
Static dist folder - Parse from built site (/category/, /tag/ pages)
Cached taxonomy file - Pre-generated taxonomy.json

Show full SKILL.md (184 more words)Show less

Distribution Data

For balanced suggestions, the skill needs post counts per category/tag:

Categories: Aim for even distribution, flag if category would become oversized
Tags: Prefer tags with 5+ posts, warn about orphan tags

Output Format

markdown

## Suggested Categories

| Category | Post Count | Confidence | Rationale |
|----------|------------|------------|-----------|
| personal-development | 245 | High | Core theme matches self-improvement focus |
| productivity-effectiveness | 89 | Medium | Secondary theme around habits and routines |

**Recommendation**: Use "personal-development" as primary category.

---

## Suggested Tags

| Tag | Post Count | Confidence | Rationale |
|-----|------------|------------|-----------|
| habits | 45 | High | Central topic of the post |
| productivity | 67 | High | Directly discussed |
| morning-routine | 12 | Medium | Specific example in content |

**Recommendation**: Use all 3 tags. Avoid creating new tags.

---

## SEO Metadata

**Title** (58 chars):
> How to Build Morning Habits That Actually Stick | Your Blog

**Meta Description** (156 chars):
> Discover the science-backed approach to building morning habits that last. Learn the 3-step framework used by high performers. Start your transformation today.

**Focus Keyphrase**:
> morning habits

**Rationale**:
- "morning habits" has good search volume and matches user intent
- Title includes keyphrase naturally at the beginning
- Description creates urgency and promises specific value

Workflow

1. Analyze Content

Extract main themes and topics
Identify key concepts and terminology
Determine content type (how-to, opinion, review, etc.)

2. Load Taxonomy

Fetch existing categories with post counts
Fetch existing tags with post counts
Identify distribution patterns

3. Match & Score

Score each category/tag by relevance
Consider distribution balance
Flag potential issues (orphan tags, oversized categories)

4. Generate SEO

Craft title with primary keyword
Write compelling meta description
Suggest focus keyphrase

5. Present with Rationale

Show recommendations in table format
Explain reasoning for each suggestion
Highlight any concerns or alternatives

Configuration

json

{
  "taxonomy_source": "graphql|dist|file",
  "dist_path": "./dist",
  "taxonomy_file": "./taxonomy.json",
  "graphql_endpoint": "https://wp.example.com/graphql",
  "limits": {
    "max_categories": 2,
    "max_tags": 5,
    "min_tag_posts": 3
  },
  "seo": {
    "title_max_length": 60,
    "description_max_length": 160,
    "site_name": "Your Blog"
  }
}

Example Usage

Basic Classification

User: "Classify this post for me: /content/drafts/morning-routine-guide.md"

Claude: [Reads file, analyzes content, fetches taxonomy]
        [Presents category/tag suggestions with rationale]
        [Generates SEO metadata]

Quick Tag Check

User: "What tags should I use for a post about Bitcoin ETFs and institutional adoption?"

Claude: [Analyzes topic, checks existing tags]
        "Based on your existing tags, I recommend:
        - bitcoin (89 posts) - primary topic
        - cryptocurrency (45 posts) - broader category
        - investing (23 posts) - relevant angle

        Avoid creating new tags like 'etf' or 'institutional' unless you plan
        to write more content on these specific topics."

SEO Focus

User: "Generate SEO metadata for my post about productivity apps for remote workers"

Claude: [Analyzes topic and search intent]

        Title: "Best Productivity Apps for Remote Workers in 2025 | Your Blog"

        Description: "Discover the top productivity apps that remote workers
        swear by. From task management to focus tools, find the perfect
        stack for your home office."

        Focus Keyphrase: "productivity apps remote workers"

Best Practices Enforced

No tag pollution - Won't suggest creating new tags unless justified
Balanced distribution - Warns if category is becoming oversized
SEO compliance - Enforces character limits and keyword placement
Existing taxonomy - Always checks against actual site data
Transparent reasoning - Every suggestion includes rationale

Files

Just SKILL.md in workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant of nicepkg/ai-workflow.

Open the folder on GitHubat commit d167b41

Compare with similar skills

Pre Publish Post Assistant next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pre Publish Post Assistant compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Pre Publish Post Assistant this skillnicepkg/ai-workflow	285	—	~1.7k	Automated safety check: Pass	MIT	8 mo ago
Khazix WeChat Article WriterKKKKhazix/khazix-skills	21k	2 repos	~2.9k	Automated safety check: Pass	MIT	6 days ago
Figurevectorize-io/hindsight	47k	—	~1.9k	Automated safety check: Pass	MIT	today
SepiaNanako0129/sepia	3k	—	~3.6k	Automated safety check: Pass	MIT	2 days ago
Blog Post Draftingluongnv89/claude-howto	42k	—	~2.1k	Automated safety check: Pass	MIT	8 days ago
Notion To Blogwasp-lang/wasp	19k	—	~922	Automated safety check: Pass	MIT	today

Similar skills

Khazix WeChat Article Writer
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
21k GitHub starsUsed in 2 repos~2.9k tokens
Writing & ContentAuto-check passed
Figure
vectorize-io/hindsight
Draw an animated figure (boxes, arrows, moving data) as one self-contained SVG for a GitHub README, PR, issue or blog post.
47k GitHub stars~1.9k tokensUpdated today
Writing & ContentAuto-check passed
Sepia
Nanako0129/sepia
Make AI-generated writing read as human-written, in fiction and in professional prose.
3k GitHub stars~3.6k tokensUpdated 2 days ago
Writing & ContentAuto-check passed
Blog Post Drafting
luongnv89/claude-howto
Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.
42k GitHub stars~2.1k tokensUpdated 8 days ago
Writing & ContentAuto-check passed
Notion To Blog
wasp-lang/wasp
Transfer a blog post from Notion to the Wasp blog. An agent skill from wasp-lang/wasp.
19k GitHub stars~922 tokensUpdated today
Writing & ContentAuto-check passed
Blog Post
nteract/semiotic
Author a new entry for the Semiotic blog. An agent skill from nteract/semiotic.
2.7k GitHub stars~3.4k tokensUpdated yesterday
Writing & ContentAuto-check passed

Questions about Pre Publish Post Assistant

What does Pre Publish Post Assistant do?

Pre-publish assistant for new blog posts. An agent skill from nicepkg/ai-workflow. Pre Publish Post Assistant is an agent skill from nicepkg/ai-workflow. Pre-publish assistant for new blog posts.

When should I use Pre Publish Post Assistant?

Pre Publish Post Assistant fits situations like: the user wants to classify a new post with categories and tags; generate SEO metadata (title; focus keyphrase); get intelligent suggestions with rationale.

How do I install Pre Publish Post Assistant in Claude Code?

Run `npx skills add nicepkg/ai-workflow --skill pre-publish-post-assistant -a claude-code`. Or copy the skill folder (workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant in nicepkg/ai-workflow) into .claude/skills/pre-publish-post-assistant in your project. Claude Code loads it when a task matches its description.

How do I install Pre Publish Post Assistant in Codex?

Run `npx skills add nicepkg/ai-workflow --skill pre-publish-post-assistant -a codex`. Or copy the skill folder (workflows/content-creator-workflow/.claude/skills/pre-publish-post-assistant in nicepkg/ai-workflow) into .agents/skills/pre-publish-post-assistant in your project. Codex loads it when a task matches its description.

Can I use Pre Publish Post Assistant in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nicepkg/ai-workflow --skill pre-publish-post-assistant -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pre-publish-post-assistant, .gemini/skills/pre-publish-post-assistant, .github/skills/pre-publish-post-assistant and .opencode/skills/pre-publish-post-assistant in your project.

What does Pre Publish Post Assistant need to run?

SKILL.md names no scripts, command-line tools or credentials: Pre Publish Post Assistant is instructions for the agent only.

Does Pre Publish Post Assistant access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pre Publish Post Assistant safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Pre Publish Post Assistant use?

Pre Publish Post Assistant is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pre Publish Post Assistant use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Pre Publish Post Assistant?

Skills that share tags, products or a category with Pre Publish Post Assistant: Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars), Figure (vectorize-io/hindsight, 47k stars), Sepia (Nanako0129/sepia, 3k stars) and Blog Post Drafting (luongnv89/claude-howto, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pre Publish Post Assistant?

nicepkg (a GitHub organization) maintains it in nicepkg/ai-workflow, which has 285 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on January 20, 2026.

Source: nicepkg/ai-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Pre Publish Post Assistant

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Pre-publish Post Assistant Skill

Purpose

When to Use This Skill

Key Principles

Category Selection

Tag Selection

SEO Metadata

Input Formats

Data Sources

Categories and Tags

Distribution Data

Output Format

Workflow

1. Analyze Content

2. Load Taxonomy

3. Match & Score

4. Generate SEO

5. Present with Rationale

Configuration

Example Usage

Basic Classification

Quick Tag Check

SEO Focus

Best Practices Enforced

Files

Compare with similar skills

Similar skills

More from nicepkg/ai-workflow

Related

Questions about Pre Publish Post Assistant