blog-taxonomy
Extract, suggest, and sync tags and categories for blog posts across all major CMS platforms. Supports WordPress REST API, Shopify GraphQL, Ghost Content API, Strapi REST/GraphQL, and Sanity GROQ. Generates tag suggestions from content analysis (keyword frequency, heading extraction, semantic grouping), enforces minimum post-count thresholds to prevent thin tag archives, and syncs taxonomy via authenticated API calls. Use when user says "tags", "categories", "taxonomy", "tag suggestions", "sync
Security Assessment
About blog-taxonomy
This skill extracts, suggests, and synchronizes tags and categories for blog posts across major CMS platforms. It solves the problem of inconsistent, bloated, or thin taxonomy by combining content analysis with authenticated CMS API operations, exposing three commands: suggest (derive candidate tags and categories from a file), sync (push taxonomy to a CMS), and audit (find thin tags, orphan tags, and taxonomy bloat).
Tag suggestion works through a defined pipeline: parse headings and emphasis, run frequency analysis with occurrence thresholds and stop-word exclusion, perform semantic grouping (merging singular/plural and hyphenation variants and synonyms), then deduplicate with fuzzy slug matching and rank by a weighted score before returning the top suggestions. It ships adapter documentation for WordPress (REST, Application Passwords), Shopify (GraphQL Admin API, access token), Ghost (Admin API with JWT signing), Strapi (REST/GraphQL, Bearer token), and Sanity (GROQ and Mutations, Bearer token), including endpoint shapes, pagination handling, and version differences. The audit workflow inventories usage and applies health-check thresholds (thin-tag, orphan-tag, tag-bloat, category depth, uncategorized posts, duplicate slugs) to produce prioritized recommendations.
It targets content teams, bloggers, and developers who manage editorial taxonomy across one or more CMS platforms. Authentication uses each platform's standard official mechanism (application passwords, API tokens, Bearer tokens, JWTs), and all writes go to the user's own CMS via documented public APIs, with no credential exfiltration or destructive behavior beyond normal taxonomy edits.
FAQ
Which CMS platforms are supported?
WordPress (REST), Shopify (GraphQL Admin API), Ghost (Admin API), Strapi (REST or GraphQL), and Sanity (GROQ/Mutations).
What can I do with it?
Suggest tags and categories from a post's content, sync taxonomy to a CMS via authenticated API calls, and audit existing taxonomy for thin tags, orphan tags, and bloat.
How does tag suggestion decide what to recommend?
It parses headings and emphasis, runs frequency analysis with occurrence thresholds, groups related terms semantically, deduplicates with fuzzy slug matching, and ranks candidates by a weighted score.
How is authentication handled?
Through each platform's standard official method: WordPress Application Passwords, Shopify access tokens, Ghost JWT signed with the admin key, and Strapi/Sanity Bearer tokens. Credentials are used only against your own CMS.
Does it delete anything automatically?
The audit recommends actions such as merging or deleting orphan tags, but the described workflow surfaces prioritized recommendations rather than performing destructive deletions unattended.
Install blog-taxonomy
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
agricidaniel/claude-blog