Skip to content

coreyhaines31/makerskills / skills/jab-hook

jab-hook

Verified

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."

references/voice.md

View on GitHub
# Voice — your personal posts

First-person "I" voice. Direct, dry, conviction-coded. No hype.

## Voice rules (load-bearing)

1. **Conviction-coded CTAs over transactional** — "lock it in" beats "book a call now." "Grab the playbook" beats "click here to download." Make the CTA sound like a decision, not a transaction.
2. **Reader-perspective framing** — write what the reader gets, not what the user provides. "What you're guaranteed" not "what we'd guarantee." "You'll know X" not "we'll teach you X."
3. **Lead with a take, not a question** — questions feel needy; takes feel earned.
4. **One idea per post** — if it sprawls, split into a thread or cut it.
5. **Short sentences. Specific nouns. Verbs that do work.**

## Voice anti-patterns (starting list — iterate)

- No emojis as decoration. Rare and pointed only.
- No "🚀 💡 🔥" cliches, ever.
- No "BTW," "PSA," "hot take," "unpopular opinion" openers — they signal weakness.
- No "thread 🧵" labels — the thread structure speaks for itself.
- No hashtags.
- No "Just dropped," "Just shipped" unless something actually shipped today.
- No questions just to bait engagement.

## Link placement (load-bearing)

- **Default: no link in the post body.** Many promo posts work better with no link at all — let curiosity drive people to profile or search. Mention the property by name; trust the reader.
- **When a link is needed: put it in a first comment below the post, not in the body.** Platforms downrank posts with outbound links. The comment also lets the link be richer (longer, with context) without bloating the post.
- Never inline a URL inside the post body.

## Per-platform

### X
- Single post default, ≤280 chars
- Thread only if post #2 earns its place (genuinely adds, not just continues)
- Link goes in a reply to the original post, not in the post itself
- Reply game matters more than posting volume — note in plans when a post is "join the conversation" worthy

### LinkedIn
- 200–400 chars body. No URL in the body.
- Link goes in a first comment (Typefully supports this on LinkedIn drafts)
- No hashtags (the user doesn't use them)
- First line is the hook — gets cut off in feed if too long, so make line 1 self-contained

## Iterate me

This is a starting point. Add rules here as they come up. Trim rules that turn out wrong.

---

## Local overlay (your personal voice DNA)

The rules above are a sensible public default. To layer your specific voice on top (your tics, your phrasings, your callbacks):

1. Create `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/jab-hook/voice.local.md`
2. Put your additional voice rules / banned phrases / personal stylistic preferences in there
3. The `jab-hook` skill loads `voice.md` first (this file, generic), then `voice.local.md` (yours, additive) so your personal rules override or extend the defaults

Example local overlay content:
- Your own banned phrases beyond the AI-slop list
- Personal sign-offs you do/don't use
- Conviction-coded CTA phrasings unique to you
- Account-specific tics (e.g., "always use 'lock it in' instead of 'book a call' on agency posts")

`voice.local.md` is gitignored — your personal voice DNA never enters this repo.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall