Source profileQuality 86/100

paperclipai/paperclip/.agents/skills/paperclip-page/SKILL.md

paperclip-page

Publish static HTML pages and asset folders to the Paperclip S3/CloudFront page host. Use when asked to deploy, host, or share a persistent page, viewer, prototype, report, or static site without here.now.

Source repository stars
74,938
Declared platforms
0
Static risk flags
1
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Use this skill to publish a static directory to the configured Paperclip pages host, for example https://pages.paperclip.ing//.

Best for

  • Use when asked to deploy, host, or share a persistent page, viewer, prototype, report, or static site without here.

Not for

  • Slug already exists: choose a different slug or use --update from the
  • Missing index.html: build the static site first or point the helper at the

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/paperclipai/paperclip --skill ".agents/skills/paperclip-page"
Safe inspection promptEditorial

Inspect the Agent Skill "paperclip-page" from https://github.com/paperclipai/paperclip/blob/77979950381a99271e4690c581a7440b73807b11/.agents/skills/paperclip-page/SKILL.md at commit 77979950381a99271e4690c581a7440b73807b11. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow

    1. Inspect the source directory and confirm it is public static content only. 2. Run scripts/publish.sh --dry-run to validate local structure and see the resolved URL/prefix. 3. Choose a slug: - Use --slug when the user gave a stable URL path. - Omit --slug to derive one from th…

    Inspect the source directory and confirm it is public static content only.Run scripts/publish.sh --dry-run to validate local structure and seeChoose a slug:
  2. 02

    Update Workflow

    Updates are additive overwrites only. The helper never deletes remote objects.

    Updates are additive overwrites only. The helper never deletes remote objects.When the target prefix already exists, --update requires local ownership proof from ./site/.paperclip-page/state.json generated by an earlier publish from that same source directory. Without that state, create a new slu…
  3. 03

    Requirements

    Source directory contains index.html at its root.

    Source directory contains index.html at its root.aws CLI v2, curl, and jq are available on PATH for live publishes.Environment variables are configured:
  4. 04

    Safety Rules

    Publish public content only. Do not publish secrets, customer data, private

    Publish public content only. Do not publish secrets, customer data, privateNever print AWS secret values.Never change bucket policy, IAM, DNS, CloudFront, or ACM settings from this

Permission review

Static risk signals and limitations

Reads files

low · line 21

The documentation asks the agent to read local files, directories, or repositories.

Inspect the source directory and confirm it is public static content only.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score86/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars74,938SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
paperclipai/paperclip
Skill path
.agents/skills/paperclip-page/SKILL.md
Commit
77979950381a99271e4690c581a7440b73807b11
License
MIT
Collected
2026-07-28
Default branch
master
View the original SKILL.md

Paperclip Page

Use this skill to publish a static directory to the configured Paperclip pages host, for example https://pages.paperclip.ing/<slug>/.

Requirements

  • Source directory contains index.html at its root.
  • aws CLI v2, curl, and jq are available on PATH for live publishes.
  • Environment variables are configured:
    • PAPERCLIP_PAGE_BUCKET
    • PAPERCLIP_PAGE_BASE_URL
    • AWS_REGION
    • AWS credentials via Paperclip Secrets or an approved AWS vault
  • Optional environment variables:
    • PAPERCLIP_PAGE_DEFAULT_PREFIX
    • PAPERCLIP_PAGE_AWS_PROFILE

Workflow

  1. Inspect the source directory and confirm it is public static content only.
  2. Run scripts/publish.sh <dir> --dry-run to validate local structure and see the resolved URL/prefix.
  3. Choose a slug:
    • Use --slug <slug> when the user gave a stable URL path.
    • Omit --slug to derive one from the source directory name.
  4. Publish:
.agents/skills/paperclip-page/scripts/publish.sh ./site --slug my-page
  1. Return the printed public URL and S3 prefix to the issue/user.

Update Workflow

Updates are additive overwrites only. The helper never deletes remote objects.

.agents/skills/paperclip-page/scripts/publish.sh ./site --slug my-page --update

When the target prefix already exists, --update requires local ownership proof from ./site/.paperclip-page/state.json generated by an earlier publish from that same source directory. Without that state, create a new slug instead of overwriting another page.

Safety Rules

  • Publish public content only. Do not publish secrets, customer data, private company material, credentials, or internal logs.
  • Never print AWS secret values.
  • Never change bucket policy, IAM, DNS, CloudFront, or ACM settings from this skill. Setup belongs to an operator runbook, not the publish helper.
  • Never upload outside the configured bucket and prefix.
  • Never use aws s3 sync --delete or require s3:DeleteObject in v1.
  • The helper forces --no-follow-symlinks and fails if any source symlink is present.
  • The helper rejects hidden files and dot-segment paths except its own .paperclip-page/state.json.
  • Slugs and prefix segments must use lowercase ASCII letters, digits, and hyphens only.
  • Keep site-wide root objects such as 404.html operator-managed; publishes always target <slug>/... or <default-prefix>/<slug>/....

Troubleshooting

  • Slug already exists: choose a different slug or use --update from the original source directory containing .paperclip-page/state.json.
  • Missing index.html: build the static site first or point the helper at the directory that contains the root HTML file.
  • Found symlink: replace symlinks with real files before publishing.
  • AccessDenied: confirm the uploader IAM policy allows ListBucket, GetObject, and PutObject for the configured bucket/prefix, and that the agent received the Paperclip Secrets.
  • Public URL verification failed: check CloudFront deployment/DNS, object existence, and that the distribution uses HTTPS with the private S3 REST origin.

See README.md next to this skill for operator setup, AWS policy examples, credential rotation, and install/attach commands.

Alternatives

Compare before choosing

Computed 9531,966

K-Dense-AI/scientific-agent-skills

simpy

Build, inspect, test, and analyze bounded process-based discrete-event simulations with SimPy, including events, resources, interrupts, monitoring, replications, warm-up, and reproducible output analysis.

Computed 9237,126

github/awesome-copilot

github-release

Guides IA through releasing a new version of a GitHub library end-to-end. Handles SemVer versioning and Keep a Changelog formatting automatically.

Computed 8842,015

coreyhaines31/marketingskills

marketing-plan

When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Also use when the user mentions "marketing plan," "growth plan," "GTM plan," "go-to-market plan," "AARRR plan," "90-day marketing plan," "12-month marketing roadmap," "fractional CMO plan," or "fCMO plan." Generates an exhaustive 13-section plan structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to the client's current budget, team, and stage, mapped

Computed 8737,126

github/awesome-copilot

azure-architecture-autopilot

Design Azure infrastructure using natural language, or analyze existing Azure resources to auto-generate architecture diagrams, refine them through conversation, and deploy with Bicep. When to use this skill: - "Create X on Azure", "Set up a RAG architecture" (new design) - "Analyze my current Azure infrastructure", "Draw a diagram for rg-xxx" (existing analysis) - "Foundry is slow", "I want to reduce costs", "Strengthen security" (natural language modification) - Azure resource deployment, Bice