publish-artifact

Publish HTML files and directories to a private IPFS Cluster using bash and curl.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/chinayin/ipfs-artifact-cluster --skill publish-artifact-chinayin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-artifact
Source: https://github.com/chinayin/ipfs-artifact-cluster/tree/main/skills/publish-artifact
Command: npx skills add https://github.com/chinayin/ipfs-artifact-cluster --skill publish-artifact-chinayin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, curl.

What problem does it solve?

This Skill solves the problem of securely hosting and sharing AI-generated HTML artifacts or attachments without exposing sensitive data to the public internet, by leveraging a private IPFS Cluster to generate immutable, shareable links for internal use.

Core Features & Use Cases

  • Private Artifact Publishing: Upload single HTML files or multi-asset directories (with relative resources like CSS or images) to a private IPFS Cluster with automatic multi-replica storage for high availability and fault tolerance.
  • Immutable Shareable Links: Every publish generates a permanent, content-addressed link that never changes, with optional custom expiry (default 1 week) or permanent hosting for long-term content retention.
  • Use Case: Ideal for teams using AI tools that generate HTML artifacts, allowing internal sharing of reports, prototypes, or attachments via a secure, private hosting solution that mirrors the convenience of public artifact platforms.

Quick Start

Use the publish-artifact skill to upload your generated HTML file or site directory to your private cluster and receive a shareable link you can distribute to others for access.

Frequently Asked Questions about publish-artifact

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I securely host and share HTML artifacts internally without exposing them to the public IPFS network?

To securely host HTML artifacts without public IPFS exposure, publish them to a private IPFS Cluster. This generates immutable, content-addressed shareable links for restricted web content hosting with multi-replica storage for fault tolerance.

Can I publish a multi-asset HTML directory with CSS and images to a private IPFS Cluster?

Yes, you can publish a multi-asset HTML directory containing relative resources like CSS and images to a private IPFS Cluster. The process generates a single immutable, content-addressed link for the entire directory structure.

Do I need Python or jq installed to publish HTML files to IPFS?

No, you do not need Python or jq to publish HTML files to IPFS. This process operates using only bash and curl, requiring three pre-configured environment variables for the private cluster write ingress, read base URL, and authentication token.

How does content-addressed hosting work for sharing internal prototypes?

Content-addressed hosting for internal prototypes works by uploading files to a private IPFS Cluster, which generates a permanent link based on the content's cryptographic hash. The immutable link never changes, ensuring secure and reliable internal access.

Can I set an expiry date for immutable IPFS links used for internal attachment distribution?

Yes, you can set a custom expiry for immutable IPFS links used in attachment distribution. The default expiry is one week, but you can also choose permanent hosting for long-term content retention on the private cluster.

What are the limitations of using a private IPFS Cluster for AI-generated artifact sharing?

A limitation of using a private IPFS Cluster for AI-generated artifact sharing is the strict requirement for a pre-deployed private cluster. You must configure three specific environment variables for ingress, read base URL, and authentication before publishing any content.