cc-skill:gap-analysis-template

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

It diagnoses the hidden problems in a product or business that could kill it, ranks them by severity, and produces a prioritized roadmap to fix them. The output is a structured report with existential risks, secondary issues, and a remediation plan that can be handed to engineers.

who it is for

Founders, product leads, and investors who need to know what could go wrong before it does.

when it fires

When you ask about gap analysis, risk assessment, auditing a product or system, finding missing pieces, or what could cause failure.

say something like

"Run a gap analysis on our SaaS product before we raise Series A."
"Audit this system for existential risks in the next 90 days."
"What could kill this product? Find the gaps."

what you might get back

The output is a report titled 'Product Gap Analysis' dated today. It opens with a 3-sentence summary of the biggest risks. Then it lists 3 to 5 critical or high-severity risks in detail, each one explaining what it is, how bad it could get, why it exists, and what it costs to fix. Below that is a numbered roadmap table showing 10 to 20 specific actions, who owns each one, and how long it takes. For example: 'Risk 1: User data not encrypted at rest. Critical. Cost of remediation: 8 days. Action 1: Implement AES-256 encryption.'

how to know it worked

You'll know it worked because you have a specific list of ranked risks with severity levels, time-to-impact estimates, and a concrete roadmap you can hand to a team or engineer.

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

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/gap-analysis-template/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 conducting a gap analysis on an existing product, system, or business — identifying existential risks, severity-scored issues, and remediation roadmaps. Triggers on "gap analysis", "risk assessment", "what's missing", "audit this

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/gap-analysis-template/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 conducting a gap analysis on an existing product, system, or business — identifying existential risks, severity-scored issues, and remediation roadmaps. Triggers on \"gap analysis\", \"risk assessment\", \"what's missing\", \"audit this product\", \"audit this system\", \"find the gaps\", or \"what could kill this\". Modeled on the gap analyses Jay has run for SwarmTrade and LeadFlow."
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/gap-analysis-template/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.