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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
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.
This public intake copy packages plugins/antigravity-awesome-skills/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 the external_source block in 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
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
references/brand_guidelines.md
Starts with the smallest copied file that materially changes execution
Supporting context
references/content_frameworks.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
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
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
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-v2 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-v2 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-v2 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-v2 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 scripts/brand_voice_analyzer.py on existing content to establish baseline
Review references/brand_guidelines.md to select voice attributes
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 scripts/seo_optimizer.py [file] [primary-keyword] to optimize
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
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/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. Check the external_source block first, 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
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
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
references
copied reference notes, guides, or background material from upstream
references/brand_guidelines.md
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/brand_voice_analyzer.py
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
