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.

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

Recommended for

Our review

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

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
Related skills