本文へ移動
cccskills
無料GitHub で公開

jab-hook

Gary Vaynerchuk's jab-jab-jab-right-hook framework applied to a personal portfolio rotation on X and LinkedIn. Jabs = build-in-public + educational (value). Hooks = promo (the ask). Each property in the user's configured portfolio (see `~/.config/makerskills/jab-hook/properties.yaml`) gets a hook at least once every ~3 weeks; jabs fill the rest. Drafts go into the user's Typefully workspace via MCP. Modes — plan (7-day plan), pick-next (single post), audit (coverage report), draft (specific post). Triggers on "/jab-hook," "what should I post," "plan my socials," "next promo," "next jab," "next hook," "social rotation," "promote [property]," "BIP post," "audit my socials," "what haven't I posted about."

インストール方法を見る

含まれるファイル(10)

  • SKILL.md8.1 KB
  • references/content-types.md3.4 KB
  • references/inspiration.example.md3.3 KB
  • references/inspiration.md3.6 KB
  • references/patterns.md1.6 KB
  • references/properties.example.yaml1.7 KB
  • references/properties.md1.6 KB
  • references/typefully-config.example.yaml1.0 KB
  • references/typefully-config.md1.2 KB
  • references/voice.md3.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

/jab-hook — Jab-jab-jab-right-hook for a personal portfolio

Gary Vaynerchuk's framework applied to your configured portfolio: keep the feed mostly jabs (value — BIP + educational) so the hooks (promo) earn attention when they land. Drafts to your personal Typefully workspace.

One-time setup: see references/properties.md and references/typefully-config.md to configure your real portfolio + workspace. Personal config lives in ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/jab-hook/.

Mental model

  • N rotation slots (configured in ~/.config/makerskills/jab-hook/properties.yaml): one per property you want to promote on rotation
  • ~2 promo posts/week → each property cycles every ~3 weeks at equal weight
  • Non-promo days: 50/50 build-in-public vs educational
  • Target weekly rhythm: ~2 promo + ~2–3 BIP + ~2–3 educational
  • Platforms: X + LinkedIn via your personal Typefully workspace

Step 1 — Pick the mode

Detect from the trigger:

User saysMode
"plan my socials," "next week's posts"plan
"what should I post," "next promo," "pick next"pick-next
"audit my socials," "what's overdue," "what haven't I posted about"audit
"draft a promo for X," "BIP post about Y," "educational about Z"draft

If ambiguous, confirm.

Step 2 — Load context

  1. Read references/properties.md — the 6 rotation slots and angle ideas
  2. Read references/voice.md — the user's voice rules per platform
  3. Read references/content-types.md — templates for promo / BIP / educational
  4. Pull recent posts from your personal Typefully workspace:
    • First run: call the Typefully MCP server's list-social-sets tool and ask which social set is your personal (X + LinkedIn). Save the ID to ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/jab-hook/typefully.yaml for future runs (schema in references/typefully-config.example.yaml — never save it inside the skill folder; upgrades wipe it).
    • Call its list-drafts tool, filtered to the last 30 days
    • Classify each as promo / BIP / educational by content
  5. Compute days since last promo for each of the 6 slots

Step 3 — Mode logic

plan (7-day plan)

  • Slot the 1–2 most overdue properties as promo posts
  • Fill remaining 5 days with alternating BIP and educational (50/50)
  • Output as a table: Day | Type | Property/Topic | Hook | Draft summary
  • Don't stack two promo on consecutive days
  • After the user approves the plan, offer to draft each one in sequence

pick-next

  • Identify the most overdue property
  • If most overdue < 14 days, suggest a BIP or educational instead (whichever is less recent)
  • Draft 1 post; ask before syndicating

audit

  • Report: days since last promo per property, ordered by most overdue
  • Flag any property >21 days as overdue
  • Suggest the next 1–2 moves

