📣 smm — Organic Social Department

One head skill for organic social. Earn attention by being worth following, not by shouting louder. Every mode starts from the platform's native behavior (what the algorithm rewards) and the audience's actual reason to follow. Volume without a point of view is invisible. Consistency beats virality.

Modes

Every invocation resolves to exactly one mode. Match the request, then load only the matched reference:

Only the resolved mode's reference is loaded — the rest stay on disk, saving tokens on every run.

Support references (load on topic)

Loadable by topic; also routable as /smm-<file> commands (not separate routed modes):

• social-intel.md

When to Use

• Designing or auditing an organic social strategy for a brand.
• Building an editorial calendar and posting cadence.
• Writing platform-native posts, captions, and hooks.
• Managing comments, DMs, and community engagement.
• Running influencer collaborations or a UGC pipeline.
• Growing an X (Twitter) account from cold start through monetization.
• Reporting on social performance and iterating.

Anti-Triggers

• Paid social campaigns, ad copy, and media buying → paidads.
• Long-form blog, email, or video scripts → content.
• Brand identity, social templates, and graphics → design.
• Attribution and cross-channel dashboards → analytics.

Quick Reference

Platform fit ladder (decide before any mode)

Rule: two platforms done natively beats six done badly. Pick where the audience already spends attention.

Verification gate (every mode)

• Every post maps to a stated objective and audience.
• Native format respected (aspect ratio, length, hook timing, hashtag norms).
• Community responses within the SLA; no unanswered high-intent comment.
• Metrics tied to a business outcome, not vanity counts.

Suite contracts

• Creative assets (templates, graphics) → design.
• Long-form source content to repurpose → content.
• Paid amplification of proven organic winners → paidads.

Procedure

1. Intake. establish which platforms matter, who the audience is, and what business outcome social must drive — before producing a single post; an unbounded 'be everywhere' plan fails.
2. Resolve the mode. Match the request against the mode table; exactly one mode. Ambiguous → ask one question, then proceed.
3. Execute the mode playbook. Load references/<mode>.md and follow its Intake → Deliverable → Procedure → Quality gate in order.
4. Gate and deliver. Pass this file's Verification checklist plus the mode's quality gate, then deliver the artifact where the client expects it.

Pitfalls

• Cross-posting identical content everywhere — each platform punishes it.
• Chasing followers instead of the audience that buys.
• No hook in the first line/frame — the platform buries it.
• Posting volume with no point of view — forgettable and invisible.
• Ignoring comments — engagement signals drive reach and trust.
• Influencer deals without brief, disclosure, or measurement.
• Reporting vanity metrics (likes) instead of saves, shares, and traffic.

Verification

• Platform focus chosen from the ladder with rationale.
• Every planned post maps to an objective and audience.
• Formats are native to each chosen platform.
• Community SLA defined and met (high-intent comments answered).
• Content repurposed from a source asset, not invented per post.
• Metrics tie to a business outcome and feed iteration.
• Disclosure present on all paid/partnered content.