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 tags", "WordPress tags", "Shopify tags".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized, actionable reference with concrete code and clear workflows, but it is a monolithic file with no progressive disclosure of platform adapters into separate references, and the destructive sync workflow lacks an explicit validation checkpoint.

Suggestions

Add an explicit validation/dry-run checkpoint to the sync workflow (e.g., preview taxonomy changes and require confirmation before pushing batch CMS writes) to lift workflow_clarity above 3.

Extract the five per-platform CMS adapter specs into separate reference files (e.g., references/wordpress.md, references/shopify.md) and link to them one level deep from the body, improving progressive disclosure and token efficiency.

Tighten the security-rule paragraph and environment-variable table into terser form to reduce residual verbosity.

Dimension	Reasoning	Score
Conciseness	The body is dense and efficient — tables, adapter specs, thresholds, and code snippets — with little padding and no over-explanation of concepts Claude knows. Minor verbosity in the security-rule paragraph and env-var table keeps it just below a 5.	4 / 5
Actionability	Provides concrete, mostly copy-paste-ready HTTP/GraphQL/GROQ snippets per platform, a scoring formula, Levenshtein thresholds, and pagination loops. Placeholders like {CMS_URL} and a few incomplete flows prevent a perfect score.	4 / 5
Workflow Clarity	The suggest and audit workflows are clearly numbered, but the sync workflow performs destructive batch CMS writes with no explicit validate-then-proceed checkpoint or dry-run preview, capping this dimension at 3 per the batch/destructive guideline.	3 / 5
Progressive Disclosure	All content is inlined into a single ~270-line SKILL.md with no bundle files; substantial per-platform adapter reference material that could live in separate files is inline, though it is reasonably section-organized with no nested references.	3 / 5
	Total	14 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is comprehensive, specific, and well-targeted: it states concrete capabilities, enumerates supported platforms and mechanisms, and provides an explicit natural-language trigger clause. It is a strong, low-conflict skill description.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — extract/suggest/sync, keyword frequency, heading extraction, semantic grouping, min post-count thresholds, authenticated API calls — with comprehensive coverage of mechanisms and platforms.	5 / 5
Completeness	Clearly answers 'what' (extract/suggest/sync taxonomy across CMS platforms with named mechanisms) and 'when' (concrete trigger phrases), both explicitly stated.	5 / 5
Trigger Term Quality	An explicit 'Use when user says...' clause lists natural phrases users actually say, including synonyms and platform-specific terms (tags, categories, taxonomy, tag suggestions, sync tags, WordPress tags, Shopify tags).	5 / 5
Distinctiveness Conflict Risk	Clear niche of blog taxonomy/CMS sync across five named platforms with distinct triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: AgriciDaniel/claude-blog
Path: brain/.raw/sources/claude-blog-skill/skills/blog-taxonomy/SKILL.md
Commit: 84f7abf

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.