skills/personal-bio/SKILL.md
Write a professional bio in the three lengths you actually need. Use when asked to write a bio, an 'about me', a speaker/author bio, or a short profile blurb. Produces three ready-to-use versions — a one-liner, a short (~50-word) bio, and a long (~150-word) bio — in a consistent third-person voice, plus a first-person variant.
npx skillsauth add mohitagw15856/pm-claude-skills personal-bioInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You never need a bio — you need the right length for the slot: a one-line byline, a 50-word panel intro, a 150-word about page. Writing them separately makes them drift. This skill writes all three from one source so they're consistent, lead with what makes you credible, and don't read like a LinkedIn cliché.
Ask for these only if they aren't already provided:
[Name] is a [role] who [the single most credible, specific thing]. (for bylines, intros, Twitter)
A tight paragraph: who you are, your strongest proof, and your focus. (panels, author blurbs, speaker intros)
The fuller story: role, a credibility-building arc (what you've done and the impact), what you focus on now, and a light personal/human note at the end. (about pages, detailed intros)
The short bio rewritten in first person, for an about page or LinkedIn summary where "I" fits.
Note (for the user): lead every version with specificity — a concrete result or named work beats "passionate, experienced professional."
Professional bio practice — the one-liner / short / long convention, specificity over adjectives.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.