@sellable/mcp 0.1.540 → 0.1.542

package/skills/refresh-sender-engagement/SKILL.md

@@ -19,10 +19,9 @@ allowed-tools:
   - mcp__sellable__get_campaign_table_schema
   - mcp__sellable__list_tables
   - mcp__sellable__get_rows_minimal
+  - mcp__sellable__refresh_sender_engagement
   - mcp__sellable__fetch_linkedin_posts
-  - mcp__sellable__select_promising_posts
   - mcp__sellable__fetch_post_engagers
-  - mcp__sellable__add_on_demand_leads
 ---
 
 # Refresh Sender Engagement
@@ -34,7 +33,7 @@ You are a pipeline supply agent. People who engage with a sender's LinkedIn post
 <inputs>
 The invoking prompt names the senders ("refresh sender engagement for csreyes92 and thomas"). Resolve each via `list_senders` (match name/handle/LinkedIn URL). With no names given, inspect the active workspace and refresh every connected sender that has an active/paused sender-owned Post Engagers campaign backed by Signal Discovery.
 
-Optional: lookback window (default: posts from the last 30 days), engagement sources (default `both` reactions+comments), target sender names/ids, maximum posts per sender (default 5, hard cap 5 unless the user explicitly asks for more), and target campaign ids/names when the user wants to force a specific campaign.
+Optional: target sender names/ids, `tableId` when the user wants to force a specific campaign table, maximum posts per sender (default 5, hard cap 5 unless the user explicitly asks for more), and maximum engager pages per tracked post.
 </inputs>
 
 <entrypoint>
@@ -53,39 +52,36 @@ suggest `refill-sends`.
 <objective>
 For each target sender/campaign:
 
-1. **Find active Signal Discovery/Post Engagers campaigns first**:
+1. **Authenticate and resolve workspace**:
    - Call `get_auth_status` and confirm the active workspace.
