aidrop.link
Sign inAdd Skill

1. Add the Skill

In a compatible AI coding environment, ask:

Add Skill from https://aidrop.link/SKILL.md

Then open the static project you want to publish. When an account action is needed, your assistant asks for your email address and then for the one-time code sent by aidrop.link.

Before publishing: your build should include an index.html file and use relative asset paths. Server-side runtimes and databases are not part of a static share.

2. Tell your AI how to share it

Include the site, visitors, password, and expiration in one request when you know them. Your assistant asks only for details that are still missing.

“Share this site to aidrop. Allow @example.com and protect it with Demo123.” “Sign in with myemail@test.test. Share this site publicly, with no expiration or password.” “Share the static build in ./dist to aidrop.”

The source can be a directory, ZIP archive, or explicit file list. On success, your assistant returns the live URL and the important share settings.

Choose the right access

Public

Anyone with the URL can visit. This option is available when your current account rights include it.

Password protected

Visitors enter a password before opening the share. Your assistant does not repeat the password or save it to project files.

Email or domain restricted

Allow named email addresses or entire domains. You can also add a password when your account permits password protection.

Available visibility, expiration, and size choices are returned by the API for your current plan. Your assistant should treat those account rights as the source of truth.

3. Keep every share current

Ask the Skill to list or inspect shares, change access, publish a replacement version, remove a file, or restore a retained version when your plan supports it.

“Update this share with the latest version.” “List my current shares.” “Make the product demo public with no time limit.” “Restore the previous version of the client preview.”

A replacement upload is the complete desired site—it replaces the current file set. Before updating, the assistant fetches the current settings and keeps them as defaults so an omitted field does not reset your configuration.

Safety built into the workflow

  • Tokens remain private and are not printed or stored in the published project.
  • Destructive actions such as deleting a share require explicit confirmation.
  • Read-only or locked shares are not mutated.
  • Expired sessions use the secure refresh flow or restart email-code authentication.
  • Blocked executable and archive types are flagged before upload.

Add the Skill