AI SummarySelf-configuring content creation pipeline. Creates SEO & GEO-optimized content matched to your project and brand voice, then validates with geo-lint until clean. For project-specific rules (components, file naming, categories), the skill
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "content-creator" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/content-creator && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/content-creator/SKILL.md "https://raw.githubusercontent.com/IJONIS/geo-lint/main/skills/content-creator/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Self-configuring content creation pipeline with geo-lint validation. On first use, scans your project to learn its framework, content schema, categories, and authors, then creates SEO & GEO-optimized content matched to your brand voice. Validates every piece with geo-lint's 92 rules until zero violations. Triggers on: "content-creator", "create content", "write blog", "new post", "content calendar", "brand voice", "content strategy".
Content Creator
Self-configuring content creation pipeline. Creates SEO & GEO-optimized content matched to your project and brand voice, then validates with geo-lint until clean. For project-specific rules (components, file naming, categories), the skill generates a local content-config skill on first use via the setup workflow.
Command Router
Parse $ARGUMENTS and route to the matching workflow: | Argument | Workflow | |----------|----------| | setup | Auto-discover project, questionnaire, generate content-config | | create [blog\|page\|project] | Full content creation pipeline | | voice | Analyze and configure brand voice | | calendar | Plan monthly content calendar | | refresh | Re-scan project, update content-config | | _(no args)_ | If no config exists → auto-trigger setup. Otherwise show commands. |
Pre-Flight Check
Before any workflow except setup: • Check if .claude/skills/content-config/SKILL.md exists in the project root. • If missing → inform the user: "No project content config found. Running setup first..." Then auto-trigger the setup workflow. • If found → read it into context and proceed with the requested workflow. ---
Workflow: setup
Three phases: auto-discover → questionnaire → generate.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster