feat(skills): add brand voice and network ops lanes

.agents/skills/brand-voice/SKILL.md

@@ -0,0 +1,97 @@
+---
+name: brand-voice
+description: Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.
+origin: ECC
+---
+
+# Brand Voice
+
+Build a durable voice profile from real source material, then use that profile everywhere instead of re-deriving style from scratch or defaulting to generic AI copy.
+
+## When to Activate
+
+- the user wants content or outreach in a specific voice
+- writing for X, LinkedIn, email, launch posts, threads, or product updates
+- adapting a known author's tone across channels
+- the existing content lane needs a reusable style system instead of one-off mimicry
+
+## Source Priority
+
+Use the strongest real source set available, in this order:
+
+1. recent original X posts and threads
+2. articles, essays, memos, launch notes, or newsletters
+3. real outbound emails or DMs that worked
+4. product docs, changelogs, README framing, and site copy
+
+Do not use generic platform exemplars as source material.
+
+## Collection Workflow
+
+1. Gather 5 to 20 representative samples when available.
+2. Prefer recent material over old material unless the user says the older writing is more canonical.
+3. Separate "public launch voice" from "private working voice" if the source set clearly splits.
+4. If live X access is available, use `x-api` to pull recent original posts before drafting.
+5. If site copy matters, include the current ECC landing page and repo/plugin framing.
+
+## What to Extract
+
+- rhythm and sentence length
+- compression vs explanation
+- capitalization norms
+- parenthetical use
+- question frequency and purpose
+- how sharply claims are made
+- how often numbers, mechanisms, or receipts show up
+- how transitions work
+- what the author never does
+
+## Output Contract
+
+Produce a reusable `VOICE PROFILE` block that downstream skills can consume directly. Use the schema in [references/voice-profile-schema.md](references/voice-profile-schema.md).
+
+Keep the profile structured and short enough to reuse in session context. The point is not literary criticism. The point is operational reuse.
+
+## Affaan / ECC Defaults
+
+If the user wants Affaan / ECC voice and live sources are thin, start here unless newer source material overrides it:
+
+- direct, compressed, concrete
+- specifics, mechanisms, receipts, and numbers beat adjectives
+- parentheticals are for qualification, narrowing, or over-clarification
+- capitalization is conventional unless there is a real reason to break it
+- questions are rare and should not be used as bait
+- tone can be sharp, blunt, skeptical, or dry
+- transitions should feel earned, not smoothed over
+
+## Hard Bans
+
+Delete and rewrite any of these:
+
+- fake curiosity hooks
+- "not X, just Y"
+- "no fluff"
+- forced lowercase
+- LinkedIn thought-leader cadence
+- bait questions
+- "Excited to share"
+- generic founder-journey filler
+- corny parentheticals
+
+## Persistence Rules
+
+- Reuse the latest confirmed `VOICE PROFILE` across related tasks in the same session.
+- If the user asks for a durable artifact, save the profile in the requested workspace location or memory surface.
+- Do not create repo-tracked files that store personal voice fingerprints unless the user explicitly asks for that.
+
+## Downstream Use
+
+Use this skill before or inside:
+
+- `content-engine`
+- `crosspost`
+- `lead-intelligence`
+- article or launch writing
+- cold or warm outbound across X, LinkedIn, and email
+
+If another skill already has a partial voice capture section, this skill is the canonical source of truth.

.agents/skills/brand-voice/references/voice-profile-schema.md

@@ -0,0 +1,55 @@
+# Voice Profile Schema
+
+Use this exact structure when building a reusable voice profile:
+
+```text
+VOICE PROFILE
+=============
+Author:
+Goal:
+Confidence:
+
+Source Set
+- source 1
+- source 2
+- source 3
+
+Rhythm
+- short note on sentence length, pacing, and fragmentation
+
+Compression
+- how dense or explanatory the writing is
+
+Capitalization
+- conventional, mixed, or situational
+
+Parentheticals
+- how they are used and how they are not used
+
+Question Use
+- rare, frequent, rhetorical, direct, or mostly absent
+
+Claim Style
+- how claims are framed, supported, and sharpened
+
+Preferred Moves
+- concrete moves the author does use
+
+Banned Moves
+- specific patterns the author does not use
+
+CTA Rules
+- how, when, or whether to close with asks
+
+Channel Notes
+- X:
+- LinkedIn:
+- Email:
+```
+
+Guidelines:
+
+- Keep the profile concrete and source-backed.
+- Use short bullets, not essay paragraphs.
+- Every banned move should be observable in the source set or explicitly requested by the user.
+- If the source set conflicts, call out the split instead of averaging it into mush.

.agents/skills/content-engine/SKILL.md

@@ -36,27 +36,24 @@ Before drafting, identify the source set:
 - prior posts from the same author
 
 If the user wants a specific voice, build a voice profile from real examples before writing.
+Use `brand-voice` as the canonical workflow when voice consistency matters across more than one output.
 
 ## Voice Capture Workflow
 
-Collect 5 to 20 examples when available. Good sources:
-- articles or essays
-- X posts or threads
-- docs or release notes
-- newsletters
-- previous launch posts
+Run `brand-voice` first when:
 
-If live X access is available, use `x-api` to pull recent original posts before drafting. If not, use the examples already provided or present in the repo.
+- there are multiple downstream outputs
+- the user explicitly cares about writing style
+- the content is launch, outreach, or reputation-sensitive
 
-Extract and write down:
-- sentence length and rhythm
-- how compressed or explanatory the writing is
-- whether capitalization is conventional, mixed, or situational
-- how parentheses are used
-- whether the writer uses fragments, lists, or abrupt pivots
-- how often the writer asks questions
-- how sharp, formal, opinionated, or dry the voice is
-- what the writer never does
+At minimum, produce a compact `VOICE PROFILE` covering:
+- rhythm
+- compression
+- capitalization
+- parenthetical use
+- question use
+- preferred moves
+- banned moves
 
 Do not start drafting until the voice profile is clear enough to enforce.
 
@@ -148,3 +145,9 @@ Before delivering:
 - no fake engagement bait remains
 - no duplicated copy across platforms unless requested
 - any CTA is earned and user-approved
+
+## Related Skills
+
+- `brand-voice` for source-derived voice profiles
+- `crosspost` for platform-specific distribution
+- `x-api` for sourcing recent posts and publishing approved X output

.agents/skills/crosspost/SKILL.md

@@ -37,6 +37,8 @@ Use `content-engine` first if the source still needs voice shaping.
 
 ### Step 2: Capture the Voice Fingerprint
 
+Run `brand-voice` first if the source voice is not already captured in the current session.
+
 Before adapting, note:
 - how blunt or explanatory the source is
 - whether the source uses fragments, lists, or longer transitions
@@ -110,5 +112,6 @@ Before delivering:
 
 ## Related Skills
 
+- `brand-voice` for reusable source-derived voice capture
 - `content-engine` for voice capture and source shaping
 - `x-api` for X publishing workflows

.agents/skills/x-api/SKILL.md

@@ -19,7 +19,7 @@ Programmatic interaction with X (Twitter) for posting, reading, searching, and a
 
 ## Authentication
 
-### OAuth 2.0 (App-Only / User Context)
+### OAuth 2.0 Bearer Token (App-Only)
 
 Best for: read-heavy operations, search, public data.
 
@@ -46,25 +46,27 @@ tweets = resp.json()
 
 ### OAuth 1.0a (User Context)
 
-Required for: posting tweets, managing account, DMs.
+Required for: posting tweets, managing account, DMs, and any write flow.
 
 ```bash
 # Environment setup — source before use
-export X_API_KEY="your-api-key"
-export X_API_SECRET="your-api-secret"
+export X_CONSUMER_KEY="your-consumer-key"
+export X_CONSUMER_SECRET="your-consumer-secret"
 export X_ACCESS_TOKEN="your-access-token"
-export X_ACCESS_SECRET="your-access-secret"
+export X_ACCESS_TOKEN_SECRET="your-access-token-secret"
 ```
 
