agentleFS
jakubtobiaszjakubtobiasz/second-brain-template/.agents/skills/capture/SKILL.md

capture

Skill0 starsChanged 8 days agoMITView on GitHub

Save something into the second brain's inbox (00-inbox/) without processing it. Use when the owner shares a URL, pastes text, a transcript, or an idea and says "save this", "clip this", "add to inbox", "remember this article", or wants to keep something for later. Does not write wiki pages; hand off to the ingest skill if the owner wants it processed now.

60 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use weekly, brief and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • gaiaaiagentSkill

    weekly

    Generate a weekly digest rolling up dailies into higher-level pattern analysis

    Also in 4 projects that use this

  • AnthropicSkill

    brief

    Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

    Also in 6 projects that use this

  • QuixiAISkill

    weekly-review

    Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week

    Also in 5 projects that use this

  • dubwoahSkill

    ask

    Answer questions about the codebase without generating or modifying any code. Use when the user wants to understand how something works, find where something is defined, or explore the project structure. Invoked with /ask.

    Also in 4 projects that use this

  • termdockSkill

    recall

    Retrieves cross-session memories about past decisions, lessons, and patterns. Use when user asks about prior work, past decisions, or mentions a feature. Triggers include check memory, what did we decide, how did we solve.

    Also in 6 projects that use this

  • AlexPEClubSkill

    refine

    Always use when the user wants to discuss an exsiting feature or specification. Open an existing feature spec to improve, extend, or fundamentally challenge it. Pass the feature ID as argument (e.g. /refine PROJ-2).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 58 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If fetching fails or is paywalled, save the URL plus whatever the owner pasted, and say so.

    line 15
  2. Very specific:

    Never overwrite an existing inbox file.

    line 36
  3. Very specific:

    If the owner says "save and ingest", run capture, then follow the ingest skill on the new file.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 58 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Capture: anything → 00-inbox/

Goal: get the material into the vault fast, faithfully, with enough metadata for a later ingest. Capture never touches 20-wiki/, index.md, or 10-raw/.

Steps

  1. Identify the input
    • URL: fetch the page and convert to clean markdown (main content only, no nav/ads/comments). If fetching fails or is paywalled, save the URL plus whatever the owner pasted, and say so.
    • Video URL: if yt-dlp is available, get title/channel/date and the transcript (yt-dlp --skip-download --write-auto-subs --sub-format vtt); otherwise ask the owner to paste the transcript.
    • Pasted text / idea / transcript: use it verbatim.
    • File path: if it is already in 00-inbox/, there is nothing to do. Otherwise copy (don't move) it into 00-inbox/.
    • Already have it? If qmd is installed, qmd search "<title or url>" -c wiki -c raw -n 3. If it's already ingested, tell the owner and ask before capturing a duplicate. (The inbox itself is not indexed.)
  2. Write 00-inbox/YYYY-MM-DD-short-title.md (today's date, kebab-case, at most 6 words):
    ---
    captured: YYYY-MM-DD
    source_type: article | paper | video | podcast | transcript | note | idea | other
    title: Original Title
    author:
    published:
    url:
    why: "<the owner's reason for saving it, if given>"
    ---
    
    <content, verbatim. Do not summarize, rewrite, or "clean up" claims>
    Never overwrite an existing inbox file; add -2 to the name if it is taken.
  3. Images referenced by the page: download to 10-raw/assets/ only if the owner asks or they carry essential information (charts, diagrams). Link them with relative paths.
  4. Report in one line: the file path, plus "say ingest it to process now".

Rules

  • Verbatim over pretty. Capture is a copy, not an interpretation.
  • No log.md entry (nothing in the knowledge layer changed).
  • If the owner says "save and ingest", run capture, then follow the ingest skill on the new file.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.