Profile Optimizer

Profile Optimizer

Codex and Claude runtime

• Use this skill in Codex or Claude with the tools actually available in the current task. AskUserQuestion examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
• Work in the user-selected project. Read its about-me.md, voice.md and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run voice-builder; never inherit the maintainer's identity, accounts or private files.
• Resolve bundled references/ relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical about-me.md, voice.md or newsletter-voice.md in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
• Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
• Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.

Visual completion state

This skill's image prompts are prompt-ready, not generated or visually reviewed assets. Keep its named Gemini workflow unless the user requests another generator. A missing image service does not block writing a prompt. When images are supplied or generated, open and inspect each export at full size and feed size (about 360px wide, 320px for thumbnails). Check exact copy, dimensions, clipping, legibility, brand colours, font appearance, logos and reference fidelity. Fix and re-inspect failed exports. Record any unavailable export or inspection as pending. An image prompt or raster export is not an editable design file.

CRITICAL: Auto-start on load

When this skill triggers, go straight to Step 1. Do not summarise. Do not explain what you will produce. Start input gathering immediately.

Step 1. Gather inputs

Check the project for about-me.md. If it exists, pre-fill name, audience, topics, and POV from it. Skip those questions and tell the user what you pulled.

Call AskUserQuestion in two batches.

Batch 1

[
  {
    "question": "What is the primary goal of your LinkedIn presence?",
    "header": "Goal",
    "multiSelect": false,
    "options": [
      {"label": "Booked calls", "description": "Drive discovery calls or demos"},
      {"label": "Inbound leads", "description": "Attract prospects who reach out to you"},
      {"label": "Newsletter subscribers", "description": "Grow your email list from LinkedIn"},
      {"label": "Job opportunities", "description": "Get recruiters and hiring managers to reach out"}
    ]
  },
  {
    "question": "What is your main offer or service?",
    "header": "Offer",
    "multiSelect": false,
    "options": [
      {"label": "Coaching", "description": "1-on-1 or group coaching"},
      {"label": "Consulting", "description": "Advisory or strategy work"},
      {"label": "Agency services", "description": "Done-for-you services for clients"},
      {"label": "Freelance", "description": "Project-based or contract work"}
    ]
  },
  {
    "question": "Do you have brand colours (hex codes)?",
    "header": "Colours",
    "multiSelect": false,
    "options": [
      {"label": "No, suggest for me", "description": "Pick colours based on my positioning"},
      {"label": "Yes, I will paste them", "description": "I have specific hex codes to use"}
    ]
  },
  {
    "question": "Any social proof you want highlighted?",
    "header": "Proof",
    "multiSelect": false,
    "options": [
      {"label": "Years of experience", "description": "e.g. 10+ years in marketing"},
      {"label": "Client results", "description": "e.g. Helped 200+ clients"},
      {"label": "Media features", "description": "e.g. Featured in Forbes"},
      {"label": "I will type my own", "description": "Let me paste specific proof points"}
    ]
  }
]

Batch 2

[
  {
    "question": "What external links do you want in your Featured Section? (max 2)",
    "header": "Links",
    "multiSelect": false,
    "options": [
      {"label": "Booking page + newsletter", "description": "Primary link to book calls, secondary to subscribe"},
      {"label": "Portfolio + booking page", "description": "Show work first, then convert"},
      {"label": "I will paste URLs", "description": "I have specific links to use"}
    ]
  },
  {
    "question": "How should I get your current profile?",
    "header": "Current profile",
    "multiSelect": false,
    "options": [
      {"label": "I will paste it", "description": "I will copy-paste my headline, about, and experience"},
      {"label": "Start fresh", "description": "Ignore my current profile, build from scratch using my about-me.md"},
      {"label": "I will upload a screenshot", "description": "I will share a screenshot or PDF of my profile"}
    ]
  }
]

Wait for all inputs before proceeding.

Step 2. The Headline

Write 3 headline options. Output in a code block.

Constraints:

• Maximum 50 characters each
• Sentence casing only (not Title Case)
• Lead with core value
• Include target audience where character count allows
• No job titles (no "Founder" / "CEO" / "Designer")
• No fluff words

Format: [Core value] + [for target audience]

Option 1 (Direct): [outcome + audience]
Option 2 (Pain-focused): [problem + audience]
Option 3 (Differentiator): [unique angle + audience]

Then call AskUserQuestion to let the user pick:

[
  {
    "question": "Which headline do you want to go with?",
    "header": "Headline",
    "multiSelect": false,
    "options": [
      {"label": "Option 1", "description": "[The actual headline text from above]"},
      {"label": "Option 2", "description": "[The actual headline text from above]"},
      {"label": "Option 3", "description": "[The actual headline text from above]"}
    ]
  }
]

Step 3. The About Section

Output in a code block. Formatting rules:

• Write in full sentences. Do not force line breaks mid-sentence.
• One line break between sentences or short phrases for readability.
• Double line break between sections (hook, story, authority, CTA).
• LinkedIn handles text wrapping on mobile and desktop. Do not manually wrap at 50 or 60 characters.
• Short punchy sentences are good. Chopping sentences in half is not.

Structure: Hook > Struggle/Empathy > Method/Philosophy > Authority > CTA

Tone: Punchy, direct, human. Not corporate.

Formatting example only; replace with supplied facts, never invented biography:

[User’s real starting point, if supplied.]
[Their verified result, with the correct timeframe.]

[What they do and how that helps their audience.]
[One concrete example from their supplied experience.]

[Their current offer and confirmed next action.]

Step 4. The Experience Section

Rewrite the top 2 roles. Output in a code block. Same formatting approach as the About section: full sentences, no forced mid-sentence line breaks, LinkedIn handles wrapping.

Structure per role: Context > Challenge > Action > Result

Storytelling format, not bullet points. 8 to 15 sentences per role maximum.

Formatting example only; replace with supplied facts, never invented biography:

I walked into a team that had lost 3 managers in 2 years.
Morale was gone. Revenue was slipping.

I didn't start with strategy decks. I started with listening.

Within 6 months we rebuilt the culture.
Within 12 months revenue was up 40%.

That taught me everything about leading through chaos.

Example of incorrect formatting:

• Managed a team of 15 sales representatives
• Responsible for Q3 revenue targets
• Implemented new CRM system