songyunseop/save
skills/save/SKILL.md
Save learning content as a TIL file and batch-update Daily notes, MOC, and backlog. Use when the user says 'save this', 'write up what I learned', 'document this as a TIL', or wants to persist a learning conversation as a note.
$ install --global
skillsauthnpx skillsauth add songyunseop/oh-my-til saveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 14, 2026, 2:16 AM29.6s4 files scanned
SKILL.md
- name:
- save
- description:
- Save learning content as a TIL file and batch-update Daily notes, MOC, and backlog. Use when the user says 'save this', 'write up what I learned', 'document this as a TIL', or wants to persist a learning conversation as a note.
- argument-hint:
- [topic] [category]
- plugin-version:
- __PLUGIN_VERSION__
Save Skill
Learning conversation → Save TIL file → Update Daily/MOC/backlog → Review document → Commit.
MCP Tools
til_get_context: Find related TILs and backlog itemstil_list: Check for duplicate existing TILstil_save_note: Save TIL note (server guarantees frontmatter/path rules, auto_check_backlog auto-checks backlog)
Step 1: Check Context
- Identify topic and category. Ask the user if unclear.
- Use
Readto check iftil/{category}/{slug}.mdexists.
Step 2: Identify Link Candidates
- Use
til_get_contextor MOC/backlog to find existing TILs and backlog items - Existing TIL/backlog items → use markdown links in the body
- Concepts that don't exist → confirm with user, then add only to related notes
Step 3: Save TIL File
Path: ./til/{category}/{topic-slug}.md (slug: lowercase English with hyphens)
Save new file: Save using the til_save_note MCP tool. The server guarantees frontmatter (title, date, category, tags, aliases) and path rules.
til_save_note(category, slug, title, content, tags, date, fmCategory, aliases, auto_check_backlog: true)
date: Get local time viadate +%Y-%m-%dT%H:%M:%Scommand and pass ittags: Must include "til"aliases: ["Korean title", "English title"]content: Body markdown excluding frontmatter
When a file with the same slug exists (detected by Read in Step 1):
- Auto-merge only when continuing a
/tilfollow-up session (preserve existing content + reinforce, addupdated) - Otherwise: ask user to confirm merge or overwrite
- For merge: use Read→Edit directly on existing content instead of
til_save_note
TIL Body Template
Read references/templates.md for the exact TIL body, Daily note, and MOC templates.
- Links:
[display name](til/{category}/{slug}.md)— no[[wiki links]]
Step 4: Update Related Files
Update the following 3 files directly in sequence (no subagents — parallel edits can race and corrupt shared files like MOC):
- Daily note (
./Daily/YYYY-MM-DD.md): Add TIL link by category (create if not exists) - TIL MOC (
./til/TIL MOC.md): Add item to category section (create if not exists) - Backlog: Already handled by
til_save_note'sauto_check_backlog: true(no separate call needed)
Daily/MOC: Read → find position → Edit. Create file if not exists.
Step 5: Document Review
Display full saved TIL content → use AskUserQuestion to confirm ("Looks good" / "Needs revision").
Step 6: Register for Review
Ask via AskUserQuestion: "Would you like to add this TIL to spaced repetition review?"
If user agrees, call til_review_update (action: "review", grade: 4) to create SRS metadata.
Step 7: git commit
📝 til: {English title}({Korean title}) - {category} (no push)
Rules
- frontmatter required: date, category, tags, aliases (fill in any missing fields before saving)
- tags must include "til" (used to filter TILs on the static site)
- No
[[wiki links]]— use[display name](path)format only (links must work in static sites and non-Obsidian editors) - Always update Daily/MOC/backlog after saving the TIL
- Use callouts:
> [!tldr],> [!example],> [!warning],> [!tip] - Visualize complex concepts with Mermaid diagrams (max 1 per TIL)
- Use placeholder values for sensitive information (avoid leaking real credentials)
Related Skills
songyunseop/til
research
VerifiedTrustedCommunity
Today I Learned — research a topic, learn interactively, then save as TIL markdown. Use when the user wants to learn about a topic, says 'teach me', 'what is X', 'deep dive into X', or asks to study something and save it as a TIL note.
4SKILL.mdUpdated Apr 14, 2026
songyunseop/til-review
testing
VerifiedTrustedCommunity
SRS-based TIL review session (spaced repetition). Use when the user says 'quiz me', 'review what I learned', 'flashcard session', 'test my knowledge', or wants to do spaced repetition review of their TIL notes.
4SKILL.mdUpdated Apr 14, 2026
songyunseop/setup-obsidian
tools
VerifiedTrustedCommunity
Install or update the Oh My TIL plugin in an Obsidian vault
4SKILL.mdUpdated Apr 14, 2026
songyunseop/research
research
VerifiedTrustedCommunity
Research a topic to identify key concepts and terms, then organize as a learning backlog. Use when the user wants a learning roadmap, study plan, curriculum, or asks 'what should I learn about X' — focuses on planning what to learn, not learning itself.
4SKILL.mdUpdated Apr 14, 2026