Awesome-omni-skills content-creator
Content Creator workflow skill. Use this skill when the user needs Professional-grade brand voice analysis, SEO optimization, and platform-specific content frameworks and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
git clone https://github.com/diegosouzapw/awesome-omni-skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/content-creator" ~/.claude/skills/diegosouzapw-awesome-omni-skills-content-creator && rm -rf "$T"
skills/content-creator/SKILL.mdContent Creator
Overview
This public intake copy packages
plugins/antigravity-awesome-skills-claude/skills/content-creator from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses
metadata.json plus ORIGIN.md as the provenance anchor for review.
Content Creator Professional-grade brand voice analysis, SEO optimization, and platform-specific content frameworks.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Keywords, Key Scripts, Performance Metrics, Integration Points, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
- Use this skill when writing blog posts, creating social media content, establishing brand voice, optimizing content for SEO, or planning content calendars.
- Use when the request clearly matches the imported source intent: Professional-grade brand voice analysis, SEO optimization, and platform-specific content frameworks.
- Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
- Use when provenance needs to stay visible in the answer, PR, or review packet.
- Use when copied upstream references, examples, or scripts materially improve the answer.
- Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.
Operating Table
| Situation | Start here | Why it matters |
|---|---|---|
| First-time use | | Confirms repository, branch, commit, and imported path before touching the copied workflow |
| Provenance review | | Gives reviewers a plain-language audit trail for the imported source |
| Workflow execution | | Starts with the smallest copied file that materially changes execution |
| Supporting context | | Adds the next most relevant copied source file without loading the entire package |
| Handoff decision | | Helps the operator switch to a stronger native skill when the task drifts |
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
- Analyze Existing Content (if available)
- Define Voice Attributes
- Review brand personality archetypes in references/brand_guidelines.md
- Select primary and secondary archetypes
- Choose 3-5 tone attributes
- Document in brand guidelines
- Create Voice Sample
Imported Workflow Notes
Imported: Core Workflows
Establishing Brand Voice (First Time Setup)
When creating content for a new brand or client:
-
Analyze Existing Content (if available)
python scripts/brand_voice_analyzer.py existing_content.txt -
Define Voice Attributes
- Review brand personality archetypes in
references/brand_guidelines.md - Select primary and secondary archetypes
- Choose 3-5 tone attributes
- Document in brand guidelines
- Review brand personality archetypes in
-
Create Voice Sample
- Write 3 sample pieces in chosen voice
- Test consistency using analyzer
- Refine based on results
Creating SEO-Optimized Blog Posts
-
Keyword Research
- Identify primary keyword (search volume 500-5000/month)
- Find 3-5 secondary keywords
- List 10-15 LSI keywords
-
Content Structure
- Use blog template from
references/content_frameworks.md - Include keyword in title, first paragraph, and 2-3 H2s
- Aim for 1,500-2,500 words for comprehensive coverage
- Use blog template from
-
Optimization Check
python scripts/seo_optimizer.py blog_post.md "primary keyword" "secondary,keywords,list" -
Apply SEO Recommendations
- Adjust keyword density to 1-3%
- Ensure proper heading structure
- Add internal and external links
- Optimize meta description
Social Media Content Creation
-
Platform Selection
- Identify primary platforms based on audience
- Review platform-specific guidelines in
references/social_media_optimization.md
-
Content Adaptation
- Start with blog post or core message
- Use repurposing matrix from
references/content_frameworks.md - Adapt for each platform following templates
-
Optimization Checklist
- Platform-appropriate length
- Optimal posting time
- Correct image dimensions
- Platform-specific hashtags
- Engagement elements (polls, questions)
Content Calendar Planning
-
Monthly Planning
- Copy
assets/content_calendar_template.md - Set monthly goals and KPIs
- Identify key campaigns/themes
- Copy
-
Weekly Distribution
- Follow 40/25/25/10 content pillar ratio
- Balance platforms throughout week
- Align with optimal posting times
-
Batch Creation
- Create all weekly content in one session
- Maintain consistent voice across pieces
- Prepare all visual assets together
Imported: Keywords
content creation, blog posts, SEO, brand voice, social media, content calendar, marketing content, content strategy, content marketing, brand consistency, content optimization, social media marketing, content planning, blog writing, content frameworks, brand guidelines, social media strategy
Examples
Example 1: Ask for the upstream workflow directly
Use @content-creator to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @content-creator against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @content-creator for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @content-creator using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Imported Usage Notes
Imported: Quick Start
For Brand Voice Development
- Run
on existing content to establish baselinescripts/brand_voice_analyzer.py - Review
to select voice attributesreferences/brand_guidelines.md - Apply chosen voice consistently across all content
For Blog Content Creation
- Choose template from
references/content_frameworks.md - Research keywords for topic
- Write content following template structure
- Run
to optimizescripts/seo_optimizer.py [file] [primary-keyword] - Apply recommendations before publishing
For Social Media Content
- Review platform best practices in
references/social_media_optimization.md - Use appropriate template from
references/content_frameworks.md - Optimize based on platform-specific guidelines
- Schedule using
assets/content_calendar_template.md
Imported: Quick Commands
# Analyze brand voice python scripts/brand_voice_analyzer.py content.txt # Optimize for SEO python scripts/seo_optimizer.py article.md "main keyword" # Check content against brand guidelines grep -f references/brand_guidelines.md content.txt # Create monthly calendar cp assets/content_calendar_template.md this_month_calendar.md
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
- Always start with audience need/pain point
- Research before writing
- Create outline using templates
- Write first draft without editing
- Optimize for SEO
- Edit for brand voice
- Proofread and fact-check
Imported Operating Notes
Imported: Best Practices
Content Creation Process
- Always start with audience need/pain point
- Research before writing
- Create outline using templates
- Write first draft without editing
- Optimize for SEO
- Edit for brand voice
- Proofread and fact-check
- Optimize for platform
- Schedule strategically
Quality Indicators
- SEO score above 75/100
- Readability appropriate for audience
- Consistent brand voice throughout
- Clear value proposition
- Actionable takeaways
- Proper visual formatting
- Platform-optimized
Common Pitfalls to Avoid
- Writing before researching keywords
- Ignoring platform-specific requirements
- Inconsistent brand voice
- Over-optimizing for SEO (keyword stuffing)
- Missing clear CTAs
- Publishing without proofreading
- Ignoring analytics feedback
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in
plugins/antigravity-awesome-skills-claude/skills/content-creator, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated
SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
- Use when the work is better handled by that native specialization after this imported skill establishes context.@conductor-validator
- Use when the work is better handled by that native specialization after this imported skill establishes context.@confluence-automation
- Use when the work is better handled by that native specialization after this imported skill establishes context.@content-marketer
- Use when the work is better handled by that native specialization after this imported skill establishes context.@content-strategy
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
| Resource family | What it gives the reviewer | Example path |
|---|---|---|
| copied reference notes, guides, or background material from upstream | |
| worked examples or reusable prompts copied from upstream | |
| upstream helper scripts that change execution or validation | |
| routing or delegation notes that are genuinely part of the imported package | |
| supporting assets or schemas copied from the source package | |
- brand_guidelines.md
- content_frameworks.md
- social_media_optimization.md
- brand_voice_analyzer.py
- seo_optimizer.py
- content_calendar_template.md
Imported Reference Notes
Imported: Reference Guides
When to Use Each Reference
references/brand_guidelines.md
- Setting up new brand voice
- Ensuring consistency across content
- Training new team members
- Resolving voice/tone questions
references/content_frameworks.md
- Starting any new content piece
- Structuring different content types
- Creating content templates
- Planning content repurposing
references/social_media_optimization.md
- Platform-specific optimization
- Hashtag strategy development
- Understanding algorithm factors
- Setting up analytics tracking
Imported: Key Scripts
brand_voice_analyzer.py
Analyzes text content for voice characteristics, readability, and consistency.
Usage:
python scripts/brand_voice_analyzer.py <file> [json|text]
Returns:
- Voice profile (formality, tone, perspective)
- Readability score
- Sentence structure analysis
- Improvement recommendations
seo_optimizer.py
Analyzes content for SEO optimization and provides actionable recommendations.
Usage:
python scripts/seo_optimizer.py <file> [primary_keyword] [secondary_keywords]
Returns:
- SEO score (0-100)
- Keyword density analysis
- Structure assessment
- Meta tag suggestions
- Specific optimization recommendations
Imported: Performance Metrics
Track these KPIs for content success:
Content Metrics
- Organic traffic growth
- Average time on page
- Bounce rate
- Social shares
- Backlinks earned
Engagement Metrics
- Comments and discussions
- Email click-through rates
- Social media engagement rate
- Content downloads
- Form submissions
Business Metrics
- Leads generated
- Conversion rate
- Customer acquisition cost
- Revenue attribution
- ROI per content piece
Imported: Integration Points
This skill works best with:
- Analytics platforms (Google Analytics, social media insights)
- SEO tools (for keyword research)
- Design tools (for visual content)
- Scheduling platforms (for content distribution)
- Email marketing systems (for newsletter content)
Imported: Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.