codeply-cli 0.5.5 → 0.6.0

package/skills/social-graph-ranker/SKILL.md

@@ -1,155 +1,155 @@
----
-name: social-graph-ranker
-description: Weighted social-graph ranking for warm intro discovery, bridge scoring, and network gap analysis across X and LinkedIn. Use when the user wants the reusable graph-ranking engine itself, not the broader outreach or network-maintenance workflow layered on top of it.
-metadata:
-  origin: ECC
----
-
-# Social Graph Ranker
-
-Canonical weighted graph-ranking layer for network-aware outreach.
-
-Use this when the user needs to:
-
-- rank existing mutuals or connections by intro value
-- map warm paths to a target list
-- measure bridge value across first- and second-order connections
-- decide which targets deserve warm intros versus direct cold outreach
-- understand the graph math independently from `lead-intelligence` or `connections-optimizer`
-
-## When To Use This Standalone
-
-Choose this skill when the user primarily wants the ranking engine:
-
-- "who in my network is best positioned to introduce me?"
-- "rank my mutuals by who can get me to these people"
-- "map my graph against this ICP"
-- "show me the bridge math"
-
-Do not use this by itself when the user really wants:
-
-- full lead generation and outbound sequencing -> use `lead-intelligence`
-- pruning, rebalancing, and growing the network -> use `connections-optimizer`
-
-## Inputs
-
-Collect or infer:
-
-- target people, companies, or ICP definition
-- the user's current graph on X, LinkedIn, or both
-- weighting priorities such as role, industry, geography, and responsiveness
-- traversal depth and decay tolerance
-
-## Core Model
-
-Given:
-
-- `T` = weighted target set
-- `M` = your current mutuals / direct connections
-- `d(m, t)` = shortest hop distance from mutual `m` to target `t`
-- `w(t)` = target weight from signal scoring
-
-Base bridge score:
-
-```text
-B(m) = Σ_{t ∈ T} w(t) · λ^(d(m,t) - 1)
-```
-
-Where:
-
-- `λ` is the decay factor, usually `0.5`
-- a direct path contributes full value
-- each extra hop halves the contribution
-
-Second-order expansion:
-
-```text
-B_ext(m) = B(m) + α · Σ_{m' ∈ N(m) \\ M} Σ_{t ∈ T} w(t) · λ^(d(m',t))
-```
-
-Where:
-
-- `N(m) \\ M` is the set of people the mutual knows that you do not
-- `α` discounts second-order reach, usually `0.3`
-
-Response-adjusted final ranking:
-
-```text
-R(m) = B_ext(m) · (1 + β · engagement(m))
-```
-
-Where:
-
-- `engagement(m)` is normalized responsiveness or relationship strength
-- `β` is the engagement bonus, usually `0.2`
-
-Interpretation:
-
-- Tier 1: high `R(m)` and direct bridge paths -> warm intro asks
-- Tier 2: medium `R(m)` and one-hop bridge paths -> conditional intro asks
-- Tier 3: low `R(m)` or no viable bridge -> direct outreach or follow-gap fill
-
-## Scoring Signals
-
-Weight targets before graph traversal with whatever matters for the current priority set:
-
-- role or title alignment
-- company or industry fit
-- current activity and recency
-- geographic relevance
-- influence or reach
-- likelihood of response
-
-Weight mutuals after traversal with:
-
-- number of weighted paths into the target set
-- directness of those paths
-- responsiveness or prior interaction history
-- contextual fit for making the intro
-
-## Workflow
-
-1. Build the weighted target set.
-2. Pull the user's graph from X, LinkedIn, or both.
-3. Compute direct bridge scores.
-4. Expand second-order candidates for the highest-value mutuals.
-5. Rank by `R(m)`.
-6. Return:
-   - best warm intro asks
-   - conditional bridge paths
-   - graph gaps where no warm path exists
-
-## Output Shape
-
-```text
-SOCIAL GRAPH RANKING
-====================
-
-Priority Set:
-Platforms:
-Decay Model:
-
-Top Bridges
-- mutual / connection
-  base_score:
-  extended_score:
-  best_targets:
-  path_summary:
-  recommended_action:
-
-Conditional Paths
-- mutual / connection
-  reason:
-  extra hop cost:
-
-No Warm Path
-- target
-  recommendation: direct outreach / fill graph gap
-```
-
-## Related Skills
-
-- `lead-intelligence` uses this ranking model inside the broader target-discovery and outreach pipeline
-- `connections-optimizer` uses the same bridge logic when deciding who to keep, prune, or add
-- `brand-voice` should run before drafting any intro request or direct outreach
-- `x-api` provides X graph access and optional execution paths
+---
+name: social-graph-ranker
+description: Weighted social-graph ranking for warm intro discovery, bridge scoring, and network gap analysis across X and LinkedIn. Use when the user wants the reusable graph-ranking engine itself, not the broader outreach or network-maintenance workflow layered on top of it.
+metadata:
+  origin: ECC
+---
+
+# Social Graph Ranker
+
+Canonical weighted graph-ranking layer for network-aware outreach.
+
+Use this when the user needs to:
+
+- rank existing mutuals or connections by intro value
+- map warm paths to a target list
+- measure bridge value across first- and second-order connections
+- decide which targets deserve warm intros versus direct cold outreach
+- understand the graph math independently from `lead-intelligence` or `connections-optimizer`
+
+## When To Use This Standalone
+
+Choose this skill when the user primarily wants the ranking engine:
+
+- "who in my network is best positioned to introduce me?"
+- "rank my mutuals by who can get me to these people"
+- "map my graph against this ICP"
+- "show me the bridge math"
+
+Do not use this by itself when the user really wants:
+
+- full lead generation and outbound sequencing -> use `lead-intelligence`
+- pruning, rebalancing, and growing the network -> use `connections-optimizer`
+
+## Inputs
+
+Collect or infer:
+
+- target people, companies, or ICP definition
+- the user's current graph on X, LinkedIn, or both
+- weighting priorities such as role, industry, geography, and responsiveness
+- traversal depth and decay tolerance
+
+## Core Model
+
+Given:
+
+- `T` = weighted target set
+- `M` = your current mutuals / direct connections
+- `d(m, t)` = shortest hop distance from mutual `m` to target `t`
+- `w(t)` = target weight from signal scoring
+
+Base bridge score:
+
+```text
+B(m) = Σ_{t ∈ T} w(t) · λ^(d(m,t) - 1)
+```
+
+Where:
+
+- `λ` is the decay factor, usually `0.5`
+- a direct path contributes full value
+- each extra hop halves the contribution
+
+Second-order expansion:
+
+```text
+B_ext(m) = B(m) + α · Σ_{m' ∈ N(m) \\ M} Σ_{t ∈ T} w(t) · λ^(d(m',t))
+```
+
+Where:
+
+- `N(m) \\ M` is the set of people the mutual knows that you do not
+- `α` discounts second-order reach, usually `0.3`
+
+Response-adjusted final ranking:
+
+```text
+R(m) = B_ext(m) · (1 + β · engagement(m))
+```
+
+Where:
+
+- `engagement(m)` is normalized responsiveness or relationship strength
+- `β` is the engagement bonus, usually `0.2`
+
+Interpretation:
+
+- Tier 1: high `R(m)` and direct bridge paths -> warm intro asks
+- Tier 2: medium `R(m)` and one-hop bridge paths -> conditional intro asks
+- Tier 3: low `R(m)` or no viable bridge -> direct outreach or follow-gap fill
+
+## Scoring Signals
+
+Weight targets before graph traversal with whatever matters for the current priority set:
+
+- role or title alignment
+- company or industry fit
+- current activity and recency
+- geographic relevance
+- influence or reach
+- likelihood of response
+
+Weight mutuals after traversal with:
+
+- number of weighted paths into the target set
+- directness of those paths
+- responsiveness or prior interaction history
+- contextual fit for making the intro
+
+## Workflow
+
+1. Build the weighted target set.
+2. Pull the user's graph from X, LinkedIn, or both.
+3. Compute direct bridge scores.
+4. Expand second-order candidates for the highest-value mutuals.
+5. Rank by `R(m)`.
+6. Return:
+   - best warm intro asks
+   - conditional bridge paths
+   - graph gaps where no warm path exists
+
+## Output Shape
+
+```text
+SOCIAL GRAPH RANKING
+====================
+
+Priority Set:
+Platforms:
+Decay Model:
+
+Top Bridges
+- mutual / connection
+  base_score:
+  extended_score:
+  best_targets:
+  path_summary:
+  recommended_action:
+
+Conditional Paths
+- mutual / connection
+  reason:
+  extra hop cost:
+
+No Warm Path
+- target
+  recommendation: direct outreach / fill graph gap
+```
+
+## Related Skills
+
+- `lead-intelligence` uses this ranking model inside the broader target-discovery and outreach pipeline
+- `connections-optimizer` uses the same bridge logic when deciding who to keep, prune, or add
+- `brand-voice` should run before drafting any intro request or direct outreach
+- `x-api` provides X graph access and optional execution paths

