@sellable/mcp 0.1.258 → 0.1.259

package/skills/create-post/SKILL.md

@@ -60,9 +60,8 @@ Do:
 
 - capture rough ideas, voice memos, freestyle notes, and ad hoc prompts
 - research currently working LinkedIn hooks
-- reverse engineer why source hooks work, what shape to keep, and what not to copy
 - develop premise cards with real story/observed tension and reader value
-- explore many hook angle territories before choosing the winning hook
+- generate hook candidates
 - draft a post body that stays true to the source idea
 - run validation before calling a draft ready
 - save ideas, hook research, drafts, and published records under `~/.sellable/content/linkedin/**`
@@ -85,7 +84,6 @@ Before drafting, load all required assets with `mcp__sellable__get_subskill_asse
 3. `subskillName: "create-post", assetPath: "references/premise-development.md"`
 4. `subskillName: "create-post", assetPath: "references/post-validation.md"`
 5. `subskillName: "create-post", assetPath: "references/gold-standard-post-pack.md"`
-6. `subskillName: "create-post", assetPath: "references/linkedin-preview-rendering.md"`
 
 If any required asset is missing, unreadable, truncated without continuation, or internally inconsistent, return:
 
@@ -306,8 +304,7 @@ If local idea capture succeeds but auth/workspace is missing, keep the idea and
 
 ## Step 1: Hook Research
 
-Use `references/hook-research-playbook.md` and
-`references/linkedin-preview-rendering.md`.
+Use `references/hook-research-playbook.md`.
 
 If the host supports background agents, delegate the search/fetch/autopsy work
 to one bounded `research-worker` before hook candidate generation. The worker
@@ -319,16 +316,12 @@ and drafting gate.
 The research worker must return a compact packet only:
 
 - source examples kept and rejected
-- hook reverse-engineering autopsies: why each source hook works, which shape to
-  keep, what not to copy, and what payoff the body must deliver
 - full adapted hook blocks
-- angle territories tested before drafting
 - market belief map: resonating ideas, implicit beliefs, audience wants, resentments, fears, and credible controversy angles
 - premise inputs: real scenes, observed tensions, reader value openings, and proof gaps
-- reach-normalized signal notes, including follower-band fit when available
 - exact phrase patterns and sentence shapes
 - body structures and exact body language moves
-- rendered mobile and desktop preview records
+- preview measurements
 - track-person and gold-standard recommendations
 - blocked states or confidence gaps
 
@@ -339,24 +332,18 @@ the exact extracted phrase shapes.
 Default flow:
 
 1. Convert the idea into 3-8 search keywords.
-2. Call `mcp__sellable__search_engagement_posts` with an explicit multi-month window. Default to `maxAgeDays: 120`, tightening to 30-60 days only when the topic is trend-sensitive. When the user gives a follower range, pass it as `targetFollowerMin` and `targetFollowerMax`; for example, "8k-20k followers" means `targetFollowerMin: 8000` and `targetFollowerMax: 20000`.
-3. Shortlist posts by topic fit, rendered hook strength, content pattern replicability, creator repeat evidence, weighted engagement quality, and reach-normalized signal quality. Do not sort by raw engagement alone, and do not let the numeric reach score choose the final hook by itself.
-4. Because search results may only include previews, call `mcp__sellable__fetch_linkedin_posts` for shortlisted authors/profile URLs and match recent posts by URL/activity ID when full text is needed. If a promising source is missing follower count and the user requested reach normalization, call `mcp__sellable__fetch_linkedin_profile` on a bounded shortlist before treating the source as a keeper.
+2. Call `mcp__sellable__search_engagement_posts` with an explicit multi-month window. Default to `maxAgeDays: 120`, tightening to 30-60 days only when the topic is trend-sensitive.
+3. Shortlist high-engagement posts by topic fit, hook strength, creator repeat evidence, and weighted engagement quality.
+4. Because search results may only include previews, call `mcp__sellable__fetch_linkedin_posts` for shortlisted authors/profile URLs and match recent posts by URL/activity ID when full text is needed.
 5. If full text cannot be matched, record `full_text_unavailable` and use only the preview. Do not invent missing body details.
-6. Weigh shares/reposts above comments, comments above reactions, and reactions as weak reach unless paired with stronger signals. Normalize engagement against follower count when available: record `authorFollowerCount`, `targetFollowerBand`, `followerBandFit`, `engagementPer1kFollowers`, `weightedEngagementPer1kFollowers`, `reachPenaltyMultiplier`, `reachAdjustedScore`, and `baselineLift` when repeated creator posts make it possible. If follower count is unavailable, record `follower_count_unavailable`; if shares/reposts are unavailable, record `repost_data_unavailable`.
+6. Weigh shares/reposts above comments, comments above reactions, and reactions as weak reach unless paired with stronger signals. If shares/reposts are unavailable, record `repost_data_unavailable`.
 7. Penalize lead-magnet or giveaway mechanics unless the user explicitly asks for a lead magnet post.
 8. Build a market belief map before hook generation: what the space is rewarding, what the audience implicitly believes, what they want permission to say, what they resent or fear, what they will argue with, and which controversial angle the user can credibly own. If the user's raw idea is internally coherent but not attached to a live market tension, do not draft from the internal idea alone; present stronger directions or rewrite the draft angle around the external tension.
 9. Extract premise inputs: real story/scene possibilities, observed tensions, useful reader takeaways, and proof gaps. A good hook cannot rescue a premise with no value.
 10. For story posts, extract the story mechanism that made the post work, not just the first line.
 11. Extract hook structures plus specific reusable words, phrases, sentence
    shapes, transitions, and body language patterns.
-12. For each keeper, create a `hookAutopsy`: the source mechanism, open-loop
-   type, click question, promised payoff, specificity anchor, tension opened,
-   source shape to keep, source words not to copy, and adaptation rule for the
-   user's idea.
-13. Render each kept source hook and adapted hook block through the LinkedIn
-   preview rendering contract. Character counts alone are not enough.
-14. Save the research with `mcp__sellable__save_hook_research`.
+12. Save the research with `mcp__sellable__save_hook_research`.
 
 Record provenance:
 
@@ -365,29 +352,18 @@ Record provenance:
 - search window
 - source post URLs
 - authors/profile URLs
-- author follower counts and target follower-band fit when available
 - engagement totals and available likes/comments/shares breakdown
-- reach-normalized scoring fields and confidence notes
 - creator repeat evidence
 - lead-magnet or engagement-bait penalties
 - story mechanism when relevant
 - full-text match status
-- source hook rendered preview records and whether they came from full text,
-  authenticated LinkedIn screenshots, or a search preview
+- source hook preview measurements and whether they came from full text or a search preview
 - selected hook patterns
-- hook reverse-engineering autopsies, including `clickQuestion`,
-  `promisedPayoff`, `sourceShapeToKeep`, `sourceWordsNotToCopy`, and
-  `adaptationRule`
 - market belief map and selected controversy
 - premise cards and selected premise
 - exact phrase patterns and sentence shapes
 - body structures and body language patterns
 - why each pattern fits the user's idea and voice
-- `whyTheHookCarries`: why the selected hook works from the words, tension, and
-  content pattern independent of the source creator's reach
-- `whyTheReachEvidenceIsTrustworthy`: follower-band fit, reach-adjusted score,
-  baseline lift, share/comment quality, or why a large-account example is only
-  secondary pattern evidence
 
 ## Step 1.5: Research Learning Report
 
@@ -413,9 +389,6 @@ Research status:
 - keywords:
 - full-text coverage:
 - repost/share data:
-- target follower band:
-- reach-normalized winners:
-- big-account examples used only as secondary pattern evidence:
 
 Best source examples:
 1. author, URL, engagement, why kept, why not copied
@@ -436,15 +409,7 @@ Premise cards:
 Hook patterns learned:
 1. full adapted hook block
    - source mechanism:
-   - open-loop type:
-   - click question:
-   - promised payoff:
-   - source shape to keep:
-   - source words not to copy:
-   - rendered preview:
-     - mobile visible block:
-     - desktop visible block:
-     - verdict:
+   - preview budget:
    - internal question:
    - why it fits / why it does not:
 
@@ -472,9 +437,9 @@ Save recommendations:
 - gold-standard candidates:
 
 Recommended draft directions:
-1. premise card + hook territory + hook block + click question + body structure
-2. premise card + hook territory + hook block + click question + body structure
-3. premise card + hook territory + hook block + click question + body structure
+1. premise card + hook block + body structure
+2. premise card + hook block + body structure
+3. premise card + hook block + body structure
 ```
 
 Keep this report concise enough to read, but concrete enough that another agent
