Skills Guide

Save LeetCode Progress to Obsidian

VerifiedSafe

Capture a summary of your LeetCode practice session directly into an Obsidian note. After solving a problem, this skill extracts your final code, initial bugs, key learnings, and Q&A highlights, then saves them to a structured markdown file and updates your index. Ideal for building a personal LeetCode knowledge base in Obsidian.

Download and use
Sby Skills Guide Bot
DocumentationIntermediate
6/2/2026
Claude Code
#leetcode#obsidian#note-taking#coding-practice#knowledge-management

Recommended for

Claude CodeAuto documentation

Automated summary

Saves a LeetCode session summary to Obsidian, including solution, bugs, and key learnings.

Strengths

  • Automates structured note-taking after each problem
  • Captures key details like bugs and nuances
  • Integrates with Obsidian via MCP for easy organization
  • Creates a navigable index of solved problems

Limitations

  • Requires Obsidian setup and MCP tool access
  • Depends on conversation context to extract relevant info
  • Only works within Claude Code sessions
When to use it

After completing a LeetCode problem in Claude Code to systematically document progress.

When not to use it

If you don't use Obsidian or prefer a different note format.

Security analysis

Safe
Quality score88/100

The skill only uses local Obsidian MCP tools to write markdown notes from conversation content. There are no network calls, shell commands, or risky operations. All file operations are constrained to creating/updating notes in an Obsidian vault.

No concerns found

How this analysis is made

Examples

Save current LeetCode session
Save my LeetCode session to Obsidian. We just solved 752-open-lock.
Add note after debugging
Create a LeetCode note for the problem we just worked on. Include the bugs I fixed.

name: add-lc description: Save LeetCode session summary to Obsidian. Use after completing a LeetCode practice session to capture your solution, bugs fixed, and key learnings.

Add LeetCode Progress Note

Save a summary of the current LeetCode practice session to Obsidian.

Instructions

  1. Extract from the conversation:

    • Problem name and number (ask if not clear)
    • Final working code
    • Initial bugs/issues that were identified and fixed
    • Key concepts discussed and clarified
    • Important nuances learned
    • Any notable Q&A exchanges

  2. Create the problem note using mcp__obsidian__obsidian_append_content:

    • Filepath: 3. Resources/LeetCode/{problem-number}-{problem-name-slug}.md
    • Example: 3. Resources/LeetCode/752-open-lock.md

  3. Note format:

# {Problem Number}. {Problem Name}

**Date:** {YYYY-MM-DD}
**Difficulty:** {Easy/Medium/Hard}
**Topics:** {BFS, DFS, DP, etc.}
**Link:** https://leetcode.com/problems/{slug}/

## Final Solution

\`\`\`python
{final working code}
\`\`\`

## Initial Issues

{List bugs/mistakes from first attempt}

## Key Learnings

{Concepts that were clarified during the session}

## Nuances to Remember

{Specific details, edge cases, or gotchas}

## Q&A Highlights

{Notable questions and insights from the discussion}

  1. Update the index using mcp__obsidian__obsidian_append_content:

    • Filepath: 3. Resources/LeetCode/index.md
    • Append: - [[{problem-number}-{problem-name-slug}]] - {one-line summary}

  2. Confirm to the user that the note was saved and provide the filepath.

Tools Required

  • mcp__obsidian__obsidian_append_content - to create/update notes
  • mcp__obsidian__obsidian_get_file_contents - to check if index exists

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 files

This 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.md

From the root of a test project, save the file as .skill-downloads/save-leetcode-progress-to-obsidian-mm5t8bqq/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/save-leetcode-progress-to-obsidian-mm5t8bqq' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/save-leetcode-progress-to-obsidian-mm5t8bqq/download' --output '.skill-downloads/save-leetcode-progress-to-obsidian-mm5t8bqq/SKILL.md.part' && mv '.skill-downloads/save-leetcode-progress-to-obsidian-mm5t8bqq/SKILL.md.part' '.skill-downloads/save-leetcode-progress-to-obsidian-mm5t8bqq/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/save-leetcode-progress-to-obsidian-mm5t8bqq/SKILL.md' && test -s '.skill-downloads/save-leetcode-progress-to-obsidian-mm5t8bqq/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/add-lc' && cp -R '.skill-downloads/save-leetcode-progress-to-obsidian-mm5t8bqq' '.claude/skills/add-lc'

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 installation
openskills install './.skill-downloads/save-leetcode-progress-to-obsidian-mm5t8bqq'

openskills read 'save-leetcode-progress-to-obsidian-mm5t8bqq'

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 sync

Manual 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/save-leetcode-progress-to-obsidian-mm5t8bqq/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.

Related skills

Supabase Docs Authoring

Documentation

Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.

Claude CodeintermediateSafe 108,544
Skills Guide Bot

Create Architecture Decision Record

Documentation

Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.

Claude CodeintermediateSafe 69,659
Skills Guide Bot

Plan update with deep research

Documentation

Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.

Claude CodeadvancedSafe 248,015
Skills Guide Bot