publisher

Publish local HTML visuals to SCP or S3 destinations via CLI.

16|3|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/tolitius/salvador --skill publisher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publisher
Source: https://github.com/tolitius/salvador/tree/main/.claude/skills/publisher
Command: npx skills add https://github.com/tolitius/salvador --skill publisher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires boto3, and includes scripts (resource) components.

What problem does it solve?

This Skill deploys local visuals or HTML artifacts to configured remote destinations (e.g., SSH, S3), enabling hosting and sharing without manual file transfers.

Core Features & Use Cases

  • Deploys a single visual to a configured provider (SCP or S3).
  • Reads deployment configuration from resources/config.json and supports environment overrides.
  • Sets remote permissions to read-only to protect published visuals.
  • Use case: publish a visualization to a web server or cloud bucket for public access.

Quick Start

Use the publisher to deploy a local visual by running: python3 .claude/skills/publisher/scripts/publish.py visuals/gravity.html gravity-simulation

Frequently Asked Questions about publisher

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

FAQPage Schema
How do I deploy a local HTML file to a remote server using SCP?

To deploy a local HTML file to a remote server using SCP, run the publish.py script with your local visual and a target name, which transfers the file and sets remote directory permissions. It requires a resources/config.json file for connection details.

Can I publish local visual artifacts directly to an S3 bucket?

Yes, you can publish local visual artifacts to S3 by configuring S3 as your provider in resources/config.json. The deployment script uses the optional boto3 dependency to handle the file transfer to your configured cloud bucket.

What is needed to automate transferring visuals to remote destinations?

Automating visual transfers to remote destinations requires a local HTML file, a resources/config.json file defining your SSH or S3 targets, and Python installed to execute the deployment script for remote directory creation and permission setting.

Does deploying visuals with this method protect published files from being overwritten?

Deploying visuals with this method protects published files by setting remote permissions to read-only during the transfer process. This prevents accidental overwriting or unauthorized modifications on the destination server or cloud bucket.

SCP vs S3 for publishing HTML visuals: which remote destination should I configure?

Choosing between SCP and S3 for publishing HTML visuals depends on your infrastructure: SCP deploys directly to web servers via SSH, while S3 uses the boto3 library to upload artifacts to cloud buckets for public access.

Why does my visual deployment fail when transferring to a new remote directory?

Visual deployment to a new remote directory may fail if resources/config.json lacks proper SSH credentials or S3 permissions. The script attempts remote directory creation before transfer, so insufficient access rights will halt the publishing process.