@@ -508,48 +473,17 @@ unless the premise still has concrete reader value.
 
 ## Step 2: Hook Candidates
 
-Generate a hook angle matrix from the selected premise before writing the post
-body. Do not generate hooks directly from the raw idea before the premise is
-selected.
-
-Minimum exploration:
-
-- normal drafting: at least 8 distinct angle territories and 24 hook candidates
-- hook-critical requests, "nail the hook," "a ton of angles," or space research:
-  at least 12 distinct angle territories and 40 hook candidates
-- smaller set only when the user explicitly asks for fewer options
-
-Angle territories must be genuinely different. Use options such as enemy/tool
-contrast, hidden asset, first-person build proof, workflow reveal, contrarian
-category claim, mistake/confession, market timing, operator pain,
-asset/free-reveal without comment bait, specific person/company signal,
-before/after transformation, and question hook.
+Generate at least 12 hook candidates from the selected premise unless the user
+requested a smaller set. Do not generate hooks directly from the raw idea before
+the premise is selected.
 
 Each hook must include:
 
 - selected premise
-- angle territory
 - premise tension opened
 - reader value implied
 - source hook pattern
-- source shape kept
-- source words not copied
 - why it fits this idea
-- `renderedPreview` using `references/linkedin-preview-rendering.md`
-- `mobileRenderedPreviewBlock`
-- `desktopRenderedPreviewBlock`
-- `mobileRenderedLines`
-- `desktopRenderedLines`
-- `firstScreenPromise`
-- `intentionalOpenLoop`
-- `specificClickQuestionVisible`
-- `seeMoreClickReason`
-- `clickQuestion`
-- `payoffAfterFold`
-- `bodyProofObligation`
-- `corePainProofOrCuriosityVisibleMobile`
-- `corePointVisibleMobile`
-- `pointAfterMobileClamp`
 - `charCount`
 - `charCountIncludingNewlines`
 - `firstLineChars`
@@ -566,50 +500,26 @@ Each hook must include:
 - `rewriteIfTruncated`
 - proof/story dependency
 - AI-tell risk
-- why it should win
-- why it should lose
 - score
 
 Do not copy source wording. Copy only the structure.
 
-Render every candidate before scoring it. The LinkedIn preview rendering
-contract is the gate; character counts are secondary diagnostics only. Use the
-deterministic CSS contract when no authenticated LinkedIn screenshot is
-available:
-
-- mobile text width: `308px`
-- desktop text width: `582px`
-- font size: `14px`
-- line height: `21px`
-- white space: `pre-wrap`
-- overflow wrap: `break-word`
-- review clamp: first 3 rendered text lines
-
-Use the rendered gates from `references/linkedin-preview-rendering.md`:
-
-- `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.
+Use this conservative mobile-first LinkedIn preview gate. LinkedIn does not
+publish exact "see more" cutoff rules, and rendering varies by device, app
+version, font, media, and line break. These are v1 safety budgets, not claims
+about an official LinkedIn limit:
+
+- `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 `desktopPreviewFit`, but
 never let desktop fit compensate for a mobile `fail`.
 
-If a hook's point depends on text after the rendered mobile preview clamp,
-rewrite it before selecting it unless the hook is intentionally using a
-see-more open loop. Intentional open loops must show a specific click question
-inside the mobile clamp and must define the first payoff line after the fold. A
-selected hook may carry a `warn` only when the warning is explicit and the
-validation receipt includes a compact fallback. A hook with no rendered mobile
-and desktop preview record cannot be selected.
+If a hook's point depends on text after the likely preview, rewrite it before
+selecting it. A selected hook may carry a `warn` only when the warning is about
+intentional blank-line rhythm or a slight line-length overage; include a compact
+fallback in the validation receipt.
 
 ## Step 3: Draft
 
@@ -639,14 +549,10 @@ Every saved draft needs a validation receipt with:
 - selected premise card
 - candidate hooks considered
 - selected hook and why
-- hook reverse-engineering audit
-- hook angle matrix summary
-- see-more click audit
 - proof claims used and source
 - story/proof files consulted
 - gold standards consulted
 - LinkedIn preview audit
-- rendered mobile and desktop hook preview blocks
 - premise/value audit findings
 - simplifier/concrete-language audit findings
 - voice audit findings

package/skills/create-post/references/gold-standard-post-pack.md

@@ -119,8 +119,6 @@ Show compact candidate cards. Include:
 - why it might belong in the pack
 - hook mechanism
 - hook preview budget status and measurement basis
-- rendered mobile preview block and verdict
-- rendered desktop preview block and verdict
 - content/body mechanism
 - rhythm notes
 - sentence-structure notes
@@ -196,15 +194,6 @@ Tags:
 - longest nonblank line chars:
 - blank-line visual risk:
 - source text basis:
-- render basis:
-- css contract version:
-- mobile rendered preview block:
-- desktop rendered preview block:
-- mobile rendered lines:
-- desktop rendered lines:
-- core pain/proof/curiosity visible on mobile:
-- core point visible on mobile:
-- point after mobile clamp:
 - preview budget status:
 - mobile preview fit:
 - desktop preview fit: