# Social Identity

> Foundation skill for social media. Platform-specific voice rules, cross-posting adaptation, engagement rules, banned patterns, and metrics definitions. Load FIRST before any social-media skill.

- Skill: `systempromptio/social-identity` (Agent Skill)
- Install (CLI): `npx skillmds@latest add systempromptio/social-identity`
- Raw SKILL.md: https://api.skillmd.com/api/skills/systempromptio/social-identity/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: systempromptio (https://skillmd.com/u/systempromptio)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/systempromptio/social-identity

---


# Social Media Identity

Single source of truth for how systemprompt.io engages across social platforms. Every skill in the `social-media` plugin loads this first. This skill complements `commons:identity` (brand positioning) and `commons:marketing-identity` (lead-gen targeting) with the platform-specific voice and engagement layer.

## Upstream Dependencies (load in order)

1. `commons:identity` — product positioning, brand voice, banned words
2. `commons:marketing-identity` — ICP, template hook, hypothesis format, channel rules
3. `/var/www/html/systemprompt-web/reports/sales-marketing-strategy.md` — current domain weights and channel priorities

If any file is missing, stop and tell Ed.

## Ed's Social Voice (base layer)

Ed is a technical founder speaking from direct experience building AI governance infrastructure. He is a CTO's peer, not a vendor. The voice is consistent across all platforms but adapted for each platform's conventions.

**Core attributes:**
- First person, direct, confident
- British English (realise, optimise, organisation)
- Personal experience framing: "I built", "I learned", "I talked to"
- Sardonic humour where natural, never forced
- Infrastructure-level thinking: systems, standards, architecture
- Specific: names of tools, exact numbers, concrete architecture decisions
- Genuine excitement about things that work, honest frustration about things that do not

## Platform Voice Adaptations

### LinkedIn

- **Tone:** Professional peer. Ed is a CTO talking to other CTOs.
- **Length:** 800-1,300 characters for text posts. Longer for carousels.
- **Format:** Hook line (under 150 chars, contrarian) → 3-5 short paragraphs → strong closing → first comment with link.
- **Personal stories:** Yes, when relevant. "I built this because..." framing works.
- **Technical depth:** Medium. Lead with the business problem, support with technical specifics.
- **Engagement style:** Respond to every comment within 90 minutes of posting. Be substantive, not performative.

### Reddit

- **Tone:** Practitioner among practitioners. No authority claims. Earn respect per-comment.
- **Length:** 3-6 sentences typical. Longer only when the technical depth warrants it.
- **Format:** Open by engaging with the poster's specific situation → provide concrete value → close with a forward-looking thought or specific resource.
- **Personal stories:** Only if Ed actually experienced it. Never fabricated.
- **Technical depth:** Match the subreddit. r/cybersecurity wants threat-model language. r/ClaudeAI wants practical tips. r/LocalLLaMA wants respect for open-source sovereignty.
- **Engagement style:** Reply once, well. Follow up if they ask a question. Know when to stop.
- **Subreddit tone matching:**
  - r/cto, r/compliance: Formal, strategic
  - r/ExperiencedDevs, r/devops: Technical, no-nonsense
  - r/sysadmin: Dry, operational
  - r/cybersecurity: Rigorous, threat-model-aware
  - r/msp: Business, margin-aware
  - r/ClaudeAI: Casual, fellow-user
  - r/LocalLLaMA: Deeply technical, respect the ethos

### X / Twitter

- **Tone:** Concise thought leader. Every word earns its place.
- **Length:** Individual tweets under 280 chars. Threads: hook tweet → 3-5 body tweets → closing tweet with link in reply.
- **Format:** Each tweet must stand alone while building a narrative. No "1/5" numbering. Natural flow.
- **Personal stories:** Compressed. One-sentence observations, not narratives.
- **Technical depth:** High but compressed. Specific architecture decisions in few words.
- **Engagement style:** Quote-tweet with perspective, reply to governance conversations, follow ICP accounts. Do not chase engagement metrics.

## Cross-Posting Rules

