Skip to content
Agentmart
Submit a tool

linkedin-post-hook-lab

Turn a pasted LinkedIn post brief, draft opener, and approved proof into evidence-bounded two-line hooks, a “see more” bridge, and a post-opening package.

Skill by anicca

IndexedMIT★ 8
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/daisuke134-linkedin-post-hook-lab

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Turn a pasted LinkedIn post brief, draft opener, and approved proof into evidence-bounded two-line hooks, a “see more” bridge, and a post-opening package. Use for LinkedIn post openings, not posting, audience analytics, or performance prediction.

Use cases: data

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/linkedin-post-hook-lab

What's inside

Skill name
linkedin-post-hook-lab
Description
Turn a pasted LinkedIn post brief, draft opener, and approved proof into evidence-bounded two-line hooks, a “see more” bridge, and a post-opening package. Use for LinkedIn post openings, not posting, audience analytics, or performance prediction.
License
MIT
Compatibility
Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent
Metadata
stage: S2-Content · author: anicca · version: 1.0
Instructions
183 lines in SKILL.md · view on GitHub

Files (4)

  • LISTING.md
  • SKILL.md
  • verified-demonstration.md · evidence/
  • icon.svg

SKILL.md (first lines)

# LinkedIn Post Hook Lab

LinkedIn Post Hook Lab turns one buyer-supplied post brief into a text-only opening
package for a LinkedIn post. It keeps approved proof, editorial framing, and unknowns
separate so a stronger first two lines do not become a stronger unsupported claim.

## Stage

This skill belongs to Stage S2: Content.

## When to Use

- A B2B founder has a draft LinkedIn post whose first two lines do not clearly earn the reader's attention.
- A subject-matter expert has an approved insight, example, or customer-safe proof point and needs several opening angles.
- A content lead needs a “see more” bridge and first-paragraph structure without turning a short brief into invented evidence.
- A team needs a repeatable text-only opening package for a new LinkedIn post each week.

## Input Schema

```text
post_goal: string (required) — the reader action, lesson, or discussion the post should support
audience: string (required) — intended LinkedIn reader
topic_or_offer: string (required) — subject, product, lesson, or point of view
draft_or_source_material: string (required) — pasted rough opener, notes, or source text
approved_proof: string (optional) — buyer-approved facts, examples, quotations, or constraints
tone: string (optional) — e.g. direct, reflective, technical, conversational
cta: string (optional) — buyer-approved closing invitation
constraints: string (optional) — banned wording, compliance rules, length, or brand requirements
```

## Workflow

### Step 1: Establish the evidence boundary

Extract supplied facts, quotations, audience, topic, CTA, and constraints into an
evidence ledger. Mark a missing fact `[ADD: ...]`; do not invent customer results,
metrics, prices, employer facts, or product capabilities. Quality bar: every factual
phrase proposed for a hook has a source phrase or an explicit `[ADD: ...]` marker.

### Step 2: Diagnose the supplied opening

Identify the first two lines, reader cue, stated tension, promised value, and the
point at which a reader would need more context. If no draft is supplied, report
`No draft opening supplied`. Quality bar: each diagnosis is labelled `supplied`,
`inference`, or `unknown` rather than presented as a platform observation.

### Step 3: Create distinct opening angles

Write five two-line hooks using distinct structures: specific observation, contrast,
question, process moment, and misconception. Keep the supplied audience and topic;
when an angle needs unsupplied proof, retain it only with `[ADD: proof]`. Quality bar:
no two options rely on the same first claim or rhetorical structure.

### Step 4: Build the recommended post opening

Choose the strongest supported hook and expand it into a first paragraph, a “see
more” bridge, and a second-paragraph handoff. This is text for review, not a posted
LinkedIn update. Quality bar: the bridge introduces only the supplied lesson or a
clearly marked question; it does not imply views, engagement, or authority.

### Step 5: Add supporting copy and a claim check

Return three post titles or internal labels, the supplied CTA (or `[ADD: CTA]`), and
a self-critique for vague framing, unsupported proof, audience mismatch, or compliance
review. Quality bar: the critique lists at least one limitation and makes no claim of
post reach, leads, replies, or conversion.

## Output Schema

```text
output_schema_version: "1.0.0"
evidence_ledger: EvidenceItem[]
opening_diagnosis: OpeningDiagnosis
hook_options: LinkedInHookOption[5]
recommended_opening: LinkedInOpeningPackage
supporting_copy: SupportingCopy
honesty_check: HonestyCheck
```

## Output Format

```markdown
# LinkedIn Post Hook Lab: [topic]

## Evidence boundary
- Supplied: [fact or constraint]
- Unknown: [ADD: missing fact]

## Opening diagnosis
- First two lines: [supplied lines or No draft opening supplied]
- Reader cue: [supplied / inference / unknown]
- Tension: [diagnosis]

## Five hook options
1. **[structure]**
   [first line]
   [second line]
   Evidence: [supplied source or ADD marker]

## Recommended opening package
- First two lines: [text]
- First paragraph: [text]
- “See more” bridge: [text]
- Second-paragraph handoff: [text]

## Supporting copy
- Internal label: [text]
- CTA: [supplied CTA or ADD marker]

## Honesty check
- [unsupported claim removed or missing proof]
```

## Error Handling

- **No usable source material:** Ask for the audience, post goal, topic, and pasted notes or rough opener; do not fabricate an expert point of view.
- **Unsupported outcome claim:** Replace it with `[ADD: approved proof]` or a process-based statement.
- **Conflicting audience or CTA:** Preserve both supplied directions and ask which instruction governs the recommendation.
- **Request to post or inspect results:** Explain that the skill produces text for review from pasted material; it does not publish, access LinkedIn, or measure engagement.

From Daisuke134/life-manager, MIT.

More from Daisuke134/life-manager

Signals

Stars
8
Forks
2
Open issues
2,737
Last commit (this folder)
Oct 4, 2026 (24 days ago)
Last release
Aug 15, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Version
1.0
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from anicca

Cite this page

linkedin-post-hook-lab skill. Agent Mart. https://agentmart.dev/skills/daisuke134-linkedin-post-hook-lab (last updated 2026-10-24)