diegosouzapw/awesome-omni-skills

Social Media Strategist and Content Writer

Overview

This public intake copy packages plugins/antigravity-awesome-skills/skills/social-post-writer-seo 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.

Social Media Strategist and Content Writer

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How It Works, Prompt Template, Limitations, Security & Safety Notes, Common Pitfalls.

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 you need a clear, engaging, and accurate social media post for Instagram, LinkedIn, or Facebook.
• Use it to transform topics and keywords into audience-focused content with platform-native structure.
• Use when the request clearly matches the imported source intent: Social Media Strategist and Content Writer. Creates clear, engaging social media posts for Instagram, LinkedIn, and Facebook.
• 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.

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	SKILL.md	Starts with the smallest copied file that materially changes execution
Supporting context	SKILL.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.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Overview

This skill is designed to help users create high-quality, engaging, and platform-optimized social media content. It focuses on clarity, readability, and platform-specific nuances for Instagram, LinkedIn, and Facebook.

Imported: How It Works

Step 1: Input Gathering

The skill starts by collecting essential details like the topic, primary keyword, target audience, and the specific social media platform.

Step 2: Content Generation

Based on the inputs, it follows strict writing rules to ensure simplicity, factual accuracy, and engagement. It structures the post with a hook, context, value, and a call to action.

Step 3: Platform Optimization

The output is tailored for the selected platform, adjusting emoji density and tone (e.g., more professional for LinkedIn, more visual/casual for Instagram).

Examples

Example 1: Ask for the upstream workflow directly

Use @social-post-writer-seo-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 @social-post-writer-seo-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 @social-post-writer-seo-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 @social-post-writer-seo-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: Examples

Example: New Product Launch

• Topic: Solar Powered Coffee Mug
• Keyword: eco-friendly coffee
• Target: Commuters
• Platform: Instagram
• Tone: Insightful

Output: ☕️ Your morning coffee just got a clean energy upgrade! Meet SolMug, a solar powered coffee mug concept for busy commutes. It is designed to keep your drink warm without adding another charger to your bag. A small change for your morning routine, with sustainability in mind. Check the link in bio to pre-order! #ecofriendly #coffee #sustainability #tech #morningroutine

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 include a "Hook" in the first line to capture attention.
• ✅ Use line breaks frequently to make the post scannable on mobile.
• ✅ Tailor the tone: LinkedIn should be more professional, Instagram more visual/energetic.
• ❌ Avoid using more than 10 hashtags; it can look like spam.
• ❌ Never guess facts; if info isn't provided, stick to general industry knowledge.
• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.

Imported Operating Notes

Imported: Best Practices

• ✅ Always include a "Hook" in the first line to capture attention.
• ✅ Use line breaks frequently to make the post scannable on mobile.
• ✅ Tailor the tone: LinkedIn should be more professional, Instagram more visual/energetic.
• ❌ Avoid using more than 10 hashtags; it can look like spam.
• ❌ Never guess facts; if info isn't provided, stick to general industry knowledge.

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/social-post-writer-seo, 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

• @ab-test-setup-v4 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @analytics-tracking-v4 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @app-store-optimization-v4 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @content-creator-v4 - 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/n/a
examples	worked examples or reusable prompts copied from upstream	examples/n/a
scripts	upstream helper scripts that change execution or validation	scripts/n/a
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	assets/n/a

Imported Reference Notes

Imported: Prompt Template

Your task is to create a clear, engaging, and accurate social media post that works for a global audience on platforms like Instagram, LinkedIn, and Facebook.

INPUT:

• Topic: {Insert Topic}
• Primary Keyword: {Insert Keyword}
• Target Audience: {Global audience or specific group}
• Platform: {Instagram or LinkedIn or Facebook}
• Tone: {Professional or simple or storytelling or insightful}
• Region Focus: {Global or specific region if needed}
• Brand: {Optional name}

GOAL:

Create a post that is easy to understand, useful, and encourages engagement.

WRITING RULES:

• Use simple and clear English
• Avoid slang and complex words
• Avoid assumptions that are not verified
• Do not create or guess facts
• Only include information that is general, widely known, or provided in the input
• Keep sentences short
• Use line breaks for readability
• Do not use long paragraph
• Use emojis correctly for each platform (fewer for LinkedIn, more for Instagram)
• Make it about the reader, not just the brand
• Provide a clear call to action at the end
• Include 5-8 relevant hashtags

STRUCTURE:

1. Hook: One strong line.
2. Main Context: Simple and clear.
3. Value/Insight: Useful information.
4. Call to Action: Check the comment section or follow.
5. Hashtags: 5-8 relevant tags.

Imported: Limitations

• This skill does not generate image or video assets.
• It requires manual copy-pasting to the respective social media platforms.
• It cannot schedule or post content directly to social media accounts.

Imported: Security & Safety Notes

• This skill only generates text content and does not interact with system APIs or run shell commands.
• Ensure any links included in the generated content are verified by the user before posting.

Imported: Common Pitfalls

• Problem: Post feels too "salesy". Solution: Focus more on the "Value/Insight" section to provide helpful info before the CTA.
• Problem: Low engagement on LinkedIn. Solution: Reduce emoji count and ensure the "Hook" addresses a professional pain point.