Skip to content
Skills Library
Science & research · Learning & explanation

source-learn

/source-learn

Turns a learning source (a web article, a PDF, a video or pasted text) into your own notes in sources/, with claims checked and suggestions for tips.md, try-next.md, cards and the glossary. Use when the user gives a link, a file or a text and wants to learn from it, "process a source", "take notes on this", or "is this worth reading".

Licence
MIT
Last repository change
01.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Turns a learning source (a web article, a PDF, a video or pasted text) into your own notes in sources/, with claims checked and suggestions for tips.md, try-next.md, cards and the glossary. Use when the user gives a link, a file or a text and wants to learn from it, "process a source", "take notes on this", or "is this worth reading".

Triggers from the description

process a sourcetake notes on thisis this worth reading
Original author description

Turns a learning source (a web article, a PDF, a video or pasted text) into your own notes in sources/, with claims checked and suggestions for tips.md, try-next.md, cards and the glossary. Use when the user gives a link, a file or a text and wants to learn from it, "process a source", "take notes on this", or "is this worth reading".

How it works

  1. Rules
  2. Steps
Original SKILL.md headings · 43 lines, 496 words
SKILL.md preview
---
name: source-learn
description: Turns a learning source (a web article, a PDF, a video or pasted text) into your own notes in sources/, with claims checked and suggestions for tips.md, try-next.md, cards and the glossary. Use when the user gives a link, a file or a text and wants to learn from it, "process a source", "take notes on this", or "is this worth reading".
---

# source-learn

Source → preview → notes → check → suggestions → (the user approves) → applied.
The register and the folders are described in `sources/README.md`.

## Rules

- **Take the information in full.** Notes hold all the facts, lists, numbers, tools, steps and rules, not a summary.
  They must answer the question "what can I use from this?". Checking claims supports that; it is not the main part.
- **Copyright.** The repository gets only your own notes, quotes of up to about 15 words, and a link to the source.
  Full texts and transcripts go in `sources/_cache/`, which git ignores.
- **Never guess at the text.** If you cannot get the full text, say what you got and ask the user to paste the rest.
- **Do not change other files without approval.** Tips, try-next, cards and the glossary get a suggestions table in the
  notes first.
- **Keep register rows.** Change the status (`queued` → `previewed` → `processed` → `applied <date>` / `not worth it`).

## Steps

1. **Get the text.**
   - Pasted text or a local file: read it.
   - Web page: read the page. Check that you have the full article and not a summary of it.
   - PDF: read it as text. If it is a scan, say so and ask the user how to proceed.
   - Video: use a transcript the user provides. If `yt-dlp` is installed, you may fetch the subtitles into
     `sources/_cache/`. Otherwise ask for the transcript.
2. **Preview.** From the title, the opening and the headings, give five lines of summary and a verdict: worth it or not.
   If it is not worth it, add a register row with the reason and stop.
3. **Choose the form.** A teaching source gets notes section by section. A practice source (someone describing how they
   work) gets an inventory: what, for what, with which data, and with what result.
4. **Write the notes** in `sources/<type>/YYYY-MM-DD-short-title.md`, where the date is the publication date. Use the
   sections of the example in `sources/web/`: header, summary, main points, what I can use, my conclusions (leave empty
   for the user), suggestions.
5. **Check the important claims** and mark each one: ✅ confirmed by a primary source (name it), ⚠️ secondary, disputed
   or unconfirmed, ❌ wrong or outdated. Order of sources: official documentation, then the tool's repository or
   changelog, then reviews and articles. Date anything that changes over time, such as versions, prices and limits.
6. **Update the register** in `sources/README.md`: add or change the row, status `processed`.
7. **Report to the user** in a few lines: the verdict, the two or three main points, how many suggestions there are.
   Ask which ones to apply.
8. **Apply only what the user approved.** Write the entries, rebuild the self-test if cards changed
   (`python cards/make_self_test.py`), mark the suggestions as applied in the notes, and set the register status to
   `applied <date>` with links in **Applied to**.
9. **Update the session records** in `_session/`. Do not commit unless asked.

Versions

The database has no other skills named source-learn.

Database snapshot: 13.11.2026 · package version 09d72653125f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95learn-from-materials
    Turn books, PDFs, slides, documents, web pages and text into a source-grounded knowledge base, interactive learning HTML and Markdown in English or Chinese. Use for learning, summaries, explanations, review, quizzes, relationship maps, saving reusable methodology files,…
  • 90add-source
    This skill should be used when the user wants to "add a source", "provide the full text for reference 3", "here is the PDF for that citation", "upload a source", "use this link for the cited paper", "add these sources", "add the sources in this folder", "add the attached files…
  • 95wicked-garden-learn
    Learn a topic or an event from outside sources and save it to the repository as KNOWLEDGE: research with cited sources, synthesize a claims ledger, walk the operator through it in chat, then author .wicked/knowledge/<slug>/ (topic.json, claims.jsonl, README.md) plus text-only…
  • 86sources
    Literature help: search papers, check the author's Zotero library and Obsidian notes, verify DOIs, write marked source notes. Use when the author needs sources or wants citations checked.
  • 100learn
    Start learning a topic or study material in the Obsidian vault. Accepts a topic, a lecture note, or any source file (PDF, slides, Word, Excel, e-book, images or photos of notes, notebooks, code, text, transcripts, web links). Has the study-researcher agent study the material,…
  • 90paper-glossary
    Use when building reusable Obsidian glossary notes from an existing paper source manifest, optionally with a raw-sections override, especially when a reader needs a reviewed shortlist before glossary notes and article links are changed.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.