Automated summary
Fetches a LeetCode problem statement with the leetcode CLI and scaffolds a Rust solution file inside the problems/ directory.
Strengths
- A single command displays the problem and creates the Rust starter file.
- Enforces a consistent problems/ layout and `impl Solution` skeleton across problems.
- Notes that `struct Solution;` must be omitted because LeetCode defines it and build.rs provides it for rust-analyzer.
- Documents the test and submit commands (`leetcode test` / `leetcode submit`).
Limitations
- Requires the leetcode-cli tool to be installed and authenticated.
- Rust only, and it assumes the CLI's `<id>.<name>.rs` filename plus a working directory at the project root.
- Errors are suppressed with `2>/dev/null`, making failures harder to diagnose.
Use it when starting a new LeetCode problem in Rust inside a local practice repository.
Avoid it for solutions in another language, or when the leetcode CLI is not installed and configured.
Security analysis
SafeThe skill runs the 'leetcode' CLI to show problem details and generate a Rust template, then moves the file into a local directory. No destructive, exfiltrating, or obfuscated actions are present; the commands are straightforward and limited to local project file management.
No concerns found
How this analysis is madeExamples
/lc-show 1/lc-show 146Show LeetCode problem 20 with /lc-show, generate the Rust template in problems/, then run leetcode test on it.name: lc-show description: Show LeetCode problem details and generate Rust template (project)
LeetCode Show
Show problem details and generate Rust template in problems/ directory.
Usage
/lc-show <problem_id> - Show problem and generate Rust code template
Instructions
- Run
leetcode show <problem_id> 2>/dev/nullto display the problem description - Show the problem details to the user
- Run
leetcode show <problem_id> -g -l rust 2>/dev/nullto generate the Rust template - Move the generated file to
problems/directory:mv <problem_id>.<problem-name>.rs problems/ - Tell the user the file is ready at
problems/<problem_id>.<problem-name>.rs
File Format
use std::collections::HashMap; // if needed
impl Solution {
pub fn function_name(...) -> ... {
// implementation
}
}
Note: struct Solution; は含めない(LeetCode側で定義されるため)。rust-analyzer用には build.rs が lib.rs 経由で提供する。
Commands
- Test:
leetcode test problems/<file>.rs - Submit:
leetcode submit problems/<file>.rs
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/leetcode-rust-template-generator-mmlj2oz5/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/leetcode-rust-template-generator-mmlj2oz5' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/leetcode-rust-template-generator-mmlj2oz5/download' --output '.skill-downloads/leetcode-rust-template-generator-mmlj2oz5/SKILL.md.part' && mv '.skill-downloads/leetcode-rust-template-generator-mmlj2oz5/SKILL.md.part' '.skill-downloads/leetcode-rust-template-generator-mmlj2oz5/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/leetcode-rust-template-generator-mmlj2oz5/SKILL.md' && test -s '.skill-downloads/leetcode-rust-template-generator-mmlj2oz5/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/lc-show' && cp -R '.skill-downloads/leetcode-rust-template-generator-mmlj2oz5' '.claude/skills/lc-show'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/leetcode-rust-template-generator-mmlj2oz5'openskills read 'leetcode-rust-template-generator-mmlj2oz5'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/leetcode-rust-template-generator-mmlj2oz5/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.