-   - Call `get_campaigns` and, when needed, `list_tables`/`get_campaign` to find candidate campaigns.
-   - Keep only active or paused campaign-backed sender-owned Post Engagers campaigns. Strong signals include campaign/table names like `<Sender> - Post Engagers`, `sourceProvider:"signal-discovery"`, sender attachment to exactly one sender, and source/list/table readback indicating post engagers.
-   - Exclude shared Signal Discovery lanes, Shared Cold Fallback lanes, archived/completed campaigns, non-campaign tables, direct/on-demand-only campaigns, and any campaign attached to multiple senders unless the user explicitly selected it and the readback proves it is sender-owned.
-   - If no matching campaign exists for a sender, report "no active Post Engagers Signal Discovery campaign — create one first" and skip; do not silently create campaigns.
-2. **Resolve the sender and source boundary**:
-   - Match each candidate campaign to its sender from `list_senders`/`get_sender`.
-   - Use the sender's own LinkedIn profile URL/handle as the only source author boundary.
-   - Never scrape third-party authors into a sender-owned Post Engagers campaign.
-3. **Find relevant sender-authored posts to refresh**:
-   - Call `fetch_linkedin_posts({ linkedinUrl: sender profile, limit: 25 })`.
-   - Keep original posts authored by that exact sender, not reposts, from the lookback window.
-   - Rank posts by recency, engagement count, and fit to the campaign's buyer/problem/topic. Prefer posts likely to attract the target buyer over generic company updates.
-   - If the campaign has an existing Signal Discovery/source state that names tracked/selected posts, prefer refreshing those posts when they are still inside the lookback window and relevant; otherwise choose the strongest recent sender-authored posts.
-   - When the product flow expects selected posts to be visible, call `select_promising_posts` before scraping.
-4. **Pull latest engagers**:
-   - For the top posts (up to 5 per sender per run), call `fetch_post_engagers({ postUrl, sources })`.
-   - Default `sources` to `"both"` unless the user requested reactions-only or comments-only.
-5. **Filter to ICP** using the campaign's existing headline ICP criteria (from `get_campaign` brief/rubrics/table schema). Judge each engager's headline against those criteria; exclude obvious non-fits, the sender's own colleagues, existing employees, students/job-seekers, competitors, and anyone with no usable headline. When the campaign has no criteria, keep likely decision-makers/operators and exclude weak-fit profiles.
-6. **Add net-new leads only**:
-   - Use `add_on_demand_leads({ tableId, leads, skipDuplicates: true })` with name, headline-derived title, profile URL, and source/post context where the tool accepts it.
-   - Dedupe is mandatory. Never disable dedupe on a scheduled run.
-   - Do not generate, approve, schedule, or send messages.
-7. **Report**: campaigns inspected, target campaigns selected, posts scanned, engagers found, ICP-passing, net-new added per sender/campaign. If a sender posted nothing in the window, say "no recent posts — nothing to refresh" (that is a truthful no-op, not a failure).
+   - If there is no active workspace or auth is missing, stop with the MCP guidance. Do not use local env files or repo scripts as a substitute for MCP auth.
+   - Resolve each target sender with `list_senders`/`get_sender`. Use the sender id returned by the product, not a guessed handle.
+2. **Use the typed product command first**:
+   - Call `refresh_sender_engagement` in `mode:"dry_run"` for each sender.
+   - Always pass `workspaceId`, `senderId`, and any user-specified `tableId`, `maxPosts`, or `maxEngagerPages`.
+   - Treat the dry-run response as the campaign/source boundary authority. It should identify the sender-owned Post Engagers slot, campaign, workflow table, source provider `campaign-tracked-post`, source table type `tracked_post_engager_source_list`, expected tracked posts, expected engager refresh/import work, and a `dryRunFingerprint`.
+   - If the typed command reports no eligible sender-owned Post Engagers campaign, no tracked posts, no recent posts, or a workspace/sender mismatch, report that exact blocker and stop for that sender. Do not silently create campaigns or fall back to shared lanes.
+3. **Gate writes with dry-run proof**:
+   - Never call `refresh_sender_engagement` in `mode:"apply"` before a successful dry run from this same run.
+   - For manual runs, show the target workspace, sender, campaign/table, source lead list, expected tracked posts, expected row/import impact, and `dryRunFingerprint`, then wait for explicit user approval before apply.
+   - For scheduled automations where the user has already authorized refreshes, apply is allowed only with the exact `dryRunFingerprint` from the immediately preceding dry run.
+   - If apply rejects the fingerprint as stale or mismatched, rerun dry-run and ask for approval again for manual runs.
+4. **Apply through the typed command only**:
+   - Call `refresh_sender_engagement({ mode:"apply", workspaceId, senderId, tableId?, maxPosts?, maxEngagerPages?, dryRunFingerprint })`.
+   - The apply path must materialize/refresh tracked posts, import deduped tracked-post engagers into the campaign table, and preserve product idempotency. Do not use `add_on_demand_leads` or raw table row writes for the same operation.
+5. **Read-only fallback is diagnostic only**:
+   - If the typed command is unavailable, use `get_subskill_prompt`/`search_subskill_prompts` and stop with `blocked: missing_refresh_sender_engagement_tool`.
+   - `fetch_linkedin_posts` and `fetch_post_engagers` may be used only to explain source availability or diagnose provider issues. They are not an alternate write path.
+6. **Report**: campaigns inspected, target campaign/table, tracked posts materialized/refreshed, engagers scanned, ICP-passing/importable, net-new rows imported, duplicates skipped, and any no-op reason per sender/campaign. If a sender posted nothing in the window, say "no recent posts — nothing to refresh" (that is a truthful no-op, not a failure).
 </objective>
 
 <safety>
-- LinkedIn operations here are read-only fetches plus adding rows to a campaign table. **No messages are generated, approved, or sent by this skill.**
+- LinkedIn operations here are read-only fetches plus a typed product import into a campaign table. **No messages are generated, approved, scheduled, or sent by this skill.**
 - Respect workspace boundaries: only add leads to campaigns in the active workspace, and only for senders that belong to it.
 - Respect campaign boundaries: only add engagers to the matched sender-owned Post Engagers campaign/table. Do not mix shared-lane engagers into sender-owned campaigns or sender-owned engagers into shared lanes.
 - Cap provider usage per run: at most 5 posts × `fetch_post_engagers` per sender. If the invoking automation wants more, it must say so explicitly.
-- Never call `start_campaign`, `attach_sequence`, `queue_campaign_cells`, `start_campaign_message_preparation`, approval tools, or any send/schedule tool.
+- Never call `start_campaign`, `attach_sequence`, `queue_campaign_cells`, `start_campaign_message_preparation`, approval tools, send/schedule tools, or shared-lane mutation tools.
+- Never create campaigns, change campaign status, change sender ownership, approve campaign cells, or start message prep as part of this refresh.
 </safety>
 
 <output>

