@sellable/mcp 0.1.255 → 0.1.256

package/skills/create-post/references/post-file-contract.md

@@ -63,6 +63,10 @@ Hook research files must preserve:
 - source hook preview measurements, including text basis, char count including
   newlines, physical/content line counts, longest nonblank line, blank-line
   visual risk, and mobile/desktop preview budget status
+- rendered preview records for every kept source hook and adapted hook block,
+  including literal mobile/desktop preview blocks, rendered line wraps, render
+  basis, CSS contract version, text widths, first-screen promise visibility,
+  core point visibility, and whether the point lands after the mobile clamp
 - extracted hook patterns
 - selected hook basis
 
@@ -83,6 +87,9 @@ Draft files must preserve:
 - draft body
 - validation receipt, including LinkedIn preview pass/warn/fail status and
   compact fallback when the selected hook carries a warning
+- rendered mobile and desktop preview blocks for the selected hook; drafts
+  cannot be ready when this rendered-preview audit is missing or fails mobile
+  visibility
 - status: `draft`, `ready`, `needs_revision`, `published`, or `archived`
 
 Multiple drafts for the same idea are expected. Keep the `ideaId` stable and

package/skills/create-post/references/post-validation.md

@@ -78,6 +78,12 @@ Each candidate should include:
 - reader value implied
 - source pattern
 - score
+- `renderedPreview` using `references/linkedin-preview-rendering.md`
+- literal mobile and desktop rendered preview blocks
+- mobile and desktop rendered line wraps
+- first-screen promise: pain, proof, or curiosity visible by the mobile clamp
+- whether the core point is visible in the mobile rendered preview
+- whether the point lands after the mobile clamp
 - char count including newlines and first-line / first-two-line preview measurements
 - physical line count, content line count, longest nonblank line, and blank-line risk
 - `previewBudgetStatus`: `pass`, `warn`, or `fail`
@@ -98,7 +104,7 @@ After the first draft:
 6. replace generic language with concrete words only when supported
 7. preserve the user's actual story and point
 8. remove AI tells
-9. re-check LinkedIn preview fit after edits
+9. re-render the selected hook on mobile and desktop after edits
 
 ## Premise Value Audit
 
@@ -149,22 +155,65 @@ proof from another creator, save as `needs_revision`.
 
 ## LinkedIn Preview Audit
 
-Audit the selected hook and top candidates against conservative LinkedIn
-preview budgets. LinkedIn does not publish exact "see more" cutoff rules, and
-rendering varies by device, app version, font, media, and line break. This audit
-is a mobile-first safety gate, not a claim about an official LinkedIn limit.
-
-Use:
-
-- `pass`: hook is <= 110 chars including newlines, every nonblank line is <= 45 chars, and the hook's core point lands before likely truncation.
-- `warn`: hook is 111-140 chars including newlines, any nonblank line is 46-55 chars, or blank lines create visual-line risk. Blank lines are allowed, but they count as physical lines.
-- `fail`: hook is > 140 chars including newlines, any nonblank line is > 55 chars, or the hook's point depends on text after likely truncation.
+Audit the selected hook and top candidates against
+`references/linkedin-preview-rendering.md`. LinkedIn does not publish exact
+"see more" cutoff rules, and rendering varies by device, app version, font,
+media, and line break. This audit is a mobile-first rendered-preview safety
+gate, not a claim about an official LinkedIn limit.
+
+Character budgets are secondary diagnostics. They cannot be the only evidence
+that a hook works. Every selected hook must include literal rendered mobile and
+desktop preview blocks.
+
+Default deterministic renderer when no authenticated LinkedIn screenshot is
+available:
+
+```text
+cssContractVersion: linkedin-preview-rendering/v1
+font size: 14px
+line height: 21px
+white space: pre-wrap
+overflow wrap: break-word
+mobile text width: 308px
+desktop text width: 582px
+review clamp: first 3 rendered text lines
+```
+
+Use rendered gates:
+
+- `pass`: the mobile rendered preview shows the pain, proof, or curiosity by
+  the end of the first 3 rendered lines, and the core point is understandable
+  without opening "see more".
+- `warn`: the mobile rendered preview creates useful curiosity but the core
+  point is slightly softened by wrapping, blank-line rhythm, or one missing
+  context word. A compact fallback is required.
+- `fail`: the hook's real point appears after the first 3 mobile rendered
+  lines, the first rendered line is generic setup, blank lines consume the
+  preview before the reader sees the point, or desktop fit is the only reason it
+  looks good.
 
 Desktop preview usually has more room. Still record desktop fit, but never let
 desktop fit compensate for a mobile `fail`.
 
 Record:
 
+- `renderedPreview`
+- `renderBasis`: `linkedin_css_contract`, `authenticated_linkedin_screenshot`,
+  or `manual_user_source`
+- `cssContractVersion`
+- `mobileRenderedPreviewBlock`
+- `desktopRenderedPreviewBlock`
+- `mobileRenderedLines`
+- `desktopRenderedLines`
+- `mobileTextWidthPx`
+- `desktopTextWidthPx`
+- `mobileRenderedLineCount`
+- `desktopRenderedLineCount`
+- `corePainProofOrCuriosityVisibleMobile`
+- `corePainProofOrCuriosityVisibleDesktop`
+- `corePointVisibleMobile`
+- `corePointVisibleDesktop`
+- `pointAfterMobileClamp`
 - `charCount`
 - `charCountIncludingNewlines`
 - `firstLineChars`
@@ -183,10 +232,14 @@ Record:
 - `rewriteIfTruncated`
 - `compactFallback` when `previewBudgetStatus` is `warn`
 
-If the hook only works after likely truncation, rewrite it. A draft cannot be
-`ready` with `previewBudgetStatus: fail`. A draft may be `ready` with
-`previewBudgetStatus: warn` only when the warning is explicit, usually because
-the user prefers blank-line rhythm, and the receipt includes a compact fallback.
+If the hook only works after the rendered mobile clamp, rewrite it. A draft
+cannot be `ready` with `previewBudgetStatus: fail`,
+`mobilePreviewFit: fail`, missing `renderedPreview`,
+`corePainProofOrCuriosityVisibleMobile: false`,
+`corePointVisibleMobile: false`, or `pointAfterMobileClamp: true`. A draft may
+be `ready` with `previewBudgetStatus: warn` only when the warning is explicit,
+usually because the user prefers blank-line rhythm, and the receipt includes a
+compact fallback.
 
 ## Simplifier / Concrete-Language Audit
 

package/skills/find-leads/SKILL.md

@@ -90,7 +90,6 @@ should stay focused on source evidence.
 - `mcp__sellable__search_prospeo`
 - `mcp__sellable__search_prospeo_companies`
 - `mcp__sellable__confirm_prospeo_company_accounts`
-- `mcp__sellable__list_dnc_entries`
 - `mcp__sellable__load_csv_dnc_entries`
 - `mcp__sellable__load_csv_domains`
 - `mcp__sellable__load_csv_linkedin_leads`
@@ -106,9 +105,6 @@ should stay focused on source evidence.
   list after confirming the exact active workspace. Keep the mechanism to
   Sellable DNC and `DNC Check`, not provider search work or Prospeo domain
   filters.
-- If the user asks to see the current DNC count, list names, or first page
-  before import, call `list_dnc_entries`. Report the active workspace name and
-  ID from the tool response before any DNC write.
 - Do not infer sender identities from meeting attendance alone. Only treat someone as a sender when the source material explicitly identifies them as a sender or supplies their LinkedIn URL.
 - Do not ask Layer 1 questions already answered by a transcript, ICP doc, or Layer 0 research.
 - Do not include Apollo in the explorer set for this phase.
@@ -140,8 +136,6 @@ Execution flow:
      DNC entries.
    - Campaign creation already includes `DNC Check`, which checks domain/profile
      before message generation.
-   - If the user wants the existing DNC count or first page first, call
-     `list_dnc_entries` before previewing the import.
 3. If the user has a CSV of LinkedIn profile URLs on disk, call `load_csv_linkedin_leads` first.
    - Preview, confirm, then review the resulting lead list before `confirm_lead_list`.
    - Confirmed execution uploads the raw CSV file, starts the server-owned import job, and waits on lead-list readiness before returning.

package/skills/research/config.json

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