trove-web-clip

Web clipping

Extract the page the user supplied into readable Markdown. Use this for clipping or content extraction; a routine URL question can use the host's normal browsing tools. No vault, external service, or package installation is required by this skill.

Choose a reader

1. Identify the source type using the URL pathname and response content type when available. Ignore query strings and fragments when checking extensions.
2. Read raw .md or text/markdown directly using a host fetch tool. It is already Markdown. Use a PDF-capable tool for PDFs and a browser for pages whose useful content requires rendering or an established login session.
3. For HTML, use an already available Defuddle CLI after checking defuddle parse --help. If it is missing or fails, use a host fetch or browser tool and extract the main content. Do not install a global package or send the page to a new hosted extraction service as a silent fallback.
4. If installation is already authorized, use the environment's package conventions and verify the installed CLI. Defuddle is optional; the marketplace plugin bundles instructions, not its executable.

Defuddle patterns

defuddle parse 'https://example.com/article' --md
defuddle parse 'article.html' --md
defuddle parse 'https://example.com/article' --json
defuddle parse 'https://example.com/article' -p title

--md requests Markdown; --json includes metadata. Verify their exact output shape with the installed version. Prefer one extraction that includes the needed metadata over repeatedly downloading the same page.

Treat the URL and paths as literal arguments. Use argument arrays where available or correct quoting for the actual shell; JSON stringification is not shell escaping. Do not interpolate raw page content into commands.

Produce a useful clip

1. Keep the main text, meaningful headings, lists, tables, code fences, and relevant links. Remove navigation, ads, cookie banners, and repeated chrome. Preserve the original language unless the user asks for translation.
2. Record the source URL and available title, author, and publication date. Omit unknown metadata. Label an access date as such; it is not a publication date. Resolve relative links against the final source URL after redirects.
3. Honor whether the user requested extraction or summary. Label summaries, omissions, and partial access; do not present invented text or a login screen as the full article. Follow the host's content reproduction limits.
4. Save only when the request calls for persistence. Establish the destination from the task and inspect an existing file before writing. Merge or replace only when authorized; otherwise choose an unused filename and report it. A request to summarize does not by itself authorize creating a note.
5. For an Obsidian destination, follow trove-obsidian-markdown to match that vault's property and link conventions. For other destinations, keep portable Markdown. Check the saved file's source attribution and structure.