+Legacy aliases such as `X_API_KEY`, `X_API_SECRET`, and `X_ACCESS_SECRET` may exist in older setups. Prefer the `X_CONSUMER_*` and `X_ACCESS_TOKEN_SECRET` names when documenting or wiring new flows.
+
 ```python
 import os
 from requests_oauthlib import OAuth1Session
 
 oauth = OAuth1Session(
-    os.environ["X_API_KEY"],
-    client_secret=os.environ["X_API_SECRET"],
+    os.environ["X_CONSUMER_KEY"],
+    client_secret=os.environ["X_CONSUMER_SECRET"],
     resource_owner_key=os.environ["X_ACCESS_TOKEN"],
-    resource_owner_secret=os.environ["X_ACCESS_SECRET"],
+    resource_owner_secret=os.environ["X_ACCESS_TOKEN_SECRET"],
 )
 ```
 
@@ -92,7 +94,6 @@ def post_thread(oauth, tweets: list[str]) -> list[str]:
         if reply_to:
             payload["reply"] = {"in_reply_to_tweet_id": reply_to}
         resp = oauth.post("https://api.x.com/2/tweets", json=payload)
-        resp.raise_for_status()
         tweet_id = resp.json()["data"]["id"]
         ids.append(tweet_id)
         reply_to = tweet_id
@@ -126,6 +127,21 @@ resp = requests.get(
 )
 ```
 
+### Pull Recent Original Posts for Voice Modeling
+
+```python
+resp = requests.get(
+    "https://api.x.com/2/tweets/search/recent",
+    headers=headers,
+    params={
+        "query": "from:affaanmustafa -is:retweet -is:reply",
+        "max_results": 25,
+        "tweet.fields": "created_at,public_metrics",
+    }
+)
+voice_samples = resp.json()
+```
+
 ### Get User by Username
 
 ```python
@@ -155,17 +171,12 @@ resp = oauth.post(
 )
 ```
 
-## Rate Limits Reference
+## Rate Limits
 
-| Endpoint | Limit | Window |
-|----------|-------|--------|
-| POST /2/tweets | 200 | 15 min |
-| GET /2/tweets/search/recent | 450 | 15 min |
-| GET /2/users/:id/tweets | 1500 | 15 min |
-| GET /2/users/by/username | 300 | 15 min |
-| POST media/upload | 415 | 15 min |
-
-Always check `x-rate-limit-remaining` and `x-rate-limit-reset` headers.
+X API rate limits vary by endpoint, auth method, and account tier, and they change over time. Always:
+- Check the current X developer docs before hardcoding assumptions
+- Read `x-rate-limit-remaining` and `x-rate-limit-reset` headers at runtime
+- Back off automatically instead of relying on static tables in code
 
 ```python
 import time
@@ -202,13 +213,18 @@ else:
 
 ## Integration with Content Engine
 
-Use `content-engine` skill to generate platform-native content, then post via X API:
-1. Generate content with content-engine (X platform format)
-2. Validate length (280 chars for single tweet)
-3. Post via X API using patterns above
-4. Track engagement via public_metrics
+Use `brand-voice` plus `content-engine` to generate platform-native content, then post via X API:
+1. Pull recent original posts when voice matching matters
+2. Build or reuse a `VOICE PROFILE`
+3. Generate content with `content-engine` in X-native format
+4. Validate length and thread structure
+5. Return the draft for approval unless the user explicitly asked to post now
+6. Post via X API only after approval
+7. Track engagement via public_metrics
 
 ## Related Skills
 
+- `brand-voice` — Build a reusable voice profile from real X and site/source material
 - `content-engine` — Generate platform-native content for X
 - `crosspost` — Distribute content across X, LinkedIn, and other platforms
+- `connections-optimizer` — Reorganize the X graph before drafting network-driven outreach