@heyai-rules/pilo-masterkit 2.1.0 → 3.1.0

package/.agent/skills/connections-optimizer/SKILL.md

@@ -1,189 +1,189 @@
----
-name: connections-optimizer
-description: Reorganize the user's X and LinkedIn network with review-first pruning, add/follow recommendations, and channel-specific warm outreach drafted in the user's real voice. Use when the user wants to clean up following lists, grow toward current priorities, or rebalance a social graph around higher-signal relationships.
-origin: ECC
----
-
-# Connections Optimizer
-
-Reorganize the user's network instead of treating outbound as a one-way prospecting list.
-
-This skill handles:
-
-- X following cleanup and expansion
-- LinkedIn follow and connection analysis
-- review-first prune queues
-- add and follow recommendations
-- warm-path identification
-- Apple Mail, X DM, and LinkedIn draft generation in the user's real voice
-
-## When to Activate
-
-- the user wants to prune their X following
-- the user wants to rebalance who they follow or stay connected to
-- the user says "clean up my network", "who should I unfollow", "who should I follow", "who should I reconnect with"
-- outreach quality depends on network structure, not just cold list generation
-
-## Required Inputs
-
-Collect or infer:
-
-- current priorities and active work
-- target roles, industries, geos, or ecosystems
-- platform selection: X, LinkedIn, or both
-- do-not-touch list
-- mode: `light-pass`, `default`, or `aggressive`
-
-If the user does not specify a mode, use `default`.
-
-## Tool Requirements
-
-### Preferred
-
-- `x-api` for X graph inspection and recent activity
-- `lead-intelligence` for target discovery and warm-path ranking
-- `social-graph-ranker` when the user wants bridge value scored independently of the broader lead workflow
-- Exa / deep research for person and company enrichment
-- `brand-voice` before drafting outbound
-
-### Fallbacks
-
-- browser control for LinkedIn analysis and drafting
-- browser control for X if API coverage is constrained
-- Apple Mail or Mail.app drafting via desktop automation when email is the right channel
-
-## Safety Defaults
-
-- default is review-first, never blind auto-pruning
-- X: prune only accounts the user follows, never followers
-- LinkedIn: treat 1st-degree connection removal as manual-review-first
-- do not auto-send DMs, invites, or emails
-- emit a ranked action plan and drafts before any apply step
-
-## Platform Rules
-
-### X
-
-- mutuals are stickier than one-way follows
-- non-follow-backs can be pruned more aggressively
-- heavily inactive or disappeared accounts should surface quickly
-- engagement, signal quality, and bridge value matter more than raw follower count
-
-### LinkedIn
-
-- API-first if the user actually has LinkedIn API access
-- browser workflow must work when API access is missing
-- distinguish outbound follows from accepted 1st-degree connections
-- outbound follows can be pruned more freely
-- accepted 1st-degree connections should default to review, not auto-remove
-
-## Modes
-
-### `light-pass`
-
-- prune only high-confidence low-value one-way follows
-- surface the rest for review
-- generate a small add/follow list
-
-### `default`
-
-- balanced prune queue
-- balanced keep list
-- ranked add/follow queue
-- draft warm intros or direct outreach where useful
-
-### `aggressive`
-
-- larger prune queue
-- lower tolerance for stale non-follow-backs
-- still review-gated before apply
-
-## Scoring Model
-
-Use these positive signals:
-
-- reciprocity
-- recent activity
-- alignment to current priorities
-- network bridge value
-- role relevance
-- real engagement history
-- recent presence and responsiveness
-
-Use these negative signals:
-
-- disappeared or abandoned account
-- stale one-way follow
-- off-priority topic cluster
-- low-value noise
-- repeated non-response
-- no follow-back when many better replacements exist
-
-Mutuals and real warm-path bridges should be penalized less aggressively than one-way follows.
-
-## Workflow
-
-1. Capture priorities, do-not-touch constraints, and selected platforms.
-2. Pull the current following / connection inventory.
-3. Score prune candidates with explicit reasons.
-4. Score keep candidates with explicit reasons.
-5. Use `lead-intelligence` plus research surfaces to rank expansion candidates.
-6. Match the right channel:
-   - X DM for warm, fast social touch points
-   - LinkedIn message for professional graph adjacency
-   - Apple Mail draft for higher-context intros or outreach
-7. Run `brand-voice` before drafting messages.
-8. Return a review pack before any apply step.
-
-## Review Pack Format
-
-```text
-CONNECTIONS OPTIMIZER REPORT
-============================
-
-Mode:
-Platforms:
-Priority Set:
-
-Prune Queue
-- handle / profile
-  reason:
-  confidence:
-  action:
-
-Review Queue
-- handle / profile
-  reason:
-  risk:
-
-Keep / Protect
-- handle / profile
-  bridge value:
-
-Add / Follow Targets
-- person
-  why now:
-  warm path:
-  preferred channel:
-
-Drafts
-- X DM:
-- LinkedIn:
-- Apple Mail:
-```
-
-## Outbound Rules
-
-- Default email path is Apple Mail / Mail.app draft creation.
-- Do not send automatically.
-- Choose the channel based on warmth, relevance, and context depth.
-- Do not force a DM when an email or no outreach is the right move.
-- Drafts should sound like the user, not like automated sales copy.
-
-## Related Skills
-
-- `brand-voice` for the reusable voice profile
-- `social-graph-ranker` for the standalone bridge-scoring and warm-path math
-- `lead-intelligence` for weighted target and warm-path discovery
-- `x-api` for X graph access, drafting, and optional apply flows
-- `content-engine` when the user also wants public launch content around network moves
+---
+name: connections-optimizer
+description: Reorganize the user's X and LinkedIn network with review-first pruning, add/follow recommendations, and channel-specific warm outreach drafted in the user's real voice. Use when the user wants to clean up following lists, grow toward current priorities, or rebalance a social graph around higher-signal relationships.
+origin: ECC
+---
+
+# Connections Optimizer
+
+Reorganize the user's network instead of treating outbound as a one-way prospecting list.
+
+This skill handles:
+
+- X following cleanup and expansion
+- LinkedIn follow and connection analysis
+- review-first prune queues
+- add and follow recommendations
+- warm-path identification
+- Apple Mail, X DM, and LinkedIn draft generation in the user's real voice
+
+## When to Activate
+
+- the user wants to prune their X following
+- the user wants to rebalance who they follow or stay connected to
+- the user says "clean up my network", "who should I unfollow", "who should I follow", "who should I reconnect with"
+- outreach quality depends on network structure, not just cold list generation
+
+## Required Inputs
+
+Collect or infer:
+
+- current priorities and active work
+- target roles, industries, geos, or ecosystems
+- platform selection: X, LinkedIn, or both
+- do-not-touch list
+- mode: `light-pass`, `default`, or `aggressive`
+
+If the user does not specify a mode, use `default`.
+
+## Tool Requirements
+
+### Preferred
+
+- `x-api` for X graph inspection and recent activity
+- `lead-intelligence` for target discovery and warm-path ranking
+- `social-graph-ranker` when the user wants bridge value scored independently of the broader lead workflow
+- Exa / deep research for person and company enrichment
+- `brand-voice` before drafting outbound
+
+### Fallbacks
+
+- browser control for LinkedIn analysis and drafting
+- browser control for X if API coverage is constrained
+- Apple Mail or Mail.app drafting via desktop automation when email is the right channel
+
+## Safety Defaults
+
+- default is review-first, never blind auto-pruning
+- X: prune only accounts the user follows, never followers
+- LinkedIn: treat 1st-degree connection removal as manual-review-first
+- do not auto-send DMs, invites, or emails
+- emit a ranked action plan and drafts before any apply step
+
+## Platform Rules
+
+### X
+
+- mutuals are stickier than one-way follows
+- non-follow-backs can be pruned more aggressively
+- heavily inactive or disappeared accounts should surface quickly
+- engagement, signal quality, and bridge value matter more than raw follower count
+
+### LinkedIn
+
+- API-first if the user actually has LinkedIn API access
+- browser workflow must work when API access is missing
+- distinguish outbound follows from accepted 1st-degree connections
+- outbound follows can be pruned more freely
+- accepted 1st-degree connections should default to review, not auto-remove
+
+## Modes
+
+### `light-pass`
+
+- prune only high-confidence low-value one-way follows
+- surface the rest for review
+- generate a small add/follow list
+
+### `default`
+
+- balanced prune queue
+- balanced keep list
+- ranked add/follow queue
+- draft warm intros or direct outreach where useful
+
+### `aggressive`
+
+- larger prune queue
+- lower tolerance for stale non-follow-backs
+- still review-gated before apply
+
+## Scoring Model
+
+Use these positive signals:
+
+- reciprocity
+- recent activity
+- alignment to current priorities
+- network bridge value
+- role relevance
+- real engagement history
+- recent presence and responsiveness
+
+Use these negative signals:
+
+- disappeared or abandoned account
+- stale one-way follow
+- off-priority topic cluster
+- low-value noise
+- repeated non-response
+- no follow-back when many better replacements exist
+
+Mutuals and real warm-path bridges should be penalized less aggressively than one-way follows.
+
+## Workflow
+
+1. Capture priorities, do-not-touch constraints, and selected platforms.
+2. Pull the current following / connection inventory.
+3. Score prune candidates with explicit reasons.
+4. Score keep candidates with explicit reasons.
+5. Use `lead-intelligence` plus research surfaces to rank expansion candidates.
+6. Match the right channel:
+   - X DM for warm, fast social touch points
+   - LinkedIn message for professional graph adjacency
+   - Apple Mail draft for higher-context intros or outreach
+7. Run `brand-voice` before drafting messages.
+8. Return a review pack before any apply step.
+
+## Review Pack Format
+
+```text
+CONNECTIONS OPTIMIZER REPORT
+============================
+
+Mode:
+Platforms:
+Priority Set:
+
+Prune Queue
+- handle / profile
+  reason:
+  confidence:
+  action:
+
+Review Queue
+- handle / profile
+  reason:
+  risk:
+
+Keep / Protect
+- handle / profile
+  bridge value:
+
+Add / Follow Targets
+- person
+  why now:
+  warm path:
+  preferred channel:
+
+Drafts
+- X DM:
+- LinkedIn:
+- Apple Mail:
+```
+
+## Outbound Rules
+
+- Default email path is Apple Mail / Mail.app draft creation.
+- Do not send automatically.
+- Choose the channel based on warmth, relevance, and context depth.
+- Do not force a DM when an email or no outreach is the right move.
+- Drafts should sound like the user, not like automated sales copy.
+
+## Related Skills
+
+- `brand-voice` for the reusable voice profile
+- `social-graph-ranker` for the standalone bridge-scoring and warm-path math
+- `lead-intelligence` for weighted target and warm-path discovery
+- `x-api` for X graph access, drafting, and optional apply flows
+- `content-engine` when the user also wants public launch content around network moves