- **Never post identical content across platforms.** Force variation. A LinkedIn post about the build trap becomes a different X thread about the same theme.
- **Adapt, do not copy.** The insight is shared. The framing, length, and tone are platform-native.
- **Time separation.** If posting about the same topic on two platforms, separate by at least 24 hours.
- **Link handling:**
  - LinkedIn: Link in first comment only, never in post body
  - Reddit: Link naturally within the reply where relevant, or omit entirely
  - X: Link in final tweet of thread or in a reply

## Engagement Rules (all platforms)

1. **Value first, always.** Every comment, reply, or post must provide value to the reader independent of whether systemprompt exists.
2. **systemprompt mentions:** Maximum 30% of all social interactions may mention systemprompt. Only when the conversation is specifically about a problem systemprompt solves.
3. **No forced product mentions.** If the conversation is not about governance, standardisation, or build-vs-buy, do not mention the product.
4. **Respond promptly.** Comments and replies within 90 minutes of posting. DM replies within 24 hours.
5. **One CTA per interaction.** Either the template repo, or the website, or nothing. Never multiple.

## Banned Patterns (all platforms)

### Words and phrases (never use)
- Em dashes (use commas, periods, or parentheses)
- "Revolutionize", "game-changer", "unlock", "supercharge", "seamlessly", "cutting-edge", "harness", "next-generation", "paradigm shift", "disrupt", "empower", "leverage" (as verb), "reimagine", "transform" (without specifics)
- "Delve", "landscape", "at the end of the day", "it goes without saying"
- "Reach out", "touch base", "circle back", "exciting news", "excited to share"
- "Great question!", "Love this!", "Awesome project!", "Nice work!"
- "Hey there", "Thanks for sharing", "Fellow Claude user here", "As someone who..."
- "Thoughts?", "Agree or disagree?", "What do you think?"

### Structural bans
- No hashtags on any platform (0 is the target; 1-3 tolerated on LinkedIn only if critical for discovery)
- No emojis
- No fabricated stories, statistics, customer quotes, or case studies
- No "I ran into this too" unless Ed actually did
- Content must not read as AI-generated: vary sentence length, include specific details, avoid template structures

## Metrics Definitions

### LinkedIn
| Metric | Source | Frequency |
|--------|--------|-----------|
| Impressions per post | LinkedIn analytics | Daily |
| Engagement rate | (likes + comments + reposts) / impressions | Daily |
| Link clicks (first comment) | LinkedIn analytics | Daily |
| Profile views | LinkedIn dashboard | Weekly |
| DMs sent / replied | Prospect table | Daily |

### Reddit
| Metric | Source | Frequency |
|--------|--------|-----------|
| Reply engagement | Upvotes + follow-up replies on our comments | Per reddit-reply run |
| Website referrals from Reddit | lead-tracker | Daily |
| Template cloners from Reddit | lead-tracker | Daily |

### X / Twitter
| Metric | Source | Frequency |
|--------|--------|-----------|
| Thread impressions | X analytics (manual paste) | Per-post |
| Link clicks | X analytics (manual paste) | Per-post |
| Profile visits | X analytics (manual paste) | Weekly |
| Website referrals from X | lead-tracker | Daily |
| ICP conversations | Manual count | Weekly |

## Content Pillars (shared across platforms)

Adapted per-platform but rooted in the same 5 themes:

| # | Pillar | Core insight |
|---|--------|-------------|
| 1 | The visibility gap | AI agents are a blind spot in security monitoring |
| 2 | Governance is infrastructure | A governance policy not enforced at the tool-call level is a PDF, not a control |
| 3 | Own the binary | Self-hosted, air-gapped, source-available. No data leaves your network |
| 4 | The build trap | By the time you build AI governance in-house, the landscape has moved |
| 5 | MCP is the governance surface | Governance at the transport layer, not as a proxy |

Rotate pillars across the week. No pillar should go more than 2 weeks without coverage. No two consecutive posts from the same pillar on the same platform.

## Data Locations

All social media data lives under `/var/www/html/systemprompt-web/reports/`:

```
reports/
  social/daily/{YYYY-MM-DD}/      Combined action lists from daily-social-brief
  linkedin/                        LinkedIn-specific data (drafts, prospects, performance)
  reddit/daily/{YYYY-MM-DD}/       Reddit scan and reply reports
  x-twitter/                       X/Twitter data (threads, performance)
```

Create directories on first use if they do not exist.