Social Media Setup

What it is: the business on the channels it can actually sustain - Facebook Page, LinkedIn company page, TikTok - with each profile completed, each channel's format and limits recorded, and a content cadence small enough to keep.

Overview

Works out the smallest useful channel set for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a content calendar. The channel and content register - CSV, SQL DDL, JSON Schema, Notion mapping - is produced on request, from one field list so the four cannot drift apart.

Layer: Layer 6: Engage. Fits: Starter stage. Table code: n/a.

The rule this table exists to enforce: a channel and a post are different rows, and a Row Type discriminator keeps them apart. A channel is a permanent configuration; a post is a dated event that is published once. Merging them means the channel settings change every time something is posted, and the profile checklist can never be marked complete against a post.

The second rule: the cadence has to be one the business can keep with the people it has. A daily plan on one founder is a plan that stops in week three, and an abandoned account is worse than no account. Two posts a week beats five a week for one month.

When to Use This Skill

• Facebook, Facebook Page, LinkedIn, LinkedIn company page, TikTok
• social media setup, profiles, bios, avatars, cover images
• "we are not on social media", "we should be on Instagram"
• content calendar, posting schedule, what to post
• "nobody engages with our posts"
• brand voice on social, tone of voice
• social profiles for recruitment, or for a local customer base

Do not use it for: the link page every bio points to (linktree-link-hub), the presentation (presentation-deck), a paid advertising campaign, or a content marketing or guest-posting plan (seo-directory-backlinks for the citation side).

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

• "set up" / "start" / "we are not on" -> artifacts wanted; go to Step 2.
• "we have them, nothing happens" / "fix" -> something exists; capture the current state, then Step 2.
• "which platform should we be on" / "review" -> a decision question, not a build.
• "audit" / "check" -> a check, not a build.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: What is the business called, and what does one line of it actually do?

Step 2 - Ask only what is missing

Treat ambiguous replies as unanswered and ask which explicit option the user means. Record unknown values as Unknown; Unknown is not zero. A record must not be Done when a required check fails.

Skip anything already answered. Ask the rest one at a time, and stop as soon as the remaining answers would not change the channel set.

• Audience - Who are the customers - local walk-ins, online, business buyers, job candidates, or a mix? / Where are they already - which platform do they use?
• Current - Are any accounts open, even dormant? / Who has the logins, and are they personal accounts or business pages? / Any customer or staff photos already used?
• Capacity - Who will post, and how many hours a week are genuinely available? / Is there anyone who can respond to a comment within an hour?
• Content - Is there anything to post - finished work, stock, the team, an opening, a tip, an offer? / Can photos be taken on a phone at the premises? / Is anyone willing to be on camera?
• Purpose - What is the channel for - enquiries, recruitment, credibility, community, or advertising? / Is there a website to send people to yet?

Never invent an answer. Handles, follower counts, engagement rates, post volumes, platform names, account URLs and metrics the user has not supplied are Unknown. A follower count is a measurement, never an estimate.

Step 3 - Hold the internal context

module: social-media-setup
intent: null            # set up | fix | review | report | import
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Audience": null
  "Current": null
  "Capacity": null
  "Content": null
  "Purpose": null
requested_outputs: []
confirmed_facts: []
open_questions: []

…