package/.agent/skills/content-engine/SKILL.md

@@ -1,131 +1,131 @@
----
-name: content-engine
-description: Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.
-origin: ECC
----
-
-# Content Engine
-
-Build platform-native content without flattening the author's real voice into platform slop.
-
-## When to Activate
-
-- writing X posts or threads
-- drafting LinkedIn posts or launch updates
-- scripting short-form video or YouTube explainers
-- repurposing articles, podcasts, demos, docs, or internal notes into public content
-- building a launch sequence or ongoing content system around a product, insight, or narrative
-
-## Non-Negotiables
-
-1. Start from source material, not generic post formulas.
-2. Adapt the format for the platform, not the persona.
-3. One post should carry one actual claim.
-4. Specificity beats adjectives.
-5. No engagement bait unless the user explicitly asks for it.
-
-## Source-First Workflow
-
-Before drafting, identify the source set:
-- published articles
-- notes or internal memos
-- product demos
-- docs or changelogs
-- transcripts
-- screenshots
-- 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 Handling
-
-`brand-voice` is the canonical voice layer.
-
-Run it first when:
-
-- there are multiple downstream outputs
-- the user explicitly cares about writing style
-- the content is launch, outreach, or reputation-sensitive
-
-Reuse the resulting `VOICE PROFILE` here instead of rebuilding a second voice model.
-If the user wants Affaan / ECC voice specifically, still treat `brand-voice` as the source of truth and feed it the best live or source-derived material available.
-
-## Hard Bans
-
-Delete and rewrite any of these:
-- "In today's rapidly evolving landscape"
-- "game-changer", "revolutionary", "cutting-edge"
-- "here's why this matters" unless it is followed immediately by something concrete
-- ending with a LinkedIn-style question just to farm replies
-- forced casualness on LinkedIn
-- fake engagement padding that was not present in the source material
-
-## Platform Adaptation Rules
-
-### X
-
-- open with the strongest claim, artifact, or tension
-- keep the compression if the source voice is compressed
-- if writing a thread, each post must advance the argument
-- do not pad with context the audience does not need
-
-### LinkedIn
-
-- expand only enough for people outside the immediate niche to follow
-- do not turn it into a fake lesson post unless the source material actually is reflective
-- no corporate inspiration cadence
-- no praise-stacking, no "journey" filler
-
-### Short Video
-
-- script around the visual sequence and proof points
-- first seconds should show the result, problem, or punch
-- do not write narration that sounds better on paper than on screen
-
-### YouTube
-
-- show the result or tension early
-- organize by argument or progression, not filler sections
-- use chaptering only when it helps clarity
-
-### Newsletter
-
-- open with the point, conflict, or artifact
-- do not spend the first paragraph warming up
-- every section needs to add something new
-
-## Repurposing Flow
-
-1. Pick the anchor asset.
-2. Extract 3 to 7 atomic claims or scenes.
-3. Rank them by sharpness, novelty, and proof.
-4. Assign one strong idea per output.
-5. Adapt structure for each platform.
-6. Strip platform-shaped filler.
-7. Run the quality gate.
-
-## Deliverables
-
-When asked for a campaign, return:
-- a short voice profile if voice matching matters
-- the core angle
-- platform-native drafts
-- posting order only if it helps execution
-- gaps that must be filled before publishing
-
-## Quality Gate
-
-Before delivering:
-- every draft sounds like the intended author, not the platform stereotype
-- every draft contains a real claim, proof point, or concrete observation
-- no generic hype language remains
-- 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
+---
+name: content-engine
+description: Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.
+origin: ECC
+---
+
+# Content Engine
+
+Build platform-native content without flattening the author's real voice into platform slop.
+
+## When to Activate
+
+- writing X posts or threads
+- drafting LinkedIn posts or launch updates
+- scripting short-form video or YouTube explainers
+- repurposing articles, podcasts, demos, docs, or internal notes into public content
+- building a launch sequence or ongoing content system around a product, insight, or narrative
+
+## Non-Negotiables
+
+1. Start from source material, not generic post formulas.
+2. Adapt the format for the platform, not the persona.
+3. One post should carry one actual claim.
+4. Specificity beats adjectives.
+5. No engagement bait unless the user explicitly asks for it.
+
+## Source-First Workflow
+
+Before drafting, identify the source set:
+- published articles
+- notes or internal memos
+- product demos
+- docs or changelogs
+- transcripts
+- screenshots
+- 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 Handling
+
+`brand-voice` is the canonical voice layer.
+
+Run it first when:
+
+- there are multiple downstream outputs
+- the user explicitly cares about writing style
+- the content is launch, outreach, or reputation-sensitive
+
+Reuse the resulting `VOICE PROFILE` here instead of rebuilding a second voice model.
+If the user wants Affaan / ECC voice specifically, still treat `brand-voice` as the source of truth and feed it the best live or source-derived material available.
+
+## Hard Bans
+
+Delete and rewrite any of these:
+- "In today's rapidly evolving landscape"
+- "game-changer", "revolutionary", "cutting-edge"
+- "here's why this matters" unless it is followed immediately by something concrete
+- ending with a LinkedIn-style question just to farm replies
+- forced casualness on LinkedIn
+- fake engagement padding that was not present in the source material
+
+## Platform Adaptation Rules
+
+### X
+
+- open with the strongest claim, artifact, or tension
+- keep the compression if the source voice is compressed
+- if writing a thread, each post must advance the argument
+- do not pad with context the audience does not need
+
+### LinkedIn
+
+- expand only enough for people outside the immediate niche to follow
+- do not turn it into a fake lesson post unless the source material actually is reflective
+- no corporate inspiration cadence
+- no praise-stacking, no "journey" filler
+
+### Short Video
+
+- script around the visual sequence and proof points
+- first seconds should show the result, problem, or punch
+- do not write narration that sounds better on paper than on screen
+
+### YouTube
+
+- show the result or tension early
+- organize by argument or progression, not filler sections
+- use chaptering only when it helps clarity
+
+### Newsletter
+
+- open with the point, conflict, or artifact
+- do not spend the first paragraph warming up
+- every section needs to add something new
+
+## Repurposing Flow
+
+1. Pick the anchor asset.
+2. Extract 3 to 7 atomic claims or scenes.
+3. Rank them by sharpness, novelty, and proof.
+4. Assign one strong idea per output.
+5. Adapt structure for each platform.
+6. Strip platform-shaped filler.
+7. Run the quality gate.
+
+## Deliverables
+
+When asked for a campaign, return:
+- a short voice profile if voice matching matters
+- the core angle
+- platform-native drafts
+- posting order only if it helps execution
+- gaps that must be filled before publishing
+
+## Quality Gate
+
+Before delivering:
+- every draft sounds like the intended author, not the platform stereotype
+- every draft contains a real claim, proof point, or concrete observation
+- no generic hype language remains
+- 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