kubo-publish-e2e

Validates Agent HTML publishing pipeline for private IPFS Cluster deployments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort of verifying that the Agent HTML publishing pipeline for a private IPFS Cluster functions correctly, ensuring the end-to-end flow from upload to immutable share link works as expected before user rollout or demonstration.

Core Features & Use Cases

  • Full publish pipeline validation: Automatically tests token-authenticated write gate enforcement, single-file HTML publishing, directory site publishing with relative assets, default 1-week pin expiration, and permanent pinning.
  • One-click test and reporting: Includes scripts to spin up a test cluster, run all validation assertions, generate self-contained HTML reports, and debug issues with Caddy, IPFS Cluster, and the publish endpoint.
  • Use case: Ideal for DevOps engineers or AI integration specialists deploying private IPFS artifact hosting, who need to confirm the publish-to-share-link workflow is functional without manual, error-prone testing.

Quick Start

Run the one-click end-to-end test for the Agent publish pipeline by executing the make publish-e2e command in the repository root to spin up the test cluster, validate all publish steps, and generate an HTML test report.

Frequently Asked Questions about kubo-publish-e2e

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

FAQPage Schema
How do I test a private IPFS Cluster HTML publishing pipeline end-to-end?

You can validate a private IPFS Cluster HTML publishing pipeline end-to-end by spinning up a test cluster and running automated assertions against token-authenticated write gates, asset publishing, and pin expiration to generate a self-contained HTML test report.

What does token-authenticated write gate enforcement validate in an IPFS publish workflow?

Token-authenticated write gate enforcement validates that private IPFS Cluster deployments only accept publishing requests with valid tokens, ensuring secure single-file and directory asset publishing before user rollout.

How do I automate testing for IPFS CID-based content rendering via reverse proxy?

Automate IPFS CID-based content rendering tests by running validation scripts against your reverse proxy setup to confirm that published immutable share links correctly render single-file and directory site assets.

Does this IPFS publish test support both single-file and directory asset publishing?

Yes, the IPFS publish test supports both single-file HTML publishing and directory site publishing with relative assets, verifying that the full Agent workflow generates correct immutable share links.

How do I configure pin expiration when publishing artifacts to an IPFS Cluster?

Publishing artifact tests validate default 1-week pin expiration and permanent pinning configurations within a CRDT-backed IPFS Cluster pin lifecycle management workflow without requiring manual intervention.

Why does my IPFS Agent HTML publish workflow fail before user rollout?

IPFS Agent HTML publish workflows often fail due to misconfigured Caddy reverse proxies, invalid token-authenticated write gates, or broken directory asset paths, which the end-to-end test report helps identify and debug.