How do I install the Vault Fetch skill?

Run npx skillmds@latest add pantheon-org/vault-fetch in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vault Fetch safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vault Fetch?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vault Fetch free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vault Fetch?

pantheon-org (@pantheon-org) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vault Fetch by pantheon-org — Agent Skill

Name: Vault Fetch
Author: pantheon-org

Vault Fetch

Fetch a URL, extract its text content, and persist it as a semantic memory tagged with the source URL for future retrieval. Use when the user shares a link to documentation, a GitHub issue, a blog post, or any reference material that should be available across sessions without re-fetching.

pantheon-org b40e3e5 19 files · 10.8 KB Updated Sep 17, 2026

File contents

vault-fetch

Fetch a URL, extract its text content, and persist it as a semantic memory.

Mindset

Any URL the user pastes that represents reference material — documentation, an issue, an RFC, a blog post — should be fetched proactively without waiting to be asked. If the URL will be useful in more than the current message, persist it.

When to use

User shares a documentation link to consult during the project
A GitHub issue or PR contains important context
External reference material needs to be available across sessions

How to use

vault-cli fetch "<url>" [--project <id>]

The content is automatically:

Captured with tier: semantic and forceCapture: true
Truncated to 4000 characters
Tagged with the source URL

No --tier flag is needed or accepted — tier is set automatically.

Error handling

If the fetch fails (non-2xx response, timeout, or auth-gated page), fall back to capturing the URL and title manually:

vault-cli capture --text "Reference: <title> — <url>" --tier semantic --tags reference,<topic>

Examples

vault-cli fetch "https://bun.sh/docs/api/sqlite"
vault-cli fetch "https://github.com/org/repo/issues/42" --project my-app
vault-cli fetch "https://datatracker.ietf.org/doc/html/rfc9457" --project api

Never

Never add --tier — tier is set automatically to semantic; passing it will cause an error
Never fetch auth-gated URLs (e.g. private GitHub repos, internal wikis behind SSO) — they return 401/403 and capture an error page instead of useful content; use the manual capture fallback instead
Never fetch file:// or localhost URLs — these are local paths unavailable to the fetch command
Never wait to be asked when the user pastes a reference URL — fetch it proactively

---name: vault-fetchdescription: Fetch a URL, extract its text content, and persist it as a semantic memory tagged with the source URL for future retrieval. Use when the user shares a link to documentation, a GitHub issue, a blog post, or any reference material that should be available across sessions without re-fetching.---# vault-fetchFetch a URL, extract its text content, and persist it as a semantic memory.## MindsetAny URL the user pastes that represents reference material — documentation, anissue, an RFC, a blog post — should be fetched proactively without waiting to beasked. If the URL will be useful in more than the current message, persist it.## When to use- User shares a documentation link to consult during the project- A GitHub issue or PR contains important context- External reference material needs to be available across sessions## How to use```bashvault-cli fetch "<url>" [--project <id>]```The content is automatically:- Captured with `tier: semantic` and `forceCapture: true`- Truncated to 4000 characters- Tagged with the source URLNo `--tier` flag is needed or accepted — tier is set automatically.## Error handlingIf the fetch fails (non-2xx response, timeout, or auth-gated page), fall back tocapturing the URL and title manually:```bashvault-cli capture --text "Reference: <title> — <url>" --tier semantic --tags reference,<topic>```## Examples```bashvault-cli fetch "https://bun.sh/docs/api/sqlite"vault-cli fetch "https://github.com/org/repo/issues/42" --project my-appvault-cli fetch "https://datatracker.ietf.org/doc/html/rfc9457" --project api```## Never- **Never add `--tier`** — tier is set automatically to `semantic`; passing it will cause an error- **Never fetch auth-gated URLs** (e.g. private GitHub repos, internal wikis behind SSO) — they return 401/403 and capture an error page instead of useful content; use the manual capture fallback instead- **Never fetch `file://` or `localhost` URLs** — these are local paths unavailable to the fetch command- **Never wait to be asked** when the user pastes a reference URL — fetch it proactively

Frequently asked questions