package/dist/refill-date-window.d.ts

@@ -1,34 +0,0 @@
-export type RefillDateWindowSource = "default_scheduler_forward" | "horizon_send_days" | "until_date" | "target_date";
-export type NormalizedRefillDateSelector = {
-    source: RefillDateWindowSource;
-    targetDate: string | null;
-    untilDate: string | null;
-    horizonSendDays: number | null;
-};
-export type RefillRunDateWindow = NormalizedRefillDateSelector & {
-    version: 1;
-    selectedDates: string[];
-    senderWindows?: Array<{
-        senderId: string | null;
-        timeZone: string | null;
-        selectedDates: string[];
-    }>;
-};
-type DateSelectorInput = {
-    targetDate?: unknown;
-    untilDate?: unknown;
-    horizonSendDays?: unknown;
-};
-export declare function normalizeRefillDateSelector(input: DateSelectorInput): NormalizedRefillDateSelector;
-export declare function refillDateSelectorBody(selector: NormalizedRefillDateSelector): {
-    targetDate?: string;
-    untilDate?: string;
-    horizonSendDays?: number;
-};
-export declare function dateWindowFromSelector(selector: NormalizedRefillDateSelector): RefillRunDateWindow;
-export declare function dateWindowFromPlan(plan: Record<string, unknown>, selector: NormalizedRefillDateSelector): RefillRunDateWindow;
-export declare function dateWindowFromRunState(runState: unknown): RefillRunDateWindow | null;
-export declare function selectorFromDateWindow(window: RefillRunDateWindow): NormalizedRefillDateSelector;
-export declare function dateSelectorMatchesWindow(selector: NormalizedRefillDateSelector, window: RefillRunDateWindow): boolean;
-export declare function schedulerSweepTargetDates(window: RefillRunDateWindow): string[];
-export {};

package/dist/refill-date-window.js

