Leetcode Py
wislertt/leetcode-py
Generates Python LeetCode practice environments and manages a 307-problem catalog with the lcpy CLI.
Search recent LeetCode Discuss posts (leetcode.com/discuss/) by keyword — a company, a level, a round — read the ones that describe real interview questions, map each question to an LC number, check…
Install Lc Discussion
$ npx skills add yennanliu/CS_basics --skill lc-discussion -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yennanliu/CS_basics lc-discussion --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/yennanliu/CS_basics.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/lc-discussion .claude/skills/lc-discussion && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "lc-discussion" agent skill from https://github.com/yennanliu/CS_basics/tree/master/.claude/skills/lc-discussion into .claude/skills/lc-discussion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lc-discussion", 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.
$skill-installer install https://github.com/yennanliu/CS_basics/tree/master/.claude/skills/lc-discussionType 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.
$ npx skills add yennanliu/CS_basics --skill lc-discussion -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yennanliu/CS_basics lc-discussion --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yennanliu/CS_basics.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/lc-discussion .agents/skills/lc-discussion && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lc-discussion" agent skill from https://github.com/yennanliu/CS_basics/tree/master/.claude/skills/lc-discussion into .agents/skills/lc-discussion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lc-discussion", 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.
$ npx skills add yennanliu/CS_basics --skill lc-discussion -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yennanliu/CS_basics lc-discussion --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yennanliu/CS_basics.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/lc-discussion .cursor/skills/lc-discussion && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lc-discussion" agent skill from https://github.com/yennanliu/CS_basics/tree/master/.claude/skills/lc-discussion into .cursor/skills/lc-discussion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lc-discussion", 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.
$ gemini skills install https://github.com/yennanliu/CS_basics.git --path .claude/skills/lc-discussion--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add yennanliu/CS_basics --skill lc-discussion -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yennanliu/CS_basics lc-discussion --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yennanliu/CS_basics.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/lc-discussion .gemini/skills/lc-discussion && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lc-discussion" agent skill from https://github.com/yennanliu/CS_basics/tree/master/.claude/skills/lc-discussion into .gemini/skills/lc-discussion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lc-discussion", 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.
$ gh skill install yennanliu/CS_basics lc-discussionInstalls 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).
$ npx skills add yennanliu/CS_basics --skill lc-discussion -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yennanliu/CS_basics.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/lc-discussion .github/skills/lc-discussion && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lc-discussion" agent skill from https://github.com/yennanliu/CS_basics/tree/master/.claude/skills/lc-discussion into .github/skills/lc-discussion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lc-discussion", 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.
$ npx skills add yennanliu/CS_basics --skill lc-discussion -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yennanliu/CS_basics lc-discussion --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yennanliu/CS_basics.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/lc-discussion .opencode/skills/lc-discussion && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lc-discussion" agent skill from https://github.com/yennanliu/CS_basics/tree/master/.claude/skills/lc-discussion into .opencode/skills/lc-discussion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lc-discussion", 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
lc-discussion- GitHub stars
- 141
- Token cost
- ~2k tokens
- SKILL.md length
- 1,027 words
- Files
- 1
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- None found
At a glance
Search recent LeetCode Discuss posts (leetcode.com/discuss/) by keyword — a company, a level, a round — read the ones that describe real interview questions, map each question to an LC number, check…
- Works in 7 steps: Search → Shortlist → Read → …
- Asked what a company has been asking lately
- SKILL.md covers Why this exists, Prime directives, The steps and Do not, plus 1 more section
- Calls python3
What it does
Lc Discussion is an agent skill from yennanliu/CS_basics. Search recent LeetCode Discuss posts (leetcode.com/discuss/) by keyword — a company, a level, a round — read the ones that describe real interview questions, map each question to an LC number, check every one against README and the practice log, and write the result as a 繁體中文 summary doc under doc/ws/. Use when asked what a company has been asking lately, to scan LC discuss for interview experiences, to turn recent posts into a drill list, or to summarise discussion threads into a doc. Triggers - "/lc-discussion…
Its SKILL.md is about 2k 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 Development, covering Interview preparation and Technical documentation. The repository describes itself as: My CS learning : algorithm, data structure, and system design | SE.
When your agent uses it
- Asked what a company has been asking lately
- Scan LC discuss for interview experiences
- Turn recent posts into a drill list
- Summarise discussion threads into a doc
Example prompts
- “/lc-discussion google”
- “/lc-discussion meta e4 --days 30”
- “scan LC discuss for recent Google L3 questions”
- “/lc-discussion”
Requirements
- Python 3
- Pre-approved tools (allowed-tools): Read, Write, Glob, Grep, Bash
Workflow steps
7 steps, taken from the step headings in SKILL.md.
- Search
- Shortlist
- Read
- Map to LC numbers
- Cross-reference
- Write the doc
- Report
What it can do on your machine
Read from SKILL.md and the folder at commit b6cade9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteGlobGrepBash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Lc Discussion loads about 2k tokens when it runs. Until then it costs about 178 tokens; SKILL.md has 1,027 words of instructions outside code blocks.
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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Write, Glob, Grep, Bash
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.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,027 words (~1,969 tokens).
“Turn the last few weeks of interview write-ups on LeetCode Discuss into one doc in 繁體中文: the posts worth reading, the questions that came up more than once, and which of those problems this repo has never practised.”
- name
- lc-discussion
- allowed-tools
- Read, Write, Glob, Grep, Bash
Files
Just SKILL.md in .claude/skills/lc-discussion of yennanliu/CS_basics.
Open the folder on GitHubat commit b6cade9
Compare with similar skills
Lc Discussion 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lc Discussion this skillyennanliu/CS_basics | 141 | — | ~2k | Automated safety check: Notes | None | |
| Leetcode Pywislertt/leetcode-py | 142 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Handoverk1ein-chen/Harness-Starter | 119 | — | ~752 | Automated safety check: Pass | MIT | |
| Diagram Designcathrynlavery/diagram-design | 49k | 1 repos | ~7.6k | Automated safety check: Pass | MIT | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Doc SyncJetBrains/ideavim | 10k | 2 repos | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Handover
k1ein-chen/Harness-Starter
将当前会话中的技术决策、运维流程或阶段性研发进展，归档为标准工程文档（ADR / SOP / Handover），并自动更新模块内的 README 归档索引。
Diagram Design
cathrynlavery/diagram-design
Creates branded diagrams, from architecture, flowchart and sequence to charts and maps, as self-contained HTML with inline SVG, with import from draw.io, Mermaid and Excalidraw.
Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
- Official
Doc Sync
JetBrains/ideavim
Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.
Mailspring App Screenshots
Foundry376/Mailspring
Captures screenshots of the running Mailspring dev app for docs, PRs or visual checks by launching it with a debugging port, driving the UI and clipping to an element.
More from yennanliu/CS_basics
All 16 skills in this repoLc Coach
yennanliu/CS_basics
FAANG coding-interview coach. An agent skill from yennanliu/CS_basics.
Code Refactor Master
yennanliu/CS_basics
Code refactoring expert for improving code quality, readability, maintainability, and performance.
L3 Core
yennanliu/CS_basics
Report where the L3 core set stands and pick the next problems to drill from it.
Lc Again
yennanliu/CS_basics
Move a problem's README status cell after a re-solve — promote AGAIN to OK when it was genuinely re-derived unaided, add a review pass when it was not, or demote OK back to AGAIN when a solid…
Lc Algo Demo
yennanliu/CS_basics
Add or edit an algorithm visualizer under algodemo/ against the shared contract the other 36 pages already obey — colours read from the VIZ palette and never hardcoded, no re-implementation of the…
Lc Cheatsheet
yennanliu/CS_basics
File a LeetCode problem into the cheatsheets under doc/cheatsheet/ the way the existing sections are written — find the sheet whose Scope line owns the topic, file it under the pattern it belongs to…
Related
Categories
Questions about Lc Discussion
What does Lc Discussion do?
Search recent LeetCode Discuss posts (leetcode.com/discuss/) by keyword — a company, a level, a round — read the ones that describe real interview questions, map each question to an LC number, check…. Lc Discussion is an agent skill from yennanliu/CS_basics.com/discuss/) by keyword — a company, a level, a round — read the ones that describe real interview questions, map each question to an LC number, check every one against README and the practice log, and write the result as a 繁體中文 summary doc under doc/ws/.
When should I use Lc Discussion?
Lc Discussion fits situations like: asked what a company has been asking lately; scan LC discuss for interview experiences; turn recent posts into a drill list; summarise discussion threads into a doc.
How do I install Lc Discussion in Claude Code?
Run `npx skills add yennanliu/CS_basics --skill lc-discussion -a claude-code`. Or copy the skill folder (.claude/skills/lc-discussion in yennanliu/CS_basics) into .claude/skills/lc-discussion in your project. Claude Code loads it when a task matches its description.
How do I install Lc Discussion in Codex?
Run `npx skills add yennanliu/CS_basics --skill lc-discussion -a codex`. Or copy the skill folder (.claude/skills/lc-discussion in yennanliu/CS_basics) into .agents/skills/lc-discussion in your project. Codex loads it when a task matches its description.
Can I use Lc Discussion 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 yennanliu/CS_basics --skill lc-discussion -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lc-discussion, .gemini/skills/lc-discussion, .github/skills/lc-discussion and .opencode/skills/lc-discussion in your project.
What does Lc Discussion need to run?
Going by SKILL.md and its folder, Lc Discussion needs the command-line tools its instructions call (python3). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Glob, Grep, Bash.
Does Lc Discussion access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Lc Discussion safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Lc Discussion use?
No licence was found for Lc Discussion or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Lc Discussion use?
About 2k tokens (SKILL.md is roughly 7.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 Lc Discussion?
Skills that share tags, products or a category with Lc Discussion: Leetcode Py (wislertt/leetcode-py, 142 stars), Handover (k1ein-chen/Harness-Starter, 119 stars), Diagram Design (cathrynlavery/diagram-design, 49k stars) and Simple English (moeru-ai/airi, 50k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lc Discussion?
yennanliu (a GitHub user) maintains it in yennanliu/CS_basics, which has 141 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 11, 2026.
Source: yennanliu/CS_basics on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.