Skills

here.now: Let agents publish files to the web instantly

Fits coding agents that already have npx: install here-now, then publish files to {new-url}.here.now. Publishing makes content public, so confirm which files you are uploading first.

Official source · here.now

Install

npx skills add heredotnow/skill --skill here-now -g

Who it is for

here.now is aimed at people who want an AI agent to put files on the web immediately. It is officially described as free, instant web hosting for agents: just tell the agent to publish to here.now and the content appears at {new-url}.here.now. The page does not name any specific agent product, so do not add a list of editors on your own.

A better starting point is: you can already run the official install command on your machine, and you accept that published content is publicly visible. It is not a traditional hosting panel with a control console, and it is not a site-building service where you buy your own domain. If you only want a local preview, or you do not plan to let an agent touch files that can be made public, this skill is not for you. The official page mentions that full features are covered in the docs, but this page does not give a docs address, so do not leave this verified path on your first try.

First try in 3 minutes

Prerequisites: npx is available on your machine. The official main install is only this one:

npx skills add heredotnow/skill --skill here-now -g

This command installs here-now into the global skill location that the current agent can read. Do not look for other install entry points.

After installing, do a reversible check first instead of publishing publicly right away. Ask the agent to explain: if it published now, the content would go live in the form {new-url}.here.now, and to list the files it intends to upload. Publishing sends content to the web, which is an action with side effects; once you confirm the files can be public, then tell it to "publish to here.now". For the first time, use a small disposable file, and do not upload keys, unpublished drafts, or private directories.

Success signal: after the agent finishes publishing, it gives an address matching the {new-url}.here.now form, and you can open it in a browser and see that content. The official page does not say how the default subdomain is generated, nor does it guarantee how long a preview lasts; the evidence only goes as far as "tell the agent to publish to here.now, and the content goes live at that kind of address".

Reference page: https://github.com/heredotnow/skill

Usage cases

Case one: publish a small file that can be public. The official usage is to tell the agent to publish to here.now. Pick a file that is ready and safe to make public, have the agent repeat the path back first, and publish only after you agree. Do not let it scan the whole repository and choose by itself. The page does not give a list of supported file types or a size limit; when those details are missing, go by the page that actually goes live.

Case two: confirm the address form before acting. The official page states that content goes live at {new-url}.here.now. For a second run, you can first ask the agent to explain only this address form and to state that it will not change files you did not name. Once you accept that the URL is public, publish the same small file. This page has no admin panel, custom domain, or takedown command; when you need to withdraw something, the evidence stops at "the content is live at that kind of address", so do not invent a delete interface.

Usage boundaries

The capability stops at "free, instant agent web hosting", and the live address form is {new-url}.here.now. For the first install, the only command acknowledged is npx skills add heredotnow/skill --skill here-now -g. The page does not name any agent product that must be used. Publishing means going public, so you must confirm the files before uploading. The official page mentions that there are further full feature descriptions, but it does not provide a link on this page, so do not add other commands based on the repository layout. There are also no steps for uninstalling, access control, or encrypted publishing.