← all tools

cc-skill:consultantvoice-pov-essay

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

This skill generates a 1500-2500 word opinion essay that takes a real stand on a healthcare IT problem, backs it with actual go-live experience, and ends with a constructive solution. It sounds like someone who has actually lived through the problem, not a vendor selling a product.

who it is for

Healthcare IT consultants, industry leaders, and thought leaders who want to publish credible, specific critiques that only someone with real project experience can write.

when it fires

When you ask for a POV essay, manifesto, industry critique, thought piece, or long-form opinion piece about healthcare IT, particularly around go-live experience or industry practices.

say something like
  • "Write a POV essay about how Epic certification gatekeeping is hurting the consultant market"
  • "I want a ConsultantVoice manifesto on why hospital RFP processes are theater"
  • "Create a long-form essay about the real problems with AI scribes in clinical workflows"
what you might get back
An essay titled 'The Cert Tax: Why Epic's Gatekeeping Is Killing Consultant Diversity' opens with a scene of a talented consultant being locked out of projects because she can't afford the $5K module fee. It then explains how certification requirements protect Epic's training revenue, shows who loses (smaller firms, diverse candidates, hospitals with thin budgets), and proposes a community-sponsored certification model. It closes by stating ConsultantVoice's bet on removing barriers to entry.
how to know it worked

You will know it worked because the essay opens with a specific, time-and-place scene from a real go-live, includes numbers and roles that feel earned, and lands on a mechanical change proposal, not just criticism.

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.

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/consultantvoice-pov-essay/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 long-form opinion essays, manifestos, industry critique pieces, or thought leadership content for ConsultantVoice. Triggers on "POV essay", "ConsultantVoice manifesto", "industry take", "thought piece", "long-form essay

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/consultantvoice-pov-essay/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 long-form opinion essays, manifestos, industry critique pieces, or thought leadership content for ConsultantVoice. Triggers on \"POV essay\", \"ConsultantVoice manifesto\", \"industry take\", \"thought piece\", \"long-form essay\", \"healthcare IT essay\", or \"opinion piece\". Produces 1500–2500 word essays that pick a fight, back it with go-live specifics, and land on a constructive claim."
}
how it gets called
{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/consultantvoice-pov-essay/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.