draft

  • Skip rotation logic — draft the requested post
  • Use the right content-type template

Step 4 — Draft

Follow references/voice.md and references/content-types.md. Default: single post, one per platform (X version + LinkedIn version). Thread only if the second post earns its place.

Link placement (load-bearing): never put a URL in the body. Default is no link at all — let curiosity drive the click. When a link is needed, draft it as a first comment for LinkedIn (Typefully supports auto-comment) or a reply for X. The body always stands alone.

Optional: inspiration scan

For promo and educational posts, optionally scan inspiration accounts (references/inspiration.md) before drafting:

  1. Pick 1–2 accounts whose audience overlaps with the property
  2. Pull recent posts (agent-browser if it works on LinkedIn; otherwise ask the user to paste examples or fall back to their X/newsletter)
  3. Extract structural patterns: hook openers, post length, line-break rhythm, CTA styles
  4. Apply ONE pattern to the user's voice — never mimic phrasing
  5. Log new patterns in ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/jab-hook/patterns.local.md (create if missing) so they accumulate — references/patterns.md documents the starter patterns and stays read-only

Skip inspiration scan when the user says "just draft it" or when iterating on an existing post.

Step 5 — Syndicate to Typefully

Ask: "Push to Typefully now? (X + LinkedIn, your personal workspace)"

If yes:

  1. Read social set ID from ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/jab-hook/typefully.yaml (setup notes in references/typefully-config.md)
  2. Call the Typefully create-draft tool once for X, once for LinkedIn (or once with both platforms if the social set spans both)
  3. If the draft has a first-comment link, configure Typefully to add it automatically (LinkedIn auto-comment / X reply). If the MCP doesn't support auto-comment for one of the platforms, surface the comment text so the user can paste it after publishing.
  4. Default to draft state (not scheduled) — the user reviews in Typefully UI before sending
  5. Return the Typefully draft URLs

Composes with

  • paste — clean output for pasting into Typefully / LinkedIn / X manually if the MCP path doesn't fit
  • social-fetch — pull inspiration-account posts for structural analysis (replaces inline agent-browser)
  • second-brain — the Content Ideas wiki page hoppers hooks, frameworks, stories; /jab-hook drafts pull candidates from there
  • deep-research — when a promo needs a stat or citation the draft doesn't have yet
  • marketingskills:social — generic social frameworks, useful when teaching strategy vs shipping your own posts
  • marketingskills:copywriting — for hook / headline ideation when stuck

Notes on quality

  • 1 promo per week per property is the floor, not the ceiling. Rotation compounds when it's predictable — 4 properties × 1 promo/week = 4 promo weeks/month. Educational + BIP + community fill the rest.
  • Never mimic phrasing from inspiration accounts. Extract structure (hook opener type, line-break rhythm, CTA style) and apply to your own voice. Voice is the moat; copying phrasing destroys it.
  • Links belong in first comments, not the body for LinkedIn + X. Documented in feedback_social_link_placement.md in your memory store (see below). Body posts with inline URLs get algorithm-suppressed on both platforms.
  • Draft state, not scheduled state. Every Typefully push defaults to draft — human review in the Typefully UI before publish is non-negotiable. Automated scheduling of unreviewed drafts has repeatedly produced posts the user regrets.
  • Reader-perspective framing. "You'll know X" not "we'll teach you X." "What you're guaranteed" not "what we'd guarantee."
  • Voice.local.md overrides the shipped voice.md. Personal voice rules never live in the public repo — always in ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/jab-hook/voice.local.md.
  • Cadence cap: 2 posts/day per platform, per account. More than that degrades reach + reads as spam.

Memory references

