Rickmanelius Markdown Provenance
Markdown Provenance is a Claude Code plugin for the Build phase that fingerprints markdown via IPFS and stores permanent copies on Arweave.
by rickmanelius · github.com/rickmanelius/markdown-provenance
Fingerprint markdown with IPFS and archive to Arweave so solo builders can prove when and what they published.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install rickmanelius-markdown-provenance@rickmanelius/markdown-provenanceBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:rickmanelius/markdown-provenance") and the paste-ready config with skillselion.get_install_config("plugin:rickmanelius/markdown-provenance").
What it does
Markdown Provenance is a Claude Code plugin that adds a slash command for establishing strong provenance on any markdown file. Solo builders and indie teams who publish specs, changelogs, or public docs can fingerprint content on IPFS and persist copies to Arweave without leaving the agent session. Use it when you need tamper-evident lineage for documentation, open-source writeups, or contracts rendered as markdown—not when you only need local Git history. The workflow targets permanent, decentralized storage keywords (provenance, tagging, upload) rather than a full CMS or compliance suite. Install when you are ready to anchor a markdown artifact after editing; pair with normal Git workflow for day-to-day drafts. Complexity is intermediate because you must understand IPFS hashes, Arweave funding, and what provenance does and does not prove legally.
Highlights
- Slash command workflow for markdown provenance inside Claude Code
- IPFS fingerprinting for content identity before permanent storage
- Arweave upload for long-term, decentralized archival
- Tagging and file-oriented provenance for solo publishers
- Single-plugin bundle focused on markdown—not generic file vaults
Why builders use it
Local Git and cloud drives do not give builders a simple, agent-native way to prove markdown authenticity on decentralized permanent storage.
After install, you can run a provenance slash command on a markdown file and obtain IPFS-linked fingerprints plus Arweave-backed archival references.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 10 stars, 0 votes.
FAQ
Who is rickmanelius-markdown-provenance for?
Solo builders and small teams using Claude Code who publish markdown and want IPFS fingerprints and Arweave storage without a separate toolchain.
When should I use rickmanelius-markdown-provenance?
Use it when a markdown file is final enough to anchor—specs, releases, or public docs—after edits and before you treat the file as authoritative.
How do I add rickmanelius-markdown-provenance to my agent?
Register the rickmanelius/markdown-provenance Claude Code plugin from the community catalog, then invoke its slash command on the target markdown file per the plugin docs.
Comments
Share how you use rickmanelius-markdown-provenance, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.