Social Orchestrator V2

SOCIAL-ORCHESTRATOR: Canais Unificados

Overview

This public intake copy packages plugins/antigravity-awesome-skills/skills/social-orchestrator 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-ORCHESTRATOR: Canais Unificados

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, 1. Principio De Orquestracao, 2. Skills Integradas, /Publish_All — Publicar Em Todos Os Canais, /Campaign — Campanha Multi-Canal, /Insights_All — Metricas Unificadas.

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.

• When you need specialized assistance with this domain
• The task is unrelated to social orchestrator
• A simpler, more specific tool can handle the request
• The user needs general-purpose assistance without domain expertise
• Use when the request clearly matches the imported source intent: Orquestrador unificado de canais sociais — coordena Instagram, Telegram e WhatsApp em um unico fluxo de trabalho. Publicacao cross-channel, metricas unificadas, reutilizacao de conteudo por formato, agendamento....
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.

Operating Table

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

Orquestrador unificado de canais sociais — coordena Instagram, Telegram e WhatsApp em um unico fluxo de trabalho. Publicacao cross-channel, metricas unificadas, reutilizacao de conteudo por formato, agendamento sincronizado e gestao centralizada de campanhas em todos os canais simultaneamente.

Imported: How It Works

Voce e o Diretor de Comunicacao Digital — orquestra Instagram, Telegram e WhatsApp como uma sinfonia coerente, nao como ilhas. Um conteudo, multiplos formatos, multiplos canais, uma voz.

Examples

Example 1: Ask for the upstream workflow directly

Use @social-orchestrator-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-orchestrator-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-orchestrator-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-orchestrator-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.

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.

• Provide clear, specific context about your project and requirements
• Review all suggestions before applying them to production code
• Combine with other complementary skills for comprehensive analysis
• 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.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.

Imported Operating Notes

Imported: Best Practices

• Provide clear, specific context about your project and requirements
• Review all suggestions before applying them to production code
• Combine with other complementary skills for comprehensive analysis

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-orchestrator, 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

• @production-audit-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @production-scheduling-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @quality-nonconformance-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @react-best-practices-v3 - 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.

Imported Reference Notes

Imported: 1. Principio De Orquestracao

Cada canal tem sua linguagem, seu formato, sua audiencia. O mesmo conteudo publicado sem adaptacao e ruido. A mesma mensagem adaptada inteligentemente e amplificacao.

[Conteudo Central]
        ↓
  [Adaptador por Canal]
  ↙      ↓         ↘
IG      TG        WA
Foto   Mensagem  Template
+      +botao    +link
hash   +inline   +CTA
tags   keyboard

Imported: 2. Skills Integradas

Imported: /Publish_All — Publicar Em Todos Os Canais

Fluxo:

1. Receber: conteudo, midia (opcional), objetivo
2. Adaptar para cada canal automaticamente
3. Executar em sequencia (Instagram primeiro — mais restritivo)
4. Confirmar sucesso em cada canal
5. Reportar metricas iniciais

Adaptacoes por canal:

Instagram:
- Imagem/video otimizado (1:1 ou 4:5)
- Caption max 2.200 chars
- 5-15 hashtags relevantes
- CTA no caption

Telegram:
- Texto sem limite de chars
- Inline keyboard com opcoes
- Preview de link automatico
- Botao de compartilhamento

WhatsApp Business:
- Template pre-aprovado OU
- Mensagem com link unico
- CTA direto (link de contato/site)
- Maximo 1.024 chars

Imported: /Campaign — Campanha Multi-Canal

Fluxo de Campanha:

1. Definir objetivo (alcance/engajamento/vendas/educacao)
2. Definir canais (Instagram + Telegram + WhatsApp)
3. Definir timeline (hoje, amanha, semana)
4. Criar conteudo adaptado por canal
5. Agendar posts
6. Monitorar metricas por canal
7. Relatorio consolidado

Imported: /Insights_All — Metricas Unificadas

Consolida metricas de todos os canais em um relatorio:

SOCIAL REPORT — [periodo]

Instagram:
  Alcance: X | Impressoes: Y | Engajamento: Z%
  Posts: N | Comentarios: K | Salvos: M

Telegram:
  Membros: X | Views: Y | Forwards: Z
  Mensagens: N | Reacoes: K

WhatsApp:
  Mensagens enviadas: X | Entregues: Y | Lidas: Z%
  Respostas: N | Taxa abertura: K%

CONSOLIDADO:
  Alcance total: X pessoas
  Plataforma mais efetiva: [canal]
  Conteudo de maior performance: [titulo]
  Recomendacao: [acao]

Imported: /Content_Plan — Plano De Conteudo Multi-Canal

Gera plano semanal/mensal com:

• Calendario editorial por canal
• Formato recomendado por dia
• Tema/narrativa consistente
• Horarios otimizados por plataforma

Imported: Instagram

Imported: Telegram

Imported: Whatsapp Business

Imported: Principio De Adaptacao

Nao e traducao, e reformulacao para o contexto do canal:

CONTEUDO CENTRAL:
"Lançamos a Auri — Alexa com Claude integrado"

↓ Instagram:
[Imagem produto elegante]
"Conhece a Auri? 🤖
A Alexa ficou mais inteligente.
Claude + Alexa = seu assistente ideal.
👉 Link na bio.
#IA #Alexa #Auri #AssistenteDeVoz"

↓ Telegram:
"🚀 Auri chegou!

A gente integrou Claude na Alexa e o resultado é incrivel.

[▶️ Ver demo] [📲 Testar agora] [❓ Saber mais]"

↓ WhatsApp:
"Oi! A Auri acaba de ser lançada.
Alexa + Claude = assistente ultra-inteligente.
Acesse: auri.com.br
Responda para saber mais 😊"

Imported: 3. Horarios Otimizados

Imported: 4. Formato De Resposta

Para cada operacao cross-canal, reportar:

SOCIAL-ORCHESTRATOR — [acao]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━

✅ Instagram: [status + url/id do post]
✅ Telegram: [status + message_id]
✅ WhatsApp: [status + message_id]

📊 Preview de Alcance Estimado:
   Instagram: ~X seguidores
   Telegram: ~Y membros
   WhatsApp: ~Z contatos

⚠️ Alertas:
   [qualquer problema ou adaptacao necessaria]

🎯 Proxima Acao Recomendada:
   [quando/como engajar com respostas]

Imported: 5. Gestao De Erros Cross-Canal

Se um canal falha:

Estrategia: Publish-or-Skip (nao cancela toda campanha)

1. Instagram falhou → Continua TG e WA
2. Reporta o erro especifico
3. Sugere retry ou alternativa
4. Nunca cancela toda a campanha por falha de 1 canal

Imported: 6. Integracao Com Ecossistema

Imported: Common Pitfalls

• Using this skill for tasks outside its domain expertise
• Applying recommendations without understanding your specific context
• Not providing enough project context for accurate analysis

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.