Menu

Individual skill

deed-page

Publish files to a public deed.page URL only when the user asks to publish, deploy, host, or share a link. Create-only stays local. Hosting is public; publish only a clean output folder. No account.

plugins/f-o-x11/deed-page-skill/skills/deed-page/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,530
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# deed.page

Publish a file or a clean output folder to a public `https://<slug>.deed.page/` URL with one request. No account, API key, email code, or claim link. Hosting is public: anyone with the link can view the files. The link is shareable and the site stays up until you delete it.

Publish only a clean output folder, such as `dist/`, `build/`, `out/`, `public/`, or `_site/`. Do not upload a project root, a checkout, dependencies, or secrets. The skill's `scripts/publish.sh` (and `scripts/publish-large.mjs` for folders over about 4 MB) skips sensitive and repo-metadata paths, prints a short summary of what it skipped, and prefers `dist`, then `build`, `out`, `public`, or `_site` when the path looks like a project root (`package.json` together with `src/`, or `.git`). If none of those output folders exists, the script stops. Publish that root only when the user explicitly wants it, and pass `--allow-root`.

Paths the scripts always skip: `.env` and `.env.*`, `.git`, `.github`, `.ssh`, `node_modules`, `*.pem`, `*.key`, `id_rsa*`, `.npmrc`, `.netrc`, `.DS_Store`, other dotfiles (`.well-known` is allowed), `credentials.json`, and `secrets.*`. Symlinks are skipped too. Run `scripts/publish.sh <folder> --dry-run` to see the file list and the skip summary without uploading.

Use this skill when the user asks to publish, deploy, host, share a link, put it online, or give them a link for something you generated: an HTML report, dashboard, slide deck, landing page, prototype, game, or docs folder. That request authorizes the upload.

A create-only request ("make a website", "build a page") produces a local draft only. Show the files and offer to publish. Upload only after the user asks to publish or confirms that offer.

Any other request stops before an upload. Show the destination (a public URL on deed.page, publicly accessible) and the exact file list, and ask for confirmation.