Let Claude Cook

Find hidden product opportunities in the APIs you already pay for.

You're paying for 10 APIs but only using 20% of their features. This Claude Code skill scans your entire codebase, reads the docs of every API you integrate with, and generates a ranked list of features you could build today — using capabilities you already have access to.

Think of it like handing Claude the keys to your fridge and letting it cook up a feast from ingredients you forgot you had.

What it does

1. Discovers every API your product calls (SDKs, REST calls, webhooks, env vars — all of it)
2. Reads their full docs and catalogs every endpoint you're not using
3. Brainstorms concrete features you could build with those unused capabilities
4. Scores and ranks each opportunity by your buyer personas
5. Outputs a beautiful HTML report that opens in your browser

The whole thing runs autonomously — you answer one question (buyer personas), then let Claude cook. Come back to a prioritized feature roadmap built from your existing API subscriptions.

Install

One-liner (recommended)

Run this from your project root:

mkdir -p .claude/skills && curl -fsSL \
  https://raw.githubusercontent.com/avinoamMO/let-claude-cook/main/.claude/skills/let-claude-cook.md \
  -o .claude/skills/let-claude-cook.md

Manual install

1. Download let-claude-cook.md from this repo
2. Place it in your project at .claude/skills/let-claude-cook.md
3. That's it — Claude Code picks it up automatically

Clone and copy

git clone https://github.com/avinoamMO/let-claude-cook.git /tmp/let-claude-cook
mkdir -p .claude/skills
cp /tmp/let-claude-cook/.claude/skills/let-claude-cook.md .claude/skills/
rm -rf /tmp/let-claude-cook

Note: The .claude/skills/ directory must be at your project root (next to your package.json, go.mod, requirements.txt, etc). Claude Code automatically registers any .md file in this directory as a slash command.

Usage

Open Claude Code in your project and run:

/let-claude-cook

It will ask you one question — whether you want to define your buyer personas or let it figure them out from your codebase. After that, it runs completely hands-free.

The output lands at tasks/api-opportunities.html and opens in your browser automatically.

Tip: Run it at the end of the day. Depending on how many APIs you use, it takes 10-30 minutes. Come back to a full feature roadmap in the morning.

What you get

A single self-contained HTML report with:

Each opportunity includes the specific API endpoint(s) it would use, per-persona scores (color-coded), and an effort estimate (S/M/L).

How it works

Your Codebase
     |
     v
[1. API Discovery] -----> loop through imports, env vars, HTTP calls,
     |                     SDKs, webhooks, configs until exhaustive
     v
[2. Doc Research]  -----> fetch full API docs for each service,
     |                     catalog ALL available endpoints
     v
[3. Brainstorm]    -----> match unused capabilities to concrete
     |                     product features (specific, not generic)
     v
[4. Score & Rank]  -----> rate each idea by buyer persona value
     |                     + estimate effort (S/M/L)
     v
[5. HTML Report]   -----> styled, color-coded, opens in browser

Why this works

Most products integrate APIs for one specific job — screenshots, payments, analytics — and never look at what else is on the menu. But API providers ship new endpoints constantly, and your existing plan often includes capabilities nobody in your market is using yet.

This skill automates the "what else can I cook with what's in the fridge?" question that product teams never have time to ask.

Works with any stack

The skill is language and framework agnostic. It searches for API integrations using multiple strategies (package managers, imports, HTTP calls, env vars, config files) so it works whether your project is:

• Node.js / TypeScript
• Python / Django / FastAPI
• Ruby / Rails
• Go
• Java / Kotlin
• or anything else with third-party API calls

Requirements

• Claude Code — CLI, desktop app, or IDE extension
• A codebase with at least a few third-party API integrations
• Web search/fetch capability enabled in Claude Code (for pulling API docs)

FAQ

Q: Does it send my code anywhere? A: No. The skill runs locally in Claude Code. It reads your files and uses web search to fetch public API documentation. Your code never leaves your machine (beyond what Claude Code normally does).

Q: What if I have 50 APIs? A: It'll take longer but it handles it. The discovery loop is designed to be exhaustive. Budget 30-45 minutes for large codebases.

Q: Can I customize the buyer personas? A: Yes — it asks you at the start. You can provide your own personas or let it infer them from your codebase (landing pages, pricing, docs, etc).

Q: What if an API's docs aren't publicly available? A: It'll note what it couldn't access and work with what it found. You can always re-run after adding notes about private APIs.

License

MIT

Built by @avinoamMO. Made with Claude Code.