paperclip-page

Publish static HTML pages and asset directories to an S3-backed CloudFront distribution.

79.8k|14.6k|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/paperclipai/paperclip --skill paperclip-page
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paperclip-page
Source: https://github.com/paperclipai/paperclip/tree/main/.agents/skills/paperclip-page
Command: npx skills add https://github.com/paperclipai/paperclip --skill paperclip-page

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aws-cli, jq, curl, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the deployment of static web content, eliminating the need for manual S3 uploads or complex CI/CD pipelines when sharing reports, prototypes, or documentation.

Core Features & Use Cases

  • Automated Deployment: Syncs local directories to a production S3 bucket with proper cache headers.
  • Ownership Verification: Uses state files to prevent accidental overwrites and ensure secure, additive updates.
  • Use Case: Quickly host a static prototype or a generated data report by pointing the Skill at your local build directory to receive a live, public URL.

Quick Start

Use the paperclip-page skill to publish the contents of the site directory to a new page with the slug demo.

Frequently Asked Questions about paperclip-page

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

FAQPage Schema
How do I publish a static site with paperclip-page?▼

Run the publish.sh script pointing to your directory containing index.html. The tool validates your source, syncs files to the configured S3 bucket, and returns a public URL.

Can I update an existing page without deleting files?▼

Yes, use the --update flag. The tool performs an additive sync and requires a local .paperclip-page/state.json file to verify ownership of the existing prefix.

What are the requirements for the source directory?▼

The directory must contain an index.html file at the root. It must not contain symlinks, hidden files, or dot-paths, and should be free of sensitive data like credentials.

Why does the tool require specific AWS environment variables?▼

The tool uses namespaced environment variables to scope uploader credentials to the helper process, preventing the accidental shadowing of global AWS identities during agent execution.