Your memory store is your agent's persistent memory if it has one (Claude Code's memory directory, for example), otherwise ${MAKERSKILLS_MEMORY:-${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/memory}/.

  • feedback_promo_voice.md in your memory store (if present) — conviction-coded CTAs + reader-perspective framing
  • feedback_social_cadence.md in your memory store (if present) — cadence cap (e.g., 2 posts/day per platform)

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

When you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not "marketing ideas for a product" (that's marketing-skills:marketing-ideas) — this is "should this business exist + can you win it." Runs the idea through a structured framework (problem, audience, wedge, monetization, moat, portfolio fit, distribution, energy fit, opportunity cost), checks domain availability via /domain, optionally triggers /deep-research for market validation, and outputs a viability brief: build / sleep on it / pass. Archives every idea to ~/.config/makerskills/business-brainstorm/archive/ so past work is searchable. Triggers on "/business-brainstorm," "/brainstorm," "new business idea," "should I build X," "pressure test this idea," "validate this idea," "is X a good business," "what about a [type] for [audience]."

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/makerskills8562026年10月9日 更新

Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X."

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/makerskills8562026年10月9日 更新

Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to leadership. Modes — monthly (default; the standing report), weekly (thin cash pulse), scenario (ad-hoc modeling in the projector), pickup (resume where the prior run left off). Anonymized team-scope sibling to personal-cfo (which handles personal household finances). Composes with company-brain (report gets stored + wiki-indexed there), toolify (wire company-specific data sources), loopify (schedule the monthly + weekly runs). Triggers on "/company-cfo," "/cfo," "monthly cash report," "do the CFO snapshot," "CFO monthly," "let's run CFO," "cash projection," "runway forecast," "monthly financials," "cash pulse."

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/makerskills8562026年10月9日 更新

decide

無料

When you have a decision to make and want a structured workflow that picks the load-bearing questions, walks through them, reaches a call (or "wait"), and archives the rationale for future reference. Based on the 37signals Guide to Making Decisions (38 questions) plus house additions like Q39 opportunity cost ("what does saying yes displace?"). Triages to 6–8 relevant questions per decision instead of forcing the full set. Archives every decision to ~/.config/makerskills/decide/archive/ with a revisit date so you can check later whether the call was right. Triggers on "/decide," "help me decide," "should I [X]," "I need to make a decision about," "stuck on a decision," "deciding between," "go/no-go on," "what should I do about." This is both the decision-making workflow AND the decision log — making the decision is the act of logging it.

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/makerskills8562026年10月9日 更新

When you want multi-source, multi-step research on a topic — competitor research before a sales call, market research for a new business idea, positioning angles, due diligence on a partnership or podcast guest, tech decision research (which DB, which auth), or any "I need to actually understand X." Combines web search, URL fetch, agent-browser, last30days (Reddit/X/YouTube/HN/web recency), memory, and Notion. Outputs a structured brief with citations, contradictions, gaps, and recommended next steps. Archives every research run to ~/.config/makerskills/deep-research/archive/ so past work is searchable. Triggers on "/deep-research," "research X," "investigate X," "do a deep dive on X," "look into X," "what's actually happening with X," "due diligence on X," "validate this market." Differs from a one-shot web search: this is multi-pass with verification.

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/makerskills8562026年10月9日 更新

domain

無料

When you want to brainstorm and check available .com domains for a new project — brand naming, aftermarket pricing (HugeDomains / Afternic / Sedo / Dan), USPTO trademark screening, and social handle availability. Built on Laura Roeder's "work backwards from availability" method. Combines Vercel CLI, whois, Domainr, Namecheap, and agent-browser, each for what it reliably does. Workflow: budget → brainstorm → availability check → whois cross-check → price → aftermarket sweep (plus liveness probe and drop-watch) → bucket → negotiate → trademark + socials → buy. Triggers on "/domain," "find a domain," "check domain availability," "brainstorm a domain," "what .com is available for X," "domain hunt," "name my project," "is X.com available," "aftermarket price on X.com," "trademark check for X."

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/makerskills8562026年10月9日 更新

coreyhaines31 のスキルをすべて見る

このスキルの問題を報告する