@sellable/mcp 0.1.258 → 0.1.259

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

@@ -11,10 +11,6 @@ Every saved draft needs a validation receipt. A draft without this receipt is no
 - `candidateHooksConsidered`
 - `selectedHook`
 - `selectedHookWhy`
-- `sourceHookReachAudit`
-- `hookReverseEngineeringAudit`
-- `hookAngleMatrix`
-- `seeMoreClickAudit`
 - `proofClaimsUsed`
 - `proofClaimSources`
 - `storyFilesConsulted`
@@ -72,46 +68,16 @@ set the verdict to `revise` or `reject`.
 
 ## Candidate Set
 
-Generate many hook candidates before drafting. Do not lock onto the first draft.
-
-Minimum candidate set:
-
-- normal drafting: at least 8 angle territories and 24 hook candidates
-- hook-critical requests: at least 12 angle territories and 40 hook candidates
-- smaller set only when the user explicitly asks for fewer options
-
-An angle territory is a distinct reason the reader might care, such as hidden
-asset, tool/enemy contrast, first-person build proof, workflow reveal,
-contrarian category claim, mistake/confession, market timing, operator pain,
-specific person/company signal, before/after transformation, or question hook.
+Generate multiple hook candidates before drafting. Do not lock onto the first draft.
 
 Each candidate should include:
 
 - hook text
 - selected premise
-- angle territory
 - premise tension opened
 - reader value implied
 - source pattern
-- source shape kept
-- source words not copied
-- source pattern reach signals: author follower count when available, target
-  follower band, follower-band fit, engagement per 1k followers, weighted
-  engagement per 1k followers, reach-adjusted score, baseline lift, and
-  confidence
 - 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
-- `intentionalOpenLoop`
-- `specificClickQuestionVisible`
-- `seeMoreClickReason`
-- `clickQuestion`
-- `payoffAfterFold`
-- `bodyProofObligation`
-- 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`
@@ -120,55 +86,6 @@ Each candidate should include:
 - AI-tell risk
 - why it should win or lose
 
-## Hook Reverse Engineering Audit
-
-Before a draft can be `ready`, validate that the selected hook came from a real
-source-shape analysis, not from generic brainstorming.
-
-Record:
-
-- `sourceHooksStudied`
-- `sourceHookAutopsies`
-- `selectedSourceShape`
-- `sourceShapeKept`
-- `sourceWordsNotCopied`
-- `whyItWorks`
-- `openLoopType`: `none`, `hidden_payoff`, `contradiction`, `proof_gap`,
-  `workflow_reveal`, `asset_reveal`, or `story_gap`
-- `clickQuestion`
-- `promisedPayoff`
-- `specificityAnchor`
-- `tensionOpened`
-- `proofImplied`
-- `adaptationRule`
-- `bodyPayoffObligation`
-
-The selected draft cannot be `ready` if the hook was copied verbatim from
-another creator, if the receipt only says "contrarian" or "curiosity" without
-the concrete shape, or if the body does not pay off the hook quickly.
-
-## Hook Angle Matrix Audit
-
-Before a draft can be `ready`, validate that the hook was chosen after exploring
-materially different angles.
-
-Record:
-
-- `angleTerritoriesTested`
-- `hookCandidatesGenerated`
-- `winningTerritory`
-- `runnerUpTerritories`
-- `whyWinningAngleBeatsAlternatives`
-- `whyRejectedHooksLost`
-- `mobileRenderedPreviewBlocksForTopCandidates`
-- `desktopRenderedPreviewBlocksForTopCandidates`
-- `proofNeededByWinningAngle`
-
-If the user asked to "nail the hook," "focus on hooks," or explore "a ton of
-angles," the draft cannot be `ready` unless at least 12 territories and 40 hook
-candidates were considered or the receipt explains why the user explicitly
-requested fewer.
-
 ## Finalizer Pass
 
 After the first draft:
@@ -181,7 +98,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-render the selected hook on mobile and desktop after edits
+9. re-check LinkedIn preview fit after edits
 
 ## Premise Value Audit
 
@@ -230,104 +147,24 @@ If `selectedControversy` is missing, if the audience belief is only a generic
 label like "founders want growth," or if `credibleWhyUs` depends on borrowed
 proof from another creator, save as `needs_revision`.
 
-## Source Hook Reach Audit
-
-Before a draft can be `ready`, validate that the selected source hook pattern
-was chosen for a reach-normalized reason, not raw audience size.
-
-Record:
+## LinkedIn Preview Audit
 
-- `targetFollowerBand`
-- `authorFollowerCount` for each source pattern when available
-- `followerBandFit`: `in_target_band`, `below_target_band`,
-  `above_target_band`, or `unknown`
-- `engagementPer1kFollowers`
-- `weightedEngagementPer1kFollowers`
-- `reachAdjustedScore`
-- `reachPenaltyMultiplier`
-- `creatorBaselineMedianEngagement` or `creator_baseline_unavailable`
-- `baselineLift` or `creator_baseline_unavailable`
-- `bigAccountPenaltyApplied`
-- `whyTheHookCarries`
-- `followerCountUnavailableSources`
-- `whyThisHookIsAReachAdjustedSignal`
-
-If the user asked for a follower range and the selected source pattern is from a
-large account above the target range, the receipt must explain why it survived
-the celebrity reach penalty. Use large-account hooks as secondary pattern
-evidence unless they clearly overperform the creator's baseline or the hook
-itself carries after reach is controlled. A draft cannot be `ready` when the
-selected hook is justified only by raw total engagement or follower count.
+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.
 
-## LinkedIn Preview Audit
+Use:
 
-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 either the core point is
-  understandable without opening "see more" or an intentional open loop creates
-  a specific click question with an immediate planned payoff.
-- `warn`: the mobile rendered preview creates useful curiosity but the core
-  point or click question 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 without an intentional open-loop plan, the visible open loop is vague,
-  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.
+- `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.
 
 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`
-- `intentionalOpenLoop`
-- `specificClickQuestionVisible`
-- `payoffPlannedImmediatelyAfterClamp`
-- `seeMoreClickReason`
-- `clickQuestion`
-- `payoffAfterFold`
-- `pointAfterMobileClamp`
 - `charCount`
 - `charCountIncludingNewlines`
 - `firstLineChars`
@@ -346,37 +183,10 @@ Record:
 - `rewriteIfTruncated`
 - `compactFallback` when `previewBudgetStatus` is `warn`
 
-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` unless the receipt has
-`intentionalOpenLoop: true`, `specificClickQuestionVisible: true`, and
-`payoffPlannedImmediatelyAfterClamp: true`, or `pointAfterMobileClamp: true`
-unless the post is intentionally hiding the payoff for a specific see-more
-click. 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.
-
-## See-More Click Audit
-
-When the selected hook intentionally hides the payoff after the mobile fold,
-record:
-
-- `intentionalOpenLoop: true`
-- `openLoopType`
-- `visibleBeforeFold`
-- `clickQuestion`
-- `payoffAfterFold`
-- `firstPayoffLine`
-- `payoffArrivesWithinFirstBodySection`
-- `readerValueAfterClick`
-- `baitRisk`
-- `baitRiskMitigation`
-
-Open loops are allowed only when the body actually delivers the promised payoff.
-If the hook withholds the answer but the body switches topics, save as
-`needs_revision`.
+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.
 
 ## Simplifier / Concrete-Language Audit
 

