Write a LinkedIn headline

Personal assistantKINDA1 method

KINDA — AI can help, with a person in the loop.

1 method on the page: 1 prompt.

Use cases

Methods

Paste into a general LLM and write a LinkedIn headline.

prompt

LLMPrompt

Prompt

Copied 0

## Role
You are a LinkedIn copywriting specialist focused on creating high-impact profile headlines that drive visibility and engagement.

## Task
Craft a professional LinkedIn headline (maximum 220 characters) that showcases expertise, communicates a unique value proposition, and is optimized for LinkedIn search.

## Context
The headline must:
- Clearly convey core expertise and what sets the professional apart
- Appeal directly to the target audience or industry
- Include relevant SEO keywords to maximize discoverability
- Be concise, attention-grabbing, and professional

## Input
{{professional-profile}}
Include: your expertise/skills, target audience or industry, what makes your approach unique, and relevant SEO keywords for your field.

## Process
1. Identify the core expertise and most compelling professional strengths
2. Extract the unique value proposition—what differentiates this professional from peers
3. Integrate SEO keywords naturally without compromising readability
4. Combine all elements into a headline under 220 characters
5. Optionally add a brief phrase that reflects personality or professional philosophy if it strengthens impact

## Output
Provide the finished LinkedIn headline, ensuring it is:
- Fully visible on LinkedIn profiles (≤220 characters)
- Keyword-optimized for target audience searches
- Distinctive and memorable
- Professional and credible

Example format: "Data-Driven Marketing Strategist | Elevating Brands with Innovative Campaigns | SEO & Content Marketing Expert | Turning Insights into Action"

Add a method

How you would do this use case, in plain words. Anyone can post.

The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.

All use cases:GET /api/jobs
This use case:GET /api/jobs/write-linkedin-headline
Schema:GET /api/jobs/schema
Add a method: POST /api/jobs/method — same fields as the form. No API key yet.

A bad request returns JSON like {"error":"Method description is required"} with status 400.

Field	What it is
`jobId`	This use case. Review queue uses `useCaseTitle` + `email` instead.
`summary`	Method description. Shown on the card. Also accepts `title`.
`products`	Optional. Array of `{ name, url }`. Legacy: `tools`.
`prompts`	Optional. Array of prompt strings. Legacy: one `prompt` string.
`skills`	Optional. Array of `{ text, url }`. Legacy: `skill` + `skillUrl`.
`authorName`	Author name. Legacy live field: `postedBy`.
`author`	Optional 𝕏 handle. Legacy live field: `creditHandle`.
`parts`	Optional. Inferred from products, prompts, and skills if omitted.`standalone-product`, `ai-agent`, `ai-tool`, `skill`, `prompt`. Do not send a prompt/product/agent/skill radio.

{
  "jobId": "write-linkedin-headline",
  "summary": "Turns a Zoom recording into notes and action items with owners",
  "products": [
    {
      "name": "Claude",
      "url": "https://claude.ai"
    }
  ],
  "prompts": [
    "Turn this transcript into notes and action items with owners."
  ],
  "skills": [
    {
      "text": "Watch a folder. When a transcript lands, write notes with owners.",
      "url": "https://example.com/zoom-notes.md"
    }
  ],
  "authorName": "Alex Rivera",
  "author": "@handle"
}