Editorial Config

Editorial Config — Context Loader

Load all available client context before generating any output. Call the client-context skill, then apply editorial interpretation to what's found. This is the bridge between raw documents and actionable editorial intelligence.

Loading Sequence

1. Call client-context skill
   → Reads ~~docs folder
   → Extracts brand, audience, competitor, pillar, performance, operational context
   → Checks active connectors (~~email, ~~crm, ~~calendar, ~~assets)
   → Returns status: 🟢 Configured / 🟡 Partial / ⚪ No client loaded

2. Apply editorial interpretation layer (this skill)
   → From competitor documents: build competitors[] with genuine strengths and weaknesses
   → From strategy/pillar docs: build pillars[] with current health assessment
   → From audience docs: build segments[] with content preference and funnel stage
   → From past content: extract history.biggest_wins and approaches_tested
   → From briefs/calendar: extract constraints (cadence, team, seasonal holds)
   → From performance reports: extract goals.metrics_that_matter
   → From brand guide: extract voice rules, vocabulary, tone adaptation

3. Show status header (one line — never narrate the loading process)

Status Header

🟢 [{client name}] | Drive: [{folder}] | Competitors: {N} | Pillars: {N} | Segments: {N}
🟡 [{client name}] | Drive: [{folder}] | Partial — [{what's missing and effect on output}]
⚪ No client loaded — working from what you provide. Run /setup to connect your docs.

Interpretation Rules by Domain

Competitors

Brand Voice

Voice Adaptation by Command

Different commands need different emphasis from the same voice:

Content Pillars

Pillar Health Assessment Criteria

Audience Segments

Email Context

Email Benchmarks (Use Only When No Real Data Available)

Always label these as "industry benchmarks" when used. Never present them as if they're the client's data.

Content History

Operational Constraints

Team Size Heuristics

When team size isn't explicitly stated, use these signals:

When Documents Are Ambiguous

Never Do

• Never ask the user to re-enter information that's in their Drive documents
• Never use generic "your competitors probably..." when Drive docs have real competitors
• Never recommend approaches that past content shows were tried and dropped
• Never narrate the loading process — show the status header only
• Never block on missing context — flag what's missing and continue
• Never present industry benchmarks as if they're the client's real data
• Never make up competitors, segments, or pillars that aren't in the documents
• Never apply voice rules from one client to another client's context

Cross-Skill Dependencies

• Calls: client-context (reads Drive, extracts raw context)
• Called by: All commands as the first step
• Feeds into: content-strategist (pillar health, gaps, history)
• Feeds into: competitive-intel (competitor list, strengths, weaknesses)
• Feeds into: calendar-planner (constraints, cadence, seasonal data)