Menu
Fetch and summarize a list of URLs (e.g. from OneTab) into Obsidian-friendly markdown with a brief description of each link.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Given a YouTube URL, fetch its transcript and extract atomic notes into an Obsidian vault. Use when handed a YouTube link to mine for ideas, or asked to "turn this video into atomic notes / atoms".
Create a dated zip backup of the Obsidian vault and rotate old backups on a grandfather-father-son schedule (14 daily, 5 weekly, 12 monthly, 5 yearly). Use when asked to back up the vault, make a snapshot, or run/prune vault backups.
Extract actionable lessons, key insights, emergent todos, and best practices from a note (e.g. a video transcript or article in an Obsidian vault, for example). Use when asked to "extract insights / lessons / takeaways" from a note or document. Outputs bullet lists in chat, or writes them to a markdown file if asked.
Summarize the past week's daily notes, extracting key findings, links, action items, and potential atomic notes, and write the summary into the matching weekly note.
Summarize the current agent session, create an Obsidian note for it, and link it from today's daily note. Use when the user is finished with a session and wants to log what was accomplished.
Find lat/lon coordinates for a place mentioned in a note and add them to the frontmatter for map integration
| name | summarize-urls |
| description | Fetch and summarize a list of URLs (e.g. from OneTab) into Obsidian-friendly markdown with a brief description of each link. |
| allowed-tools | WebFetch, Bash |
| argument-hint | <paste URL list> |
Turn a batch of URLs -- typically exported from OneTab or a similar browser extension -- into a curated, Obsidian-friendly markdown summary. Each link is fetched, read, and distilled into a short description so the list becomes a useful reference note rather than a wall of raw URLs.
The user will paste a list of URLs. Each line can be in one of these formats:
| Format | Example |
|---|---|
url | title | https://example.com | Example Site |
url | title | source | https://example.com | Example Site | Hacker News |
| bare URL | https://example.com |
\| (pipe surrounded by spaces) to separate URL from title/source.For each URL:
(could not fetch) and use the title if available.Fetch multiple URLs in parallel where possible to save time.
Structure the output as:
## Link Summary
| Link | Summary |
| --- | --- |
| [Display Title](url) | 1-2 sentence summary |
| ... | ... |
If there are more than 5 links and clear thematic clusters emerge (e.g. "AI / Agents", "Web Dev", "Security"), group them under subheadings instead of a single flat table:
## Link Summary
### AI / Agents
| Link | Summary |
| --- | --- |
| ... | ... |
### Web Dev
| Link | Summary |
| --- | --- |
| ... | ... |
obsidian vault.obsidian daily:append content="<the full markdown summary>" silent
Tell the user the summary was appended to their daily note, with a brief count (e.g. "Added 8 links to your daily note"). Then ask if they'd like to: