Install the "leetcode-coach" agent skill from https://github.com/tinyfish-io/tinyfish-cookbook/tree/main/skills/leetcode-coach into .claude/skills/leetcode-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leetcode-coach", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add tinyfish-io/tinyfish-cookbook --skill leetcode-coach -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "leetcode-coach" agent skill from https://github.com/tinyfish-io/tinyfish-cookbook/tree/main/skills/leetcode-coach into .agents/skills/leetcode-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leetcode-coach", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add tinyfish-io/tinyfish-cookbook --skill leetcode-coach -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "leetcode-coach" agent skill from https://github.com/tinyfish-io/tinyfish-cookbook/tree/main/skills/leetcode-coach into .cursor/skills/leetcode-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leetcode-coach", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add tinyfish-io/tinyfish-cookbook --skill leetcode-coach -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "leetcode-coach" agent skill from https://github.com/tinyfish-io/tinyfish-cookbook/tree/main/skills/leetcode-coach into .gemini/skills/leetcode-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leetcode-coach", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add tinyfish-io/tinyfish-cookbook --skill leetcode-coach -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "leetcode-coach" agent skill from https://github.com/tinyfish-io/tinyfish-cookbook/tree/main/skills/leetcode-coach into .github/skills/leetcode-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leetcode-coach", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add tinyfish-io/tinyfish-cookbook --skill leetcode-coach -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "leetcode-coach" agent skill from https://github.com/tinyfish-io/tinyfish-cookbook/tree/main/skills/leetcode-coach into .opencode/skills/leetcode-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leetcode-coach", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
leetcode-coach
GitHub stars
2.2k
Token cost
~2.5k tokens
SKILL.md length
582 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT
At a glance
Find and set up coding practice problems tailored to your weak areas, then create local files so you can solve them right away.
Works in 6 steps: Gather inputs → Find matching problems → Present problem options → …
A user wants to practice coding
SKILL.md covers Pre-flight Check (REQUIRED), Step 1 — Gather inputs, Step 2 — Find matching problems and Step 3 — Present problem options, plus 5 more sections
Calls npm; reaches leetcode.com and codeforces.com
What it does
Leetcode Coach is an agent skill from tinyfish-io/tinyfish-cookbook. Find and set up coding practice problems tailored to your weak areas, then create local files so you can solve them right away. Use this skill when a user wants to practice coding, asks for a LeetCode problem, says "give me a coding challenge", "I want to practice DSA", "help me prep for coding interviews", "find me a problem to solve", "I'm weak at dynamic programming", "quiz me on algorithms", or any request to practice coding with a specific language or topic focus.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Education. The repository describes itself as: A collection of sample apps and recipes built with the TinyFish web agent. Open-source examples for you to learn & build! The licence is MIT.
When your agent uses it
A user wants to practice coding
Asks for a LeetCode problem
Says give me a coding challenge
I want to practice DSA
Example prompts
“give me a coding challenge”
“I want to practice DSA”
“help me prep for coding interviews”
“/leetcode-coach”
Requirements
Python 3
Node.js
Workflow steps
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 292ee62. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
leetcode.com
codeforces.com
hackerrank.com
Also links to:
agent.tinyfish.ai
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Leetcode Coach loads about 2.5k tokens when it runs. Until then it costs about 122 tokens; SKILL.md has 582 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~122
When it runs· the whole SKILL.md, loaded when a task matches
~2.5k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/leetcode-coach/SKILL.md (or your agent's skills folder).
name
leetcode-coach
description
Find and set up coding practice problems tailored to your weak areas, then create local files so you can solve them right away. Use this skill when a user wants to practice coding, asks for a LeetCode problem, says "give me a coding challenge", "I want to practice DSA", "help me prep for coding interviews", "find me a problem to solve", "I'm weak at dynamic programming", "quiz me on algorithms", or any request to practice coding with a specific language or topic focus.
LeetCode Coach
Find coding problems matched to your weak areas from LeetCode, HackerRank, and Codeforces — then set up local files so you can start solving immediately.
Pre-flight Check (REQUIRED)
Before making any TinyFish call, always run BOTH checks:
1. CLI installed?
bash
which tinyfish && tinyfish --version || echo "TINYFISH_CLI_NOT_INSTALLED"
If not installed, stop and tell the user:
Install the TinyFish CLI: npm install -g @tiny-fish/cli
Preferred language — e.g. Python, JavaScript, Java, C++, Go, Rust
Optional (but improves results):
Weak areas / topics to focus on — e.g. "dynamic programming", "graphs", "sliding window", "binary search", "recursion", "trees"
Difficulty — Easy / Medium / Hard (default: Medium)
If the user isn't sure of their weak areas, ask:
"What topics do you find yourself getting stuck on, or want to get better at?"
If they still aren't sure, default to: Arrays, Strings, and Hash Maps (the most commonly tested fundamentals).
Step 2 — Find matching problems
Fire parallel TinyFish agents across LeetCode, HackerRank, and Codeforces to find real problems matching the topic and difficulty.
bash
# Agent 1 — LeetCode problem search
tinyfish agent run \
--url "https://leetcode.com/problemset/?difficulty={DIFFICULTY}&topicSlugs={TOPIC_SLUG}" \
"You are on the LeetCode problem set page filtered by difficulty and topic.
Find 3 problems that match the topic: {TOPIC}.
For each problem extract:
- title
- difficulty (Easy/Medium/Hard)
- acceptance rate
- topic tags
- direct URL to the problem (e.g. https://leetcode.com/problems/two-sum/)
STRICT RULES:
- Do NOT click any problem to open it
- Read only the problem listing visible on this page
- Return exactly 3 problems, no more
- Skip premium-only problems (marked with a lock icon)
Return JSON array: [{title, difficulty, acceptance_rate, tags, url}]" \
--sync > /tmp/lc_leetcode.json &
# Agent 2 — HackerRank problem search
tinyfish agent run \
--url "https://www.hackerrank.com/domains/algorithms?filters%5Bsubdomains%5D%5B%5D={TOPIC_SLUG}" \
"You are on HackerRank's algorithms problem listing filtered by topic.
Find 2 problems that match the topic: {TOPIC} at {DIFFICULTY} level.
For each problem extract:
- title
- difficulty
- score/points
- topic tags
- direct URL to the problem
STRICT RULES:
- Do NOT click any problem
- Read only the visible listing
- Return up to 2 problems
- Skip problems requiring premium or contests
Return JSON array: [{title, difficulty, score, tags, url}]" \
--sync > /tmp/lc_hackerrank.json &
# Agent 3 — Codeforces problem search
tinyfish agent run \
--url "https://codeforces.com/problemset?tags={TOPIC_SLUG}" \
"You are on Codeforces problem set filtered by tag.
Find 2 problems matching the topic: {TOPIC} at approximately {DIFFICULTY} level
(Easy ≈ rating 800-1200, Medium ≈ 1300-1800, Hard ≈ 1900+).
For each problem extract:
- problem ID (e.g. 1A, 158B)
- title
- rating
- tags
- direct URL (e.g. https://codeforces.com/problemset/problem/1/A)
STRICT RULES:
- Do NOT click any problem
- Read only the visible listing
- Return up to 2 problems
Return JSON array: [{id, title, rating, tags, url}]" \
--sync > /tmp/lc_codeforces.json &
wait
echo "=== LEETCODE ===" && cat /tmp/lc_leetcode.json
echo "=== HACKERRANK ===" && cat /tmp/lc_hackerrank.json
echo "=== CODEFORCES ===" && cat /tmp/lc_codeforces.json
Before running, replace:
{DIFFICULTY} — Easy / Medium / Hard
{TOPIC} — human-readable topic e.g. dynamic programming
{TOPIC_SLUG} — URL-friendly e.g. dynamic-programming
Step 3 — Present problem options
From the results, pick the 3 best problems across all sources. Prefer:
LeetCode problems (widest community support, best editorial availability)
Problems with clear descriptions visible from the listing
Problems with acceptance rates between 30-60% for Medium difficulty
Present them like this:
Here are 3 problems matched to your focus on **{TOPIC}** in **{LANGUAGE}**:
**Option 1 — {Title}** ({difficulty}) · {source}
Tags: {tags}
Acceptance: {rate}
🔗 {url}
**Option 2 — {Title}** ({difficulty}) · {source}
Tags: {tags}
🔗 {url}
**Option 3 — {Title}** ({difficulty}) · {source}
Tags: {tags}
🔗 {url}
Which one do you want to tackle? (1, 2, or 3)
Wait for the user to choose a problem before proceeding.
Step 3b — Ask how they want to solve it
Once the user picks a problem, ask:
How do you want to solve it?
1. **On the website** — I'll give you the direct link and you solve it in the browser
2. **Locally** — I'll fetch the full problem and set up files on your machine so you can code in your editor
(1 or 2)
If they choose option 1 (website):
Give them the direct link to the problem and wish them luck:
Here you go: {problem_url}
Good luck! Come back and paste your solution when you're done — I'll review it.
Stop here. Do not create any files.
If they choose option 2 (locally):
Continue to Step 4.
Step 4 — Fetch the full problem
Once the user picks, fetch the full problem description using TinyFish.
bash
tinyfish agent run \
--url "{CHOSEN_PROBLEM_URL}" \
"You are on a coding problem page. Extract the complete problem details.
Extract:
- title
- difficulty
- full problem description (exactly as written — do not paraphrase)
- constraints (exact list)
- all example inputs and outputs with explanations
- topic tags
- any follow-up questions mentioned
STRICT RULES:
- Do NOT click any links
- Extract the complete description verbatim — do not shorten it
- If examples have visual diagrams described in text, include them
Return JSON: {title, difficulty, description, constraints: [], examples: [{input, output, explanation}], tags: [], followup}" \
--sync
Show full SKILL.md (236 more words)Show less
Step 5 — Create local files
Once you have the full problem, create these three files in the current working directory:
problem.md
markdown
# {Problem Title}
**Source:** {url}
**Difficulty:** {difficulty}
**Tags:** {tags}
**Language:** {language}
---
## Problem
{full problem description}
## Constraints
{constraints as bullet list}
## Examples
### Example 1
**Input:** {input}
**Output:** {output}
**Explanation:** {explanation}
### Example 2
...
---
## Notes
<!-- Add your approach notes here before coding -->
solution.{ext}
Create a starter file with the correct extension for the chosen language and a function signature scaffold. Use the appropriate extension:
Language
Extension
Starter
Python
.py
def solution(): with docstring
JavaScript
.js
function solution() {} with JSDoc
TypeScript
.ts
typed function signature
Java
.java
class + method scaffold
C++
.cpp
#include + function
Go
.go
package + func
Rust
.rs
fn solution()
Include a comment at the top:
// Problem: {title}
// Source: {url}
// Difficulty: {difficulty}
// Your approach: (fill this in before coding)
Infer the function signature from the problem description if possible (e.g. if the problem says "given an array of integers, return..."). If unclear, use a generic starter.
test_cases.md
markdown
# Test Cases — {Problem Title}
## From the problem
| # | Input | Expected Output |
|---|-------|----------------|
| 1 | {input} | {output} |
| 2 | {input} | {output} |
## Edge cases to consider
<!-- Think about: empty input, single element, negative numbers, duplicates, max constraints -->
- [ ] Empty input
- [ ] Single element
- [ ] Already sorted / already valid
- [ ] Maximum constraint size
Step 6 — Brief the user
Once the files are created, tell the user:
Files created:
- problem.md ← full problem description
- solution.{ext} ← starter template in {language}
- test_cases.md ← sample test cases + edge case checklist
Take your time and solve it. When you're done, paste your solution here and I'll review it — checking for correctness, edge cases, time complexity, and style.
Good luck!
Edge Cases
LeetCode returns no results for topic — fall back to searching https://leetcode.com/problemset/?search={TOPIC} without the filter
Problem URL is premium-only — skip it and pick the next best option from the results
User doesn't know their weak areas — default to Arrays + Hash Maps (Medium), which covers the widest range of interview fundamentals
User wants a specific problem by name — skip Steps 2-3, go straight to fetching and creating files for that problem
Codeforces returns nothing — skip it silently, present options from LeetCode and HackerRank only
User is a complete beginner — suggest Easy difficulty and start with Two Sum (LeetCode #1) as a warm-up before moving to their topic of interest
Leetcode Coach next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Leetcode Coach compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Leetcode Coach this skilltinyfish-io/tinyfish-cookbook
Teaches the agent to set up and run DeepTutor from the command line: chat and capabilities, knowledge bases, partners, memory, sessions, notebooks and the server or Web app.
Answers education and career questions in the voice of Zhang Xuefeng, looking up current employment and admissions data before giving a direct verdict.
Comprehensive framework for deep analysis of articles, papers, and long-form content using 10+ thinking models (SCQA, 5W2H, critical thinking, inversion, mental models, first principles, systems…
Turns a codebase into an interactive single-page HTML course for non-technical learners, with scroll modules, animated diagrams, quizzes and plain-English code translations.
Default browser automation agent — click, fill forms, navigate, log in, and extract structured data from any website using a natural-language goal, or run the same task across multiple sites in…
Reverse-engineer what a company is building by scraping their job postings, careers page, LinkedIn Jobs, and engineering blog using TinyFish web agents.
Check every dependency in a package.json against live CVE databases and security advisories in real time — specifically targeting vulnerabilities disclosed in the last 48 hours, the window that…
Find and set up coding practice problems tailored to your weak areas, then create local files so you can solve them right away. Leetcode Coach is an agent skill from tinyfish-io/tinyfish-cookbook. Find and set up coding practice problems tailored to your weak areas, then create local files so you can solve them right away.
When should I use Leetcode Coach?
Leetcode Coach fits situations like: A user wants to practice coding; asks for a LeetCode problem; says give me a coding challenge; I want to practice DSA.
How do I install Leetcode Coach in Claude Code?
Run `npx skills add tinyfish-io/tinyfish-cookbook --skill leetcode-coach -a claude-code`. Or copy the skill folder (skills/leetcode-coach in tinyfish-io/tinyfish-cookbook) into .claude/skills/leetcode-coach in your project. Claude Code loads it when a task matches its description.
How do I install Leetcode Coach in Codex?
Run `npx skills add tinyfish-io/tinyfish-cookbook --skill leetcode-coach -a codex`. Or copy the skill folder (skills/leetcode-coach in tinyfish-io/tinyfish-cookbook) into .agents/skills/leetcode-coach in your project. Codex loads it when a task matches its description.
Can I use Leetcode Coach in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tinyfish-io/tinyfish-cookbook --skill leetcode-coach -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/leetcode-coach, .gemini/skills/leetcode-coach, .github/skills/leetcode-coach and .opencode/skills/leetcode-coach in your project.
What does Leetcode Coach need to run?
Going by SKILL.md and its folder, Leetcode Coach needs the command-line tools its instructions call (npm). Our summary lists: Python 3; Node.js.
Does Leetcode Coach access the network?
SKILL.md names 4 domains. In commands or code: leetcode.com, codeforces.com and hackerrank.com; the agent is likely to contact these when it follows the instructions. As links in the text: agent.tinyfish.ai. This is read from the text; nothing was executed.
Is Leetcode Coach safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Leetcode Coach use?
Leetcode Coach is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Leetcode Coach use?
About 2.5k tokens (SKILL.md is roughly 9.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Leetcode Coach?
Skills that share tags, products or a category with Leetcode Coach: DeepTutor CLI (HKUDS/DeepTutor, 41k stars), Zhang Xuefeng Perspective (alchaincyf/zhangxuefeng-skill, 10k stars), Deep Reading Analyst (ginobefun/deep-reading-analyst-skill, 353 stars) and AI Engineering Placement Quiz (rohitg00/ai-engineering-from-scratch, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Leetcode Coach?
tinyfish-io (a GitHub organization) maintains it in tinyfish-io/tinyfish-cookbook, which has 2,221 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 1, 2026.
Source: tinyfish-io/tinyfish-cookbook on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.