package/skills/find-leads/SKILL.md

@@ -90,6 +90,7 @@ 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`
@@ -105,6 +106,9 @@ 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.
@@ -136,6 +140,8 @@ 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/create-post/references/linkedin-preview-rendering.md

@@ -1,176 +0,0 @@
-# LinkedIn Preview Rendering
-
-This asset defines the required rendered-preview contract for create-post hook
-research, hook candidate generation, gold-standard decomposition, and draft
-validation.
-
-Character budgets are only diagnostics. They are not the preview gate. A hook is
-not studied, selected, or ready until it has been rendered through this contract
-or through a stricter authenticated LinkedIn screenshot.
-
-## Rendering Basis
-
-LinkedIn does not publish exact feed truncation rules, and rendering can vary by
-surface, app version, device, media attachment, and account state. Use this
-deterministic renderer as the MCP review gate for unpublished drafts.
-
-When an authenticated LinkedIn feed/composer/browser screenshot is available,
-that screenshot is the strongest evidence. Still record the fields below so
-future agents can compare candidates without redoing the visual inspection.
-
-Observed public LinkedIn post text style for feed-style post pages:
-
-```text
-selector basis: p.attributed-text-segment-list__content
-font family: -apple-system, system-ui, "Segoe UI", Roboto, "Helvetica Neue",
-  "Fira Sans", Ubuntu, "Oxygen Sans", Cantarell, "Droid Sans",
-  "Lucida Grande", Helvetica, Arial, sans-serif
-font size: 14px
-line height: 21px
-font weight: 400
-letter spacing: normal
-white space: pre-wrap
-overflow wrap: break-word
-text color: rgba(0, 0, 0, 0.9)
-mobile text width: 308px
-desktop text width: 582px
-review clamp: first 3 rendered text lines
-```
-
-The `review clamp` is not an official LinkedIn rule. It is the conservative
-apples-to-apples region create-post must use when comparing hooks. Do not let a
-desktop pass rescue a mobile fail.
-
-## Required Rendering Record
-
-Every shortlisted source hook, adapted hook block, generated hook candidate, and
-selected hook must include a `renderedPreview` record:
-
-```text
-renderedPreview:
-  basis: linkedin_css_contract | authenticated_linkedin_screenshot | manual_user_source
-  cssContractVersion: linkedin-preview-rendering/v1
-  mobile:
-    textWidthPx: 308
-    fontSizePx: 14
-    lineHeightPx: 21
-    visibleTextBlock: <literal first rendered review-clamp block>
-    renderedLines:
-      - <line 1 exactly as wrapped>
-      - <line 2 exactly as wrapped>
-      - <line 3 exactly as wrapped>
-    lineCountBeforeClamp: <number>
-    blankLinesBeforeClamp: <number>
-    corePainProofOrCuriosityVisible: true | false
-    corePointVisible: true | false
-    intentionalOpenLoop: true | false
-    specificClickQuestionVisible: true | false
-    payoffPlannedImmediatelyAfterClamp: true | false
-    seeMoreClickReason: <why a reader would click see more>
-    seeMoreRisk: pass | warn | fail
-    screenshotPath: <optional local path>
-  desktop:
-    textWidthPx: 582
-    fontSizePx: 14
-    lineHeightPx: 21
-    visibleTextBlock: <literal first rendered review-clamp block>
-    renderedLines:
-      - <line 1 exactly as wrapped>
-      - <line 2 exactly as wrapped>
-      - <line 3 exactly as wrapped>
-    lineCountBeforeClamp: <number>
-    blankLinesBeforeClamp: <number>
-    corePainProofOrCuriosityVisible: true | false
-    corePointVisible: true | false
-    seeMoreRisk: pass | warn | fail
-    screenshotPath: <optional local path>
-  diagnostics:
-    charCount: <number>
-    charCountIncludingNewlines: <number>
-    firstLineChars: <number>
-    firstTwoPhysicalLinesChars: <number>
-    longestNonblankLineChars: <number>
-    blankLineVisualRisk: none | low | medium | high
-    pointAfterMobileClamp: true | false
-    openLoopType: none | hidden_payoff | contradiction | proof_gap | workflow_reveal | asset_reveal | story_gap
-    rewriteIfTruncated: <short fallback>
-```
-
-If a host cannot produce screenshots, it must still produce the literal wrapped
-line blocks using the CSS contract. If it cannot produce either screenshots or
-literal line wraps, return `blocked` or `needs_revision`; do not claim the hook
-passed preview validation from character counts alone.
-
-## Study Rules
-
-For source-post research:
-
-- Render the exact visible opening from full text when full text is available.
-- If only a search preview is available, render only the preview text and set
-  `basis: manual_user_source` or record `sourceTextBasis: search_preview`.
-- Lower confidence when the search preview is cut off or the body is
-  unavailable.
-- Extract hook lessons from the rendered first-screen experience, not from the
-  full post in isolation.
-
-For generated hooks:
-
-- Generate the hook from the selected premise first.
-- Render the hook for mobile and desktop before scoring it.
-- Score the rendered first-screen click reason before scoring cleverness.
-- If the goal is see-more clicks, the hook may intentionally hide the payoff
-  after the mobile clamp, but the visible block must create a specific question
-  the target reader wants answered.
-- Rewrite any candidate whose real point appears after the mobile clamp unless
-  that point is the planned payoff for an intentional open loop.
-
-## Pass, Warn, Fail
-
-Use these rendered gates:
-
-- `pass`: the mobile rendered preview shows the pain, proof, or curiosity by the
-  end of the first 3 rendered lines, and either the core point is
-  understandable without opening "see more" or an intentional open loop creates
-  a specific click question with an immediate planned payoff.
-- `warn`: the mobile rendered preview creates useful curiosity but the core
-  point or click question 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 visible open loop is vague, 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.
-
-A draft cannot be `ready` when the selected hook has:
-
-- no `renderedPreview`
-- `mobile.seeMoreRisk: fail`
-- `mobile.corePainProofOrCuriosityVisible: false`
-- `mobile.corePointVisible: false` unless `mobile.intentionalOpenLoop: true`,
-  `mobile.specificClickQuestionVisible: true`, and
-  `mobile.payoffPlannedImmediatelyAfterClamp: true`
-- `pointAfterMobileClamp: true` unless the point after the clamp is the
-  intentional payoff for a specific open loop
-
-## Report Format
-
-Research reports must show rendered preview blocks for the best examples and
-recommended draft directions:
-
-```text
-Rendered preview:
-mobile:
-<line 1>
-<line 2>
-<line 3>
-
-desktop:
-<line 1>
-<line 2>
-<line 3>
-
-verdict: pass | warn | fail
-why: <what is visible before the fold>
-```
-
-Do not say "it fits on mobile" without showing what the mobile reader actually
-sees.

package/skills/research/config.json

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