← all tools

cc-skill:linkedin-long-form

Claude Code skill · anthropic · active

0
last 30 days
0 calls
0 of 30 days active
explain like I am new to this
what it does

Creates a LinkedIn post that tells a specific professional story and makes a clear point. It uses a proven formula: hook readers with the first two lines, set the scene, explain what surprised you, share the lesson, and end with a question or invitation.

who it is for

Consultants marketing their healthcare IT expertise, or job seekers in Salesforce and healthcare IT roles who want to get noticed by recruiters and hiring managers.

when it fires

When you ask to write a LinkedIn post, share a LinkedIn story, create recruiter-targeted content, or post something on LinkedIn for ConsultantVoice or your job search.

say something like
  • "Write a LinkedIn post about a go-live problem I ran into last month"
  • "Create a LinkedIn post for job search that shows my Salesforce admin skills"
  • "Help me post this on LinkedIn for ConsultantVoice"
what you might get back
Day 3 of go-live. The L&D module won't pull medication reconciliation forward. The build team says the validation passed. The clinical team says they're using paper. The command center says it's working as designed. Working as designed is the most expensive phrase in healthcare IT. Real go-live competency isn't about the build. It's about reading the room when the build hits the floor. #HealthcareIT #EpicEHR
how to know it worked

The post stays between 180 and 250 words, the first two lines hook you with a specific scene or claim, there are no em-dashes or hashtag walls, and you can imagine a hospital CIO or recruiter wanting to click 'see more' after the first paragraph.

is this skill working for me
never used
cloud runs
0
0 deployments
local fires
0
Claude Code (optional)
posts published
0
from drafts
attributed
$0.00
signups + revenue
Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/linkedin-long-form/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when generating LinkedIn posts (long-form text, carousel captions, recruiter-targeted content) for ConsultantVoice marketing or Jay's job search. Triggers on "LinkedIn post", "LinkedIn long-form", "post this on LinkedIn", "LinkedIn for

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/linkedin-long-form/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity
never used
2026-04-03today
cost model
unitincluded
capabilities
{
  "source": "global",
  "description": "Use this skill when generating LinkedIn posts (long-form text, carousel captions, recruiter-targeted content) for ConsultantVoice marketing or Jay's job search. Triggers on \"LinkedIn post\", \"LinkedIn long-form\", \"post this on LinkedIn\", \"LinkedIn for job search\", \"ConsultantVoice LinkedIn\", or \"recruiter post\"."
}
how it gets called
{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/linkedin-long-form/SKILL.md"
}
This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.