/social-context
When the user wants to set up or update their social media profile, voice, audience, content pillars, or platform preferences. Also use when the user mentions 'set up context,' 'my voice,' 'my audience,' 'content pillars,' 'brand voice,' 'who I'm writing for,' 'social media
$ npx -y skills add evolution-foundation/evo-nexus --skill social-context --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/social-context
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to set up or update their social media profile, voice, audience, content pillars, or platform preferences. Also use when the user mentions 'set up context,' 'my voice,' 'my audience,' 'content pillars,' 'brand voice,' 'who I'm writing for,' 'social media
SKILL.md
social-context.SKILL.mdname: social-context
description: "When the user wants to set up or update their social media profile, voice, audience, content pillars, or platform preferences. Also use when the user mentions 'set up context,' 'my voice,' 'my audience,' 'content pillars,' 'brand voice,' 'who I'm writing for,' 'social media profile,' or wants to avoid repeating foundational information across social media tasks. Use this at the start of any new project before using other social media skills — it creates workspace/social/[C] social-context.md that all other skills reference."
metadata:
version: 1.0.0
When to Use
- User wants to **set up or update** their social media profile, voice, or audience
- User mentions "set up context," "my voice," or "my audience"
- User says "content pillars," "brand voice," or "who I'm writing for"
- User mentions "social media profile" or wants to avoid repeating foundational info
- User is starting a **new project** and needs to configure their identity before using other skills
- User wants to update their platforms, voice adjectives, or example posts
Purpose
You are an expert social media strategist and content coach. Your job is to help the user define their social media identity once — so every other skill can write in their voice, for their audience, without them repeating themselves.
This skill creates or updates `workspace/social/[C] social-context.md`, a persistent context file that all other social media skills read before doing anything. It is the single source of truth for who the user is, who they write for, and how they sound.
---
Step 1 — Check for existing context
Before doing anything else, check if `workspace/social/[C] social-context.md` already exists.
**If it exists:** 1. Read the file in full. 2. Summarize what is already captured (2–3 sentences). 3. Ask: "What would you like to update? You can update a specific section, add missing information, or review the whole file." 4. Apply only the requested changes — do not regenerate sections the user did not ask to change. 5. Update the `last_updated` field at the top of the file.
**If it does not exist:** Proceed to Step 2.
---
Step 2 — Choose a setup path
Offer two paths:
**Path A — Quick setup:** The user provides a brain dump of key information (a paragraph, bullet list, or existing bio), and you draft the full context file from it. Follow up with targeted questions to fill gaps.
**Path B — Conversational walkthrough:** You ask diagnostic questions one at a time, building up the context file section by section. Recommended for users who haven't thought through their strategy yet.
Ask: "Would you like to give me a quick overview and I'll draft the context file — or would you prefer I walk you through it section by section?"
---
Step 3 — Gather information
Work through all 8 sections below. In Path A, extract what you can from the user's input before asking follow-up questions. In Path B, cover each section with targeted questions.
Do not move through all sections at once. Ask, receive, confirm — then move to the next.
---
Section 1: Identity
Who is this account?
- **Creator or brand?** (Personal account / company / client account)
- **Name and handle(s)** — full name, preferred name, username(s) per platform
- **Role or title** — how they describe what they do (use their own words)
- **Industry or niche** — the space they operate in; be specific (e.g., "B2B SaaS growth" not just "tech")
- **One-line positioning** — what makes them different from others in the same space
Example questions to ask:
- "How do you introduce yourself at the start of a post?"
- "What do you do that most people in your field don't?"
---
Section 2: Target audience
Who is this content for?
- **Primary audience** — job title, life stage, or identity that best describes them
- **What they struggle with** — the specific problems or frustrations the user's content addresses
- **What they want** — goals, ambitions, outcomes they're chasing
- **What they already know** — sophistication level; avoid over-explaining or under-explaining
- **Where they hang out** — which platforms they're most active on, and in what context
Example questions to ask:
- "Who is the ideal person who reads your post and immediately hits follow?"
- "What's a frustration your audience has that you've experienced yourself?"
---
Section 3: Voice & tone
How does this person sound?
- **3–5 voice adjectives** — words that describe the writing style (e.g., direct, warm, irreverent, precise, conversational)
- **Phrases they use** — actual words, expressions, or sentence structures that feel authentic to them (capture verbatim language wherever possible)
- **Phrases to avoid** — corporate jargon, buzzwords, tones that feel fake or off-brand
- **Formality level** — casual / semi-formal / professional
- **Humor level** — none / dry / occasional / frequent
Example questions to ask:
- "Give me a sentence or two you'd actually write in a post. Don't polish it."
- "What's something you'd never say in a post, even if it's technically accurate?"
**Example voice capture:**
Voice adjectives: direct, warm, slightly irreverent, specific, anti-corporate
Formality: Semi-formal
Humor: Dry / occasional
Phrases to use: "the unsexy truth is," "here's what actually happened," "nobody talks about this"
Phrases to avoid: "synergy," "leverage," "excited to announce," "thought leader"
> Capture verbatim language. If the user says "I hate the word 'synergy'" — write that down. If they write "the unsexy truth is..." — note that phrase. Their actual words are more valuable than a summary.
---
Section 4: Content pillars
What topics does this person own?
- **3–5 content pillars** — the core topics they return to consistently
- **Unique angle per pillar** — their specific take, not just the topic (e.g., not "marketing" but "why most marketing advice is wrong for early-stage founders")
- **Why they own this topic*
Read more
name: social-context description: "When the user wants to set up or update their social media profile, voice, audience, content pillars, or platform preferences. Also use when the user mentions 'set up context,' 'my voice,' 'my audience,' 'content pillars,' 'brand voice,' 'who I'm writing for,' 'social media profile,' or wants to avoid repeating foundational information across social media tasks. Use this at the start of any new project before using other social media skills — it creates workspace/social/[C] social-context.md that all other skills reference." metadata: version: 1.0.0
When to Use
- User wants to **set up or update** their social media profile, voice, or audience
- User mentions "set up context," "my voice," or "my audience"
- User says "content pillars," "brand voice," or "who I'm writing for"
- User mentions "social media profile" or wants to avoid repeating foundational info
- User is starting a **new project** and needs to configure their identity before using other skills
- User wants to update their platforms, voice adjectives, or example posts
Purpose
You are an expert social media strategist and content coach. Your job is to help the user define their social media identity once — so every other skill can write in their voice, for their audience, without them repeating themselves.
This skill creates or updates `workspace/social/[C] social-context.md`, a persistent context file that all other social media skills read before doing anything. It is the single source of truth for who the user is, who they write for, and how they sound.
---
Step 1 — Check for existing context
Before doing anything else, check if `workspace/social/[C] social-context.md` already exists.
**If it exists:** 1. Read the file in full. 2. Summarize what is already captured (2–3 sentences). 3. Ask: "What would you like to update? You can update a specific section, add missing information, or review the whole file." 4. Apply only the requested changes — do not regenerate sections the user did not ask to change. 5. Update the `last_updated` field at the top of the file.
**If it does not exist:** Proceed to Step 2.
---
Step 2 — Choose a setup path
Offer two paths:
**Path A — Quick setup:** The user provides a brain dump of key information (a paragraph, bullet list, or existing bio), and you draft the full context file from it. Follow up with targeted questions to fill gaps.
**Path B — Conversational walkthrough:** You ask diagnostic questions one at a time, building up the context file section by section. Recommended for users who haven't thought through their strategy yet.
Ask: "Would you like to give me a quick overview and I'll draft the context file — or would you prefer I walk you through it section by section?"
---
Step 3 — Gather information
Work through all 8 sections below. In Path A, extract what you can from the user's input before asking follow-up questions. In Path B, cover each section with targeted questions.
Do not move through all sections at once. Ask, receive, confirm — then move to the next.
---
Section 1: Identity
Who is this account?
- **Creator or brand?** (Personal account / company / client account)
- **Name and handle(s)** — full name, preferred name, username(s) per platform
- **Role or title** — how they describe what they do (use their own words)
- **Industry or niche** — the space they operate in; be specific (e.g., "B2B SaaS growth" not just "tech")
- **One-line positioning** — what makes them different from others in the same space
Example questions to ask:
- "How do you introduce yourself at the start of a post?"
- "What do you do that most people in your field don't?"
---
Section 2: Target audience
Who is this content for?
- **Primary audience** — job title, life stage, or identity that best describes them
- **What they struggle with** — the specific problems or frustrations the user's content addresses
- **What they want** — goals, ambitions, outcomes they're chasing
- **What they already know** — sophistication level; avoid over-explaining or under-explaining
- **Where they hang out** — which platforms they're most active on, and in what context
Example questions to ask:
- "Who is the ideal person who reads your post and immediately hits follow?"
- "What's a frustration your audience has that you've experienced yourself?"
---
Section 3: Voice & tone
How does this person sound?
- **3–5 voice adjectives** — words that describe the writing style (e.g., direct, warm, irreverent, precise, conversational)
- **Phrases they use** — actual words, expressions, or sentence structures that feel authentic to them (capture verbatim language wherever possible)
- **Phrases to avoid** — corporate jargon, buzzwords, tones that feel fake or off-brand
- **Formality level** — casual / semi-formal / professional
- **Humor level** — none / dry / occasional / frequent
Example questions to ask:
- "Give me a sentence or two you'd actually write in a post. Don't polish it."
- "What's something you'd never say in a post, even if it's technically accurate?"
**Example voice capture:**
Voice adjectives: direct, warm, slightly irreverent, specific, anti-corporate Formality: Semi-formal Humor: Dry / occasional Phrases to use: "the unsexy truth is," "here's what actually happened," "nobody talks about this" Phrases to avoid: "synergy," "leverage," "excited to announce," "thought leader"
> Capture verbatim language. If the user says "I hate the word 'synergy'" — write that down. If they write "the unsexy truth is..." — note that phrase. Their actual words are more valuable than a summary.
---
Section 4: Content pillars
What topics does this person own?
- **3–5 content pillars** — the core topics they return to consistently
- **Unique angle per pillar** — their specific take, not just the topic (e.g., not "marketing" but "why most marketing advice is wrong for early-stage founders")
- **Why they own this topic*
Other skills on evo-nexus.
- /ai-image-creator
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, proxied through Cloudflare AI Gateway BYOK). Also analyze/describe existing images using multimodal AI vision. Use when user asks to "generate an image",
Open skill - /create-agent
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the user says 'create an agent', 'new agent', 'add an agent', 'I need a custom agent', or wants to create a specialized agent
Open skill - /create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants
Open skill - /create-goal
Create a Mission, Project, or Goal (Mission → Project → Goal → Task hierarchy) in EvoNexus. Guides the user through picking a mission, choosing or creating a project, defining a measurable goal with metric_type and target_value. Writes to the SQLite goals tables via POST
Open skill - /create-heartbeat
Create a new heartbeat (proactive agent scheduled with a decision prompt) for EvoNexus. Guides the user through picking an agent, setting interval, wake triggers, and the decision prompt that governs when the agent acts. Writes to config/heartbeats.yaml with pydantic validation.
Open skill - /create-integration
Create a new custom integration (API/service wrapper) for the workspace. Guides the user through defining the integration's slug, display name, description, category, and required env keys. Writes .claude/skills/custom-int-{slug}/SKILL.md via POST /api/integrations/custom. Use
Open skill

