agentleFS
Sign inStart free
mblodemblode/agent-skills/skills/save-md/SKILL.md

save-md

Skill189 starsChanged 2 months agoMITView on GitHub

Saves a named source to Markdown with provenance and faithful extraction through direct export endpoints. Use when asked to "save this article", "get the markdown", "transcribe this", or "keep this source". A URL supplied as task context alone does not trigger conversion; a chat summary stays in chat.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write the named source to a .md file, in full, and say where it is.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Save as Markdown

Write the named source to a .md file, in full, and say where it is. The body comes from the fetched bytes, never from a summary.

  • IS: one named source (URL, attachment, paste, YouTube video, Google Doc, PDF) to one .md in the user's tree.
  • IS NOT: answering from a fetch, summarizing into chat, crawling beyond the URLs named, or reconstructing a talk from memory.

Done

A .md exists where the user can open it, with this frontmatter, and reading it back returns the source's last paragraph:

---
title: "<title>"
source: "<URL or path>"
date: "<date -u +%Y-%m-%dT%H:%M:%SZ, run now>"
type: web | youtube | gdoc | sheet | slides | pdf | docx | tweet | conversation
---

Fetch with curl -sSL -o <file> <url> and read the file. Prefer a text endpoint over HTML chrome. A missing file with a named reason (paywall, login wall, bot check, private doc) beats a plausible one.

FileRead when
references/source-endpoints.mdAlways, for the URL's host: the tested endpoint, its curl line, the failure each one shows, and the opt-in fallback reader

Gotchas

  • WebFetch hands the page to a small model and returns its answer: a 1,200-word post came back as 120 words. Only Content-Type: text/markdown under 100K characters passes through intact.
  • oEmbed, GitHub ?raw=true, and Drive downloads redirect across hosts. Without -L you save an empty 301.
  • YouTube's "Sign in to confirm you're not a bot" is an IP block: --cookies-from-browser on a laptop, stop in a sandbox. The description is not the talk.
  • An empty .md next to a large PDF means a scan, not a blank document: render the pages and read them.

Maintenance only: evals/evals.json holds scenarios and routing prompts for anyone changing this skill.

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.

Check your setup, free