@@ -1,210 +0,0 @@
-function isRecord(value) {
-    return Boolean(value) && typeof value === "object" && !Array.isArray(value);
-}
-function stringValue(value) {
-    return typeof value === "string" && value.trim() ? value.trim() : null;
-}
-function numberValue(value) {
-    return typeof value === "number" && Number.isFinite(value) ? value : null;
-}
-function arrayValue(value) {
-    return Array.isArray(value) ? value : [];
-}
-function isValidDateKey(value) {
-    if (!/^\d{4}-\d{2}-\d{2}$/.test(value))
-        return false;
-    const [year, month, day] = value.split("-").map(Number);
-    const date = new Date(Date.UTC(year, month - 1, day));
-    return (date.getUTCFullYear() === year &&
-        date.getUTCMonth() === month - 1 &&
-        date.getUTCDate() === day);
-}
-function normalizeDateKey(value, field) {
-    if (value === undefined || value === null || value === "")
-        return null;
-    if (typeof value !== "string") {
-        throw new Error(`${field} must be a string in YYYY-MM-DD format.`);
-    }
-    const trimmed = value.trim();
-    if (!isValidDateKey(trimmed)) {
-        throw new Error(`${field} must be a valid YYYY-MM-DD calendar date.`);
-    }
-    return trimmed;
-}
-function normalizeHorizonSendDays(value) {
-    if (value === undefined)
-        return null;
-    if (typeof value !== "number" ||
-        !Number.isInteger(value) ||
-        value < 1 ||
-        value > 7) {
-        throw new Error("horizonSendDays must be an integer between 1 and 7.");
-    }
-    return value;
-}
-export function normalizeRefillDateSelector(input) {
-    const targetDate = normalizeDateKey(input.targetDate, "targetDate");
-    const untilDate = normalizeDateKey(input.untilDate, "untilDate");
-    const horizonSendDays = normalizeHorizonSendDays(input.horizonSendDays);
-    if (targetDate) {
-        return {
-            source: "target_date",
-            targetDate,
-            untilDate: null,
-            horizonSendDays: null,
-        };
-    }
-    if (untilDate) {
-        return {
-            source: "until_date",
-            targetDate: null,
-            untilDate,
-            horizonSendDays: null,
-        };
-    }
-    if (horizonSendDays !== null) {
-        return {
-            source: "horizon_send_days",
-            targetDate: null,
-            untilDate: null,
-            horizonSendDays,
-        };
-    }
-    return {
-        source: "default_scheduler_forward",
-        targetDate: null,
-        untilDate: null,
-        horizonSendDays: null,
-    };
-}
-export function refillDateSelectorBody(selector) {
-    if (selector.source === "target_date" && selector.targetDate) {
-        return { targetDate: selector.targetDate };
-    }
-    if (selector.source === "until_date" && selector.untilDate) {
-        return { untilDate: selector.untilDate };
-    }
-    if (selector.source === "horizon_send_days" &&
-        selector.horizonSendDays !== null) {
-        return { horizonSendDays: selector.horizonSendDays };
-    }
-    return {};
-}
-export function dateWindowFromSelector(selector) {
-    return {
-        version: 1,
-        ...selector,
-        selectedDates: selector.targetDate ? [selector.targetDate] : [],
-    };
-}
-function selectedDatesFromPlan(plan) {
-    const packet = isRecord(plan.packet) ? plan.packet : {};
-    const target = isRecord(packet.target) ? packet.target : {};
-    const window = isRecord(target.window) ? target.window : {};
-    const senderWindows = arrayValue(window.senderWindows).filter(isRecord);
-    const fromWindows = senderWindows.flatMap((senderWindow) => arrayValue(senderWindow.selectedDates)
-        .map((entry) => stringValue(entry))
-        .filter((entry) => Boolean(entry)));
-    if (fromWindows.length > 0)
-        return Array.from(new Set(fromWindows)).sort();
-    const senderRefillPlans = arrayValue(target.senderRefillPlans).filter(isRecord);
-    return Array.from(new Set(senderRefillPlans.flatMap((senderPlan) => {
-        const horizon = isRecord(senderPlan.horizon) ? senderPlan.horizon : {};
-        return arrayValue(horizon.selectedDays)
-            .filter(isRecord)
-            .map((day) => stringValue(day.date))
-            .filter((entry) => Boolean(entry));
-    }))).sort();
-}
-function senderWindowsFromPlan(plan) {
-    const packet = isRecord(plan.packet) ? plan.packet : {};
-    const target = isRecord(packet.target) ? packet.target : {};
-    const window = isRecord(target.window) ? target.window : {};
-    return arrayValue(window.senderWindows)
-        .filter(isRecord)
-        .map((senderWindow) => ({
-        senderId: stringValue(senderWindow.senderId),
-        timeZone: stringValue(senderWindow.timeZone),
-        selectedDates: arrayValue(senderWindow.selectedDates)
-            .map((entry) => stringValue(entry))
-            .filter((entry) => Boolean(entry)),
-    }));
-}
-export function dateWindowFromPlan(plan, selector) {
-    const packet = isRecord(plan.packet) ? plan.packet : {};
-    const request = isRecord(packet.request) ? packet.request : {};
-    const targetDate = stringValue(request.targetDate) ?? selector.targetDate ?? null;
-    const untilDate = stringValue(request.untilDate) ?? selector.untilDate ?? null;
-    const horizonSendDays = numberValue(request.horizonSendDays) ?? selector.horizonSendDays ?? null;
-    const source = targetDate
-        ? "target_date"
-        : untilDate
-            ? "until_date"
-            : horizonSendDays !== null
-                ? "horizon_send_days"
-                : selector.source;
-    const selectedDates = selectedDatesFromPlan(plan);
-    return {
-        version: 1,
-        source,
-        targetDate: source === "target_date" ? targetDate : null,
-        untilDate: source === "until_date" ? untilDate : null,
-        horizonSendDays: source === "horizon_send_days" ? horizonSendDays : null,
-        selectedDates: selectedDates.length > 0
-            ? selectedDates
-            : targetDate
-                ? [targetDate]
-                : [],
-        senderWindows: senderWindowsFromPlan(plan),
-    };
-}
-export function dateWindowFromRunState(runState) {
-    const state = isRecord(runState) ? runState : {};
-    const raw = isRecord(state.dateWindow) ? state.dateWindow : null;
-    if (!raw || raw.version !== 1)
-        return null;
-    const source = raw.source === "target_date" ||
-        raw.source === "until_date" ||
-        raw.source === "horizon_send_days" ||
-        raw.source === "default_scheduler_forward"
-        ? raw.source
-        : null;
-    if (!source)
-        return null;
-    return {
-        version: 1,
-        source,
-        targetDate: source === "target_date" ? stringValue(raw.targetDate) : null,
-        untilDate: source === "until_date" ? stringValue(raw.untilDate) : null,
-        horizonSendDays: source === "horizon_send_days"
-            ? numberValue(raw.horizonSendDays)
-            : null,
-        selectedDates: arrayValue(raw.selectedDates)
-            .map((entry) => stringValue(entry))
-            .filter((entry) => Boolean(entry)),
-    };
-}
-export function selectorFromDateWindow(window) {
-    return {
-        source: window.source,
-        targetDate: window.targetDate,
-        untilDate: window.untilDate,
-        horizonSendDays: window.horizonSendDays,
-    };
-}
-export function dateSelectorMatchesWindow(selector, window) {
-    return (selector.source === window.source &&
-        selector.targetDate === window.targetDate &&
-        selector.untilDate === window.untilDate &&
-        selector.horizonSendDays === window.horizonSendDays);
-}
-export function schedulerSweepTargetDates(window) {
-    if (window.source === "target_date" && window.targetDate) {
-        return [window.targetDate];
-    }
-    if (window.source === "until_date" ||
-        window.source === "horizon_send_days") {
-        return window.selectedDates;
-    }
-    return [];
-}

