- Home
- Skills
- Ericvicenti
- Seed Hypermedia Skills
- Seed Hypermedia
seed-hypermedia_skill
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill ericvicenti/seed-hypermedia-skills --skill seed-hypermedia- SKILL.md7.1 KB
Overview
This skill provides CLI access to the Seed Hypermedia network so you can read, search, and manage hypermedia content using hm:// URLs. It exposes document fetch, search, account and activity commands with flexible output formats and server configuration. Use it to resolve Hypermedia-enabled HTTPS sites into hm:// identifiers and interact directly with Seed servers.
How this skill works
The CLI queries Seed servers (default https://hyper.media) to fetch documents, raw IPFS blocks, stats, and activity by Hypermedia ID or CID. For HTTPS sites that advertise Hypermedia headers, you can extract the hm:// ID and then use the CLI to retrieve fully resolved markdown, metadata, or raw JSON. Global options control output format, server target, and verbosity.
When to use it
- When you need to fetch or render a document from the Hypermedia network using an hm:// URL.
- When an HTTPS site exposes Hypermedia headers and you want the underlying hm:// resource.
- When searching across the network for documents, accounts, or citations.
- When inspecting account information, contacts, or signing keys.
- When auditing activity, change history, or access capabilities for resources.
Best practices
- Always convert or confirm hm:// IDs from HTTPS sites by checking x-hypermedia headers before fetching.
- Use --md with --resolve and --frontmatter to read documents with embedded content and metadata in one view.
- Prefer --json for automation and --pretty or --yaml for human inspection in scripts and CI.
- Set a default server with config --server for consistent queries, or override per command with -s.
- Use quiet mode (-q) for concise outputs when piping into other tools.
Example use cases
- Read a document as Markdown with resolved embeds: npx -y @seed-hypermedia/cli get --md --resolve --frontmatter "hm://document-id"
- Search the network for a topic and limit results to a specific account: npx -y @seed-hypermedia/cli search "term" -a <account>
- List documents in a space sorted by update time: npx -y @seed-hypermedia/cli query "space-id" --sort UpdateTime --reverse
- Fetch a raw IPFS block by CID for debugging: npx -y @seed-hypermedia/cli cid <cid>
- Inspect recent activity or paginate results for monitoring: npx -y @seed-hypermedia/cli activity -l 50 --token <token>
FAQ
Request OPTIONS or headers from the HTTPS URL and look for x-hypermedia-id (URL encoded) which contains the hm:// identifier.
Which output format should I use for automation?
Use --json (default) for machine-readable output. Use --yaml or --pretty for human-friendly inspection.