Share file handoff

Skill LIghtJUNction/lightjunction/skills/share-file-handoff

I'M LIghtJUNction

Install

npx -y skills add LIghtJUNction/lightjunction --skill share-file-handoff

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

File handoff workflow using share.lmm.best. Use this skill when the user asks to deliver files, share downloads, send work products to customers, create a file link, DM a finished file, or manage the lmm.best file transfer service.

SKILL.md

3.4 KB, as published. Nobody here has run it

Share File Handoff

Use share.lmm.best to deliver non-secret files to customers or social contacts with direct download links.

Service Facts

Public service URL: https://share.lmm.best/
Login helper URL: https://share.lmm.best/?h
Software: copyparty
systemd service: share-lmm-best.service
Local listener: 127.0.0.1:8095
Nginx config: /etc/nginx/conf.d/share.lmm.best.conf
File root: /srv/share-lmm-best/files
Admin password file: /root/.kimaki/secrets/share-lmm-best-admin-password.txt
Certificate path: /etc/letsencrypt/live/share.lmm.best/

Security Rules

Never use the share service for:

Private keys.
Seed phrases.
Passwords.
OAuth tokens.
Cookies.
Account recovery codes.
Production credentials.
Sensitive customer data unless the user explicitly approves a safer channel.

Treat every shared URL as public to anyone who has the link. The root directory is not publicly listable, but individual files are accessible by URL.

Delivery Model

The intended flow is:

Create or receive a non-secret deliverable file.
Use scripts/share-file.sh to put it under /srv/share-lmm-best/files/ using a hard-to-guess folder name.
Verify the URL returns HTTP 200.
Send the URL to the recipient by Bluesky DM, Discord, email, or public reply when public delivery is acceptable.

Preferred Handoff

From the lightjunction repository, use the validated helper:

scripts/share-file.sh ./deliverable.zip

An optional second argument sets a sanitized display name. The helper creates a random delivery directory, installs a regular file with mode 0644, cleans up failed deliveries, and prints the final https://share.lmm.best/... URL.

Verify:

curl -I "https://share.lmm.best/$token/deliverable.zip"

Expected result: HTTP/2 200.

Admin Access

Use the web UI only when needed:

https://share.lmm.best/?h

The admin password is stored locally at:

/root/.kimaki/secrets/share-lmm-best-admin-password.txt

Do not paste the password into chat, posts, commits, or public logs.

Health Checks

Run these checks after changes:

systemctl is-active share-lmm-best.service
systemctl is-enabled share-lmm-best.service
curl -I https://share.lmm.best/health.txt
curl -I https://share.lmm.best/

Expected:

Service is active and enabled.
health.txt returns HTTP/2 200.
Root path returns HTTP/2 403 for anonymous users.

Check certificate renewal:

certbot renew --dry-run --cert-name share.lmm.best

DM Delivery

Bluesky DMs require app-password DM access and recipient permission. Before sending a DM, make sure the recipient asked for or clearly welcomed private handoff.

Good DM template:

Here is the file/link I prepared:
https://share.lmm.best/<token>/<file>

It is a public-by-link download. Please do not send secrets through this link.

Public Post Language

When promoting this capability, say:

I can deliver finished files through share.lmm.best links: static pages, small
reports, copy drafts, checklists, or zipped assets. Public-by-link delivery only;
no secrets or private keys.