package/dist/tools/refill-sends-evergreen.d.ts

@@ -1,28 +0,0 @@
-type RefillSendsEvergreenInput = {
-    workspaceId?: string;
-};
-export declare const refillSendsEvergreenToolDefinitions: {
-    name: string;
-    description: string;
-    inputSchema: {
-        type: string;
-        properties: {
-            workspaceId: {
-                type: string;
-                description: string;
-            };
-        };
-        required: string[];
-        additionalProperties: boolean;
-    };
-}[];
-export declare function refillSendsEvergreenCommand(input: RefillSendsEvergreenInput): {
-    readOnly: boolean;
-    workspaceId: string | null;
-    firstOperationalSteps: string[];
-    approvalContract: string;
-    forbiddenActions: string[];
-    fillWindow: string;
-    hostExamples: string[];
-};
-export {};

package/dist/tools/refill-sends-evergreen.js

@@ -1,47 +0,0 @@
-export const refillSendsEvergreenToolDefinitions = [
-    {
-        name: "refill_sends_evergreen",
-        description: "Read-only Phase 85 evergreen refill command contract. It performs no mutations and only tells the operator to call get_evergreen_refill_plan for a dry-run packet and journal.",
-        inputSchema: {
-            type: "object",
-            properties: {
-                workspaceId: {
-                    type: "string",
-                    description: "Explicit request-scoped workspace id.",
-                },
-            },
-            required: ["workspaceId"],
-            additionalProperties: false,
-        },
-    },
-];
-export function refillSendsEvergreenCommand(input) {
-    return {
-        readOnly: true,
-        workspaceId: input.workspaceId ?? null,
-        firstOperationalSteps: [
-            "Call get_evergreen_refill_plan with the explicit workspaceId.",
-            "Read the returned packet, globalActionQueue, per-sender plans, and itinerary before taking any action.",
-            "Review the dry-run journal file path returned by get_evergreen_refill_plan.",
-            "Phase 85 is PLAN-ONLY; execution arrives in Phase 86.",
-        ],
-        approvalContract: "Nothing is approved or executable in Phase 85. The evergreen command is read-only; Phase 86 introduces execution approval.",
-        forbiddenActions: [
-            "Do not schedule sends.",
-            "Do not send messages.",
-            "Do not approve messages.",
-            "Do not prepare messages.",
-            "Do not start or launch campaigns.",
-            "Do not create campaigns.",
-            "Do not switch providers or source families.",
-            "Do not lower paid InMail thresholds.",
-            "Do not refresh paid InMail credits.",
-            "Do not write scheduler fields.",
-        ],
-        fillWindow: "Use only the target window and caps returned by get_evergreen_refill_plan.",
-        hostExamples: [
-            "refill_sends_evergreen({ workspaceId })",
-            "get_evergreen_refill_plan({ workspaceId })",
-        ],
-    };
-}

package/skills/research/config.json

@@ -1,9 +0,0 @@
-{
-  "parallelMode": "wide",
-  "agentCount": 6,
-  "maxToolCallsPerAgent": 2,
-  "senderMaxAgents": 2,
-  "senderMaxToolCallsPerAgent": 3,
-  "progressMode": true,
-  "debugMode": true
-}