here.now

Publish static sites and store private files for agent handoffs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/big4council-prog/b4c-agent --skill here-now-big4council-prog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: here.now
Source: https://github.com/big4council-prog/b4c-agent/tree/main/optional-skills/productivity/here-now
Command: npx skills add https://github.com/big4council-prog/b4c-agent --skill here-now-big4council-prog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, file, jq, and includes scripts (resource) components.

What problem does it solve?

here.now helps agents publish static websites immediately while keeping important artifacts private in cloud Drives, so handoffs between agents work reliably without leaking sensitive files.

Core Features & Use Cases

  • Static site publishing: Publish a directory or single file at {slug}.here.now for sharing results with a stable URL.
  • Private Drive storage for agent handoff: Store private documents and assets in cloud Drives so other agents can access only what’s shared.
  • Workflow-ready automation: Works with publish.sh and drive.sh, supports authenticated (permanent) and anonymous (24h) publishing, and can update existing slugs.

Quick Start

Tell the agent to publish the folder containing your site files (with index.html at the root) to here.now and return the live site URL.

Frequently Asked Questions about here.now

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

FAQPage Schema
How do I publish a static site to a live URL using a shell script?

To publish a static site, execute publish.sh with your site directory containing index.html to generate a shareable {slug}.here.now URL for immediate access.

What is the best way to store private files for agent-to-agent handoff?

Private agent handoff is achieved by using drive.sh to upload artifacts to a scoped cloud Drive, keeping files secure and accessible only to agents with authorized Drive tokens.

Do I need an API key to deploy a static site permanently?

Permanent static site deployments require configuring the HERENOW_API_KEY environment variable, whereas anonymous deployments are valid for 24 hours before expiring.

Does this static site publishing tool work without installing heavy web server dependencies?

Static site publishing and private Drive storage operate using only curl, file, and jq command-line dependencies, requiring no heavy web server installations or complex runtime environments.

Can I update an existing static site URL with new content?

Yes, the publishing workflow supports updating existing slugs, allowing you to overwrite and refresh content at your established {slug}.here.now URL without generating a new link.

What are the limitations of anonymous static site publishing?

Anonymous static site publishing is limited by a 24-hour expiration window, meaning unauthenticated URLs and their associated site files are automatically deleted after that timeframe.