package/skills/social-publisher/SKILL.md

@@ -1,130 +1,130 @@
----
-name: social-publisher
-description: Agent-driven scheduling and publishing of social media posts across 13 platforms via SocialClaw. Use when the user wants to publish to X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, or Pinterest — or when managing campaigns, uploading media, or monitoring post delivery status.
-metadata:
-  origin: community
----
-
-# Social Publisher (SocialClaw)
-
-Connects Claude Code to [SocialClaw](https://getsocialclaw.com) for agent-driven social media publishing across 13 platforms through a single workspace API key.
-
-## When to Activate
-
-- publish content to X, LinkedIn, Instagram, TikTok, or other platforms
-- schedule a post campaign across multiple platforms at once
-- upload media for use in social posts
-- validate a post schedule before going live
-- monitor publishing run status and delivery analytics
-
-## Setup
-
-```bash
-# Required: workspace API key from https://getsocialclaw.com/dashboard
-export SC_API_KEY="<workspace-key>"
-
-# Verify access
-printf 'header = "Authorization: Bearer %s"\n' "$SC_API_KEY" |
-  curl -sS -K - https://getsocialclaw.com/v1/keys/validate
-
-# Install CLI (optional but recommended)
-npm install -g socialclaw@0.1.12
-socialclaw login --api-key <workspace-key>
-```
-
-## Core Workflow
-
-### 1. List connected accounts
-```bash
-socialclaw accounts list --json
-```
-
-If not connected:
-```bash
-socialclaw accounts connect --provider x --open
-socialclaw accounts connect --provider linkedin --open
-```
-
-### 2. Upload media (optional)
-```bash
-socialclaw assets upload --file ./image.png --json
-# → { "asset_id": "..." }
-```
-
-### 3. Build schedule.json
-```json
-{
-  "posts": [
-    {
-      "provider": "x",
-      "account_id": "<account-id>",
-      "text": "Post text here",
-      "scheduled_at": "2026-06-01T10:00:00Z"
-    }
-  ]
-}
-```
-
-### Optional X/Twitter evidence packet
-
-Before building an X schedule, collect a source packet when the campaign depends on live audience signals rather than the draft alone.
-
-For OpenClaw users who have already approved TweetClaw in their dependency policy, use the pinned package as a separate evidence source:
-
-```bash
-openclaw plugins install npm:@xquik/tweetclaw@1.6.31
-```
-
-Use it for public tweet search, reply search, follower export, user lookup, media review, monitors, or giveaway evidence. Keep the output as research input for `schedule.json`; SocialClaw remains responsible for validation, scheduling, publishing, and delivery status. Store TweetClaw credentials in its plugin config, not in `SC_API_KEY`, schedule files, or campaign assets. Do not install it as a default ECC or SocialClaw dependency.
-
-### 4. Validate before publishing
-```bash
-socialclaw validate -f schedule.json --json
-```
-
-### 5. Publish
-```bash
-socialclaw apply -f schedule.json --json
-# → { "run_id": "..." }
-```
-
-### 6. Monitor
-```bash
-socialclaw status --run-id <run-id> --json
-socialclaw posts list --json
-```
-
-## Supported Providers
-
-| Provider | Key |
-|----------|-----|
-| X (Twitter) | `x` |
-| LinkedIn profile | `linkedin` |
-| LinkedIn page | `linkedin_page` |
-| Instagram Business | `instagram_business` |
-| Instagram standalone | `instagram` |
-| Facebook Page | `facebook` |
-| TikTok | `tiktok` |
-| YouTube | `youtube` |
-| Reddit | `reddit` |
-| WordPress | `wordpress` |
-| Discord | `discord` |
-| Telegram | `telegram` |
-| Pinterest | `pinterest` |
-
-## Security
-
-- Outbound requests go to `getsocialclaw.com` only
-- Provider OAuth is in the SocialClaw dashboard — no per-provider secrets exposed to the agent
-- `SC_API_KEY` is a workspace-scoped key
-
-## Related Skills
-
-- `x-api` — direct X/Twitter API operations
-- `social-graph-ranker` — network analysis for outreach targeting
-- `TweetClaw` - optional approved OpenClaw X/Twitter source evidence before SocialClaw scheduling
-
-## Source
-
-- npm: `npm install -g socialclaw@0.1.12`
-- Dashboard: [SocialClaw dashboard](https://getsocialclaw.com/dashboard)
+---
+name: social-publisher
+description: Agent-driven scheduling and publishing of social media posts across 13 platforms via SocialClaw. Use when the user wants to publish to X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, or Pinterest — or when managing campaigns, uploading media, or monitoring post delivery status.
+metadata:
+  origin: community
+---
+
+# Social Publisher (SocialClaw)
+
+Connects Claude Code to [SocialClaw](https://getsocialclaw.com) for agent-driven social media publishing across 13 platforms through a single workspace API key.
+
+## When to Activate
+
+- publish content to X, LinkedIn, Instagram, TikTok, or other platforms
+- schedule a post campaign across multiple platforms at once
+- upload media for use in social posts
+- validate a post schedule before going live
+- monitor publishing run status and delivery analytics
+
+## Setup
+
+```bash
+# Required: workspace API key from https://getsocialclaw.com/dashboard
+export SC_API_KEY="<workspace-key>"
+
+# Verify access
+printf 'header = "Authorization: Bearer %s"\n' "$SC_API_KEY" |
+  curl -sS -K - https://getsocialclaw.com/v1/keys/validate
+
+# Install CLI (optional but recommended)
+npm install -g socialclaw@0.1.12
+socialclaw login --api-key <workspace-key>
+```
+
+## Core Workflow
+
+### 1. List connected accounts
+```bash
+socialclaw accounts list --json
+```
+
+If not connected:
+```bash
+socialclaw accounts connect --provider x --open
+socialclaw accounts connect --provider linkedin --open
+```
+
+### 2. Upload media (optional)
+```bash
+socialclaw assets upload --file ./image.png --json
+# → { "asset_id": "..." }
+```
+
+### 3. Build schedule.json
+```json
+{
+  "posts": [
+    {
+      "provider": "x",
+      "account_id": "<account-id>",
+      "text": "Post text here",
+      "scheduled_at": "2026-06-01T10:00:00Z"
+    }
+  ]
+}
+```
+
+### Optional X/Twitter evidence packet
+
+Before building an X schedule, collect a source packet when the campaign depends on live audience signals rather than the draft alone.
+
+For OpenClaw users who have already approved TweetClaw in their dependency policy, use the pinned package as a separate evidence source:
+
+```bash
+openclaw plugins install npm:@xquik/tweetclaw@1.6.31
+```
+
+Use it for public tweet search, reply search, follower export, user lookup, media review, monitors, or giveaway evidence. Keep the output as research input for `schedule.json`; SocialClaw remains responsible for validation, scheduling, publishing, and delivery status. Store TweetClaw credentials in its plugin config, not in `SC_API_KEY`, schedule files, or campaign assets. Do not install it as a default ECC or SocialClaw dependency.
+
+### 4. Validate before publishing
+```bash
+socialclaw validate -f schedule.json --json
+```
+
+### 5. Publish
+```bash
+socialclaw apply -f schedule.json --json
+# → { "run_id": "..." }
+```
+
+### 6. Monitor
+```bash
+socialclaw status --run-id <run-id> --json
+socialclaw posts list --json
+```
+
+## Supported Providers
+
+| Provider | Key |
+|----------|-----|
+| X (Twitter) | `x` |
+| LinkedIn profile | `linkedin` |
+| LinkedIn page | `linkedin_page` |
+| Instagram Business | `instagram_business` |
+| Instagram standalone | `instagram` |
+| Facebook Page | `facebook` |
+| TikTok | `tiktok` |
+| YouTube | `youtube` |
+| Reddit | `reddit` |
+| WordPress | `wordpress` |
+| Discord | `discord` |
+| Telegram | `telegram` |
+| Pinterest | `pinterest` |
+
+## Security
+
+- Outbound requests go to `getsocialclaw.com` only
+- Provider OAuth is in the SocialClaw dashboard — no per-provider secrets exposed to the agent
+- `SC_API_KEY` is a workspace-scoped key
+
+## Related Skills
+
+- `x-api` — direct X/Twitter API operations
+- `social-graph-ranker` — network analysis for outreach targeting
+- `TweetClaw` - optional approved OpenClaw X/Twitter source evidence before SocialClaw scheduling
+
+## Source
+
+- npm: `npm install -g socialclaw@0.1.12`
+- Dashboard: [SocialClaw dashboard](https://getsocialclaw.com/dashboard)