[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WWRAZ23AFAR81FWDT9SEQ6":3,"skill-same:01M6WWRAZ23AFAR81FWDT9SEQ6":87},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":68},"01M6WWRAZ23AFAR81FWDT9SEQ6","brewpage-publish",null,"Publish HTML, markdown, text, any file, or a multi-file site to brewpage.app — free hosting with no sign-up. Paste text, share a file, upload a site, or host a temporary page and get an instant public URL to share a link. Asks namespace and password, returns the public URL. Triggers: publish, publish HTML, share link, share a link, share a file, upload to brewpage, host page, host a temporary page, host a website, free hosting, paste text, instant public URL, no sign-up, brewpage, publish site, upload site, upload directory, deploy site, сделай публичную ссылку, опубликуй.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fkochetkov-ma\u002Fbrewpage-codex-plugin\u002Fskills\u002Fbrewpage-publish\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"publish","brewpage publish","page","returns","publish site","html","instant","paste","directory","website","markdown","share a file","text","URL","free","host","deploy site","up","get","app","2026-11-10 10:12:30",false,"---\nname: brewpage-publish\ndescription: \"Publish HTML, markdown, text, any file, or a multi-file site to brewpage.app — free hosting with no sign-up. Paste text, share a file, upload a site, or host a temporary page and get an instant public URL to share a link. Asks namespace and password, returns the public URL. Triggers: publish, publish HTML, share link, share a link, share a file, upload to brewpage, host page, host a temporary page, host a website, free hosting, paste text, instant public URL, no sign-up, brewpage, publish site, upload site, upload directory, deploy site, сделай публичную ссылку, опубликуй.\"\nhomepage: https:\u002F\u002Fbrewpage.app\nuser-invocable: true\nlicense: MIT\n---\n\n# brewpage-publish\n\nPublish content to **brewpage.app** — free instant hosting for HTML pages, files, and multi-file sites. No sign-up required.\n\n## Running commands\n\nEvery shell step is ONE command of the exact shape in the fences below, run with the shell tool.\n`{baseDir}` is this skill's folder; the bundled `scripts\u002Fbrewpage-run.sh` does every upload.\n\n- Fill each `'{…}'` slot with the raw value and write every `'` inside it as `'\\''`; nothing else is\n  escaped. Never wrap a value in double quotes. An empty slot stays `''` (= omitted).\n- Never prefix or chain the command (`cd`, `VAR=…`, `;`, `&&`, `|`, `$(…)`) and never inline the text in\n  any other form: single-quoted argv is what keeps the content inert.\n- Text longer than 6,000 characters goes through `stage` (Step 6).\n- The script prints one decisive line: `OK {url}` or `OK {url} | Files: N` (then `MANAGE: …`, the private management link, and any `NOTICE: …` lines:\n  what the server skipped or adjusted), `CONFIRM: …` (exit 2, nothing uploaded) or `FAILED: …` (server reason `HTTP \u003Cstatus>: \u003Cmessage>`).\n  It removes its private run directory on every exit.\n\n## Workflow\n\n### Step 1: Parse Arguments\n\nExtract from the arguments string:\n- `--ttl N` → TTL in days (default: `15`)\n- `--entry \u003Cfilename>` → entry file for SITE uploads (default: auto-detect)\n- `--delivery-mode path|subdomain` → optional creation header; omitted means server defaults. Reject other values before upload.\n- Remaining text → `content_arg`: a path, or the exact text to publish, never a summary of it.\n\n### Step 2: Detect Content Type\n\nA `content_arg` that names a path -> probe it (read-only; prints `TYPE:`, the absolute `PATH:` to use\nbelow, and the Step 3 stats) — run with the shell tool:\n\n```bash\nbash {baseDir}\u002Fscripts\u002Fbrewpage-run.sh probe '{path}'\n```\n\n| Input | Type | `publish` type + source | API |\n|-------|------|-------------------------|-----|\n| `TYPE: site-dir` | SITE | `site-dir` + `--path` | `POST \u002Fapi\u002Fsites` (ZIP built from the dir — primary path) |\n| `TYPE: site-zip` (`.zip` file) | SITE | `site-zip` + `--path` | `POST \u002Fapi\u002Fsites` (pre-built archive upload) |\n| `TYPE: html-file` (`.html`\u002F`.htm` file) | HTML | `html-file` + `--path` | `POST \u002Fapi\u002Fhtml` (format=html, content read from the file — a real page in any namespace, NOT a raw download; the script sends a non-UTF-8 file by multipart `POST \u002Fapi\u002Ffiles` instead, bytes untouched) |\n| `TYPE: markdown` (`.md`\u002F`.markdown` file) | MARKDOWN | `html` + `--path` | `POST \u002Fapi\u002Fhtml` (format=markdown, content read from the file — renders styled, NOT a raw download; the script sends a non-UTF-8 file by multipart `POST \u002Fapi\u002Ffiles` instead, bytes untouched) |\n| `TYPE: file` (any other file) | FILE | `file` + `--path` | `POST \u002Fapi\u002Ffiles` (multipart) |\n| Anything else (`TYPE: none`, inline text) | HTML | `html` + `--text` | `POST \u002Fapi\u002Fhtml` (`format=html` when the text is a whole HTML document, `\u003C!doctype html` or `\u003Chtml` first; the script decides; else `format=markdown`) |\n\nMode rule: directory\u002FZIP → SITE. `.html`\u002F`.htm` file → HTML page. `.md`\u002F`.markdown` file → MARKDOWN page. Any other single file → FILE. Everything else → HTML (whole HTML document text as HTML, the rest as markdown). `POST \u002Fapi\u002Fsites` accepts a multipart `archive=@file.zip` or repeated `files` and matching `paths` fields; the script zips a directory to preserve relative paths.\n\n### Step 3: Show Pre-Publish Stats\n\nFrom the probe lines — SITE (dir): `HTML`, `SIZE_KB`, `ENTRY`. SITE (ZIP): `BYTES`, entry override. FILE, MARKDOWN, HTML file: `BYTES` + `MIME`. TEXT: char count.\n\nFor HTML\u002FFILE:\n```\nContent:  \u003Ctype description> · \u003Csize> · \u003Capi endpoint>\nTTL:      \u003CN> days\n```\n\nFor SITE (entry = server rule: `--entry` > root `index.html` > shallowest `.html`; another page → pass `--entry`; `ENTRY: none` → fail with an explicit error, never guess):\n\n**Built-static guard (before publishing).** Publish BUILT output, never project sources:\n- No `.html` file in the directory (`ENTRY: none`) → **FAIL** with an explicit error: \"No `.html` found — build the site first, then point at the build output directory.\" Do not guess an entry.\n- The directory looks like un-built sources (has `package.json` + `src\u002F` but no top-level `.html`) → **warn and ask** the user to point at the build output instead (`dist\u002F`, `build\u002F`, `out\u002F`, `_site\u002F`, or `public\u002F`). Do not publish the source tree.\n```\nContent:  site · \u003CN> files · \u003Ctotal_size> · POST \u002Fapi\u002Fsites\nEntry:    \u003Centry_file>\nTTL:      \u003CN> days\n```\nThese are source-tree estimates: report the ARCHIVE MANIFEST that Step 6 prints before upload; its\n`ENTRY:` line is the entry `scripts\u002Fpublish.mjs` resolved in the built archive.\n\n**Site limits** (`GET https:\u002F\u002Fbrewpage.app\u002Fapi\u002Flimits` returns the current ones): 25 MB per request; a site\nholds 200 files, 5 MB per file, 20 MB total uncompressed, a ZIP expands to at most 40 MB; a path is at most\n380 characters \u002F 900 bytes, each file or folder name at most 200 bytes. A big site (`FILES` or `SIZE_KB`\nnear a limit) → check the current values first, and send many files as one ZIP (a folder is always zipped). Run:\n```bash\nbash {baseDir}\u002Fscripts\u002Fbrewpage-run.sh limits\n```\nPre-checks, folder or ZIP: system files (`.DS_Store`, `__MACOSX\u002F`, `Thumbs.db`) never count and are\ndropped; hidden files and folders are dropped too, except the root `.well-known\u002F`; at least one `.html`\nfile must remain.\n\n### Step 4: Ask Namespace\n\nAsk the user:\n\n```\nNamespace decides who can find the publication; it also appears in its address on brewpage.app.\n\nOptions:\n1) public — public pages, sites and files are listed in the public gallery and the sitemap, so Google, Bing and AI search can find and index them and people can discover them. Use it for anything meant to be found or shared: docs, guides, demos, portfolios, reports, landing pages. Public pages are served right on the brewpage.app domain, which gives them the strongest reach in search; a page whose code needs its own origin (cookies, storage) gets its own subdomain automatically. Anyone can find and read a public publication: never put secrets, tokens or personal data there.\n2) {suggested slug} — private: unlisted and not indexed; anyone who has the link can still open it (a password restricts access).\n3) Enter custom namespace (private, like 2)\n4) Skip → use suggested slug (private)\n\nReply with a number or your custom namespace (1-32 lowercase letters, digits or hyphens).\n```\n\nAuto-suggest: generate a **meaningful short slug** (3-16 chars, lowercase alphanumeric + hyphens) from content context:\n- File → topic\u002Fpurpose of the file (e.g. `api-docs`, `login-page`, `report-q2`)\n- Text\u002FHTML → main subject or title (e.g. `pricing`, `team-intro`, `changelog`)\n- Site → site title or directory name (e.g. `portfolio`, `docs-site`)\n- Fallback → project name or directory name if content is ambiguous\nNever use random strings or truncated filenames — the slug should be human-readable and describe what's being published.\n\nResolution:\n- Explicit `2` or `4` → suggested slug (private)\n- `1` → `public`\n- Custom slug → validate it; `3` alone still needs the slug.\n- An empty, unavailable, ambiguous or unanswered choice → stop before upload. Never infer publication consent from silence.\n\n### Step 5: Ask Password\n\nAsk the user:\n\n```\nPassword protection (if set, page is hidden from gallery):\n\nOptions:\n1) No password (explicit choice)\n2) Use an existing local password file (min 4 characters)\n3) Skip → no password\n\nReply with a number and, for option 2, the absolute local file path. Do not paste password contents.\n```\n\nResolution: explicit `1` or `3` → `{password_file}` = `''` (no password). `2` + an existing local file\npath → `{password_file}` = that absolute path: the script moves the bytes via private header files\n(never shell literals or curl argv) and rejects control characters (header injection). Never read,\ngenerate or print the password contents.\nAn empty, unavailable, ambiguous or unanswered choice → stop before upload. A previous explicit choice for this content\u002Fworkflow may be reused; never invent one.\n\n### Step 6: Publish and Save Token (secure)\n\nNEW sites and non-public HTML pages (format `html`) get a Dedicated subdomain: an explicit `path` is not refused, the publication lands on its subdomain and the response reports the mismatch.\nEverything else defaults to Promotion (`path`) and may select `subdomain`, including password-protected uploads.\nSend the mode only as `X-Delivery-Mode` (the `--delivery-mode` slot), never in authored content or upload fields.\nDeduplication may return an OLD or NEW winner: retain its identity, cohort, mode and exact server `link`, even when the requested mode differs.\nMissing\u002Fnull OLD routing metadata means Existing link; never infer mode from its URL.\n\n> **Owner token and management link:** the script does curl, token parsing and history save in one run. It prints the URL and the management link (`MANAGE:`); the ownerToken goes to the private history file and is printed only when that save fails. A rejected upload prints only the server's status and message.\n\nEvery slot is re-validated by the script before anything is written or uploaded:\n\n| Slot | Must match |\n|------|------------|\n| `{ns}` | `^[a-z0-9-]{1,32}$` |\n| `{days}` | positive integer; `''` = 15 |\n| `{entry}` | plain relative file name, no `..`; `''` = auto-detect; sites only |\n| `{delivery_mode}` | `''`, `path` or `subdomain` |\n| `{password_file}` | `''` or an absolute path to an existing regular file |\n\nA value failing its pattern: re-ask; never clean it up or substitute it anyway. A slot error fails before\nany run is touched, so staged text survives the retry. `{type}` comes from the Step 2 table.\n\n**SITE, MARKDOWN, HTML file, FILE** — `{path}` is the probe's `PATH:` — run with the shell tool:\n```bash\nbash {baseDir}\u002Fscripts\u002Fbrewpage-run.sh publish {type} --ns '{ns}' --ttl '{days}' --entry '{entry}' --delivery-mode '{delivery_mode}' --password-file '{password_file}' --path '{path}'\n```\n\n**HTML\u002FMarkdown text** — `{content}` is the exact text, verbatim — run with the shell tool:\n```bash\nbash {baseDir}\u002Fscripts\u002Fbrewpage-run.sh publish html --ns '{ns}' --ttl '{days}' --entry '' --delivery-mode '{delivery_mode}' --password-file '{password_file}' --text '{content}'\n```\n\n**Longer text** (over 6,000 characters): split it at line ends into chunks of at most 6,000 characters.\nThe first `stage` call passes `--run ''` and prints `RUN: brewpage.XXXXXX`; every later chunk and the\nfinal publish pass that id. The script rejoins chunks with one newline. Run once per chunk:\n```bash\nbash {baseDir}\u002Fscripts\u002Fbrewpage-run.sh stage --run '{run_id}' --text '{chunk}'\n```\nThen run:\n```bash\nbash {baseDir}\u002Fscripts\u002Fbrewpage-run.sh publish html --ns '{ns}' --ttl '{days}' --entry '' --delivery-mode '{delivery_mode}' --password-file '{password_file}' --run '{run_id}'\n```\nStaged but not published (cancelled) — run:\n```bash\nbash {baseDir}\u002Fscripts\u002Fbrewpage-run.sh cleanup --run '{run_id}'\n```\n\n### Step 7: Output Result\n\n**Success** (the script printed `OK {url}`, then `MANAGE: {manage_url}`):\n```\nPublished: {url from bash output}\nManagement link (private): {manage_url from bash output}\nOwner token saved to .\u002Fbrewpage-history.md (mode 600, git-ignored)\nOptional: sign in free (Google or any email) at https:\u002F\u002Faccount.brewpage.app to manage publications and token history, and extend publication retention up to 90 days. Publications still expire. Not needed to publish.\n```\n\n**Success for SITE** (the script printed `OK {url} | Files: {count}`, then `MANAGE: {manage_url}`):\n```\nPublished site: {url from bash output}\nEntry: {entry_file} | Files: {count}\nManagement link (private): {manage_url from bash output}\nOwner token saved to .\u002Fbrewpage-history.md (mode 600, git-ignored)\nOptional: sign in free (Google or any email) at https:\u002F\u002Faccount.brewpage.app to manage publications and token history, and extend publication retention up to 90 days. Publications still expire. Not needed to publish.\n\nShare the server URL exactly as printed, including any trailing slash.\n```\n\nFor a private (non-`public`) namespace, append one short line after the link (skip if the reply must stay brief): *Unlisted link — anyone who has it can open it, but it's not in the gallery or search. Want it discoverable? Publish to `public`.*\n\nGive the user the page link and the management link, and say once that the management link is private: anyone who has it can edit or delete the page. No `MANAGE:` line → omit that line. The owner token stays in the history file for later updates; show it (read the history file) when the user asks. Never post the management link or the token publicly (public page, repo, shared channel).\n\nMention the sign-in line only as optional; never ask the user to sign in.\nIf a NOTICE says no owner capability was saved, this publication has no management link or token to give: omit both lines and report the URL plus that notice; existing history stays unchanged.\n\n**Needs confirmation** (the script printed `CONFIRM: ...`, exit 2; nothing uploaded): show the manifest\nlines, name the flagged entries, ask the user once (publish anyway \u002F cancel). Publish anyway -> re-run the\nidentical command with ` --confirmed --review-sha256 '{review_sha256}'` appended, using the exact\n`REVIEW_SHA256` printed beside the approved manifest. Changed archive bytes produce a fresh manifest and\ndigest: ask again; never silently approve the replacement. No payload is retained between calls.\nCancel or no answer -> stop: the script already removed\nits own run directory and never touches other runs, user source files or the shared tmp directory.\n\n**Error** (the script printed `FAILED: ...`):\n```\nPublish failed: {the FAILED line, verbatim}\n```\n\n**Published but not saved** (`FAILED: published but owner token could not be saved securely`, then `URL:`, `MANAGE:` and `OWNER TOKEN:` lines): the page is live and nothing was written to history. Give the user all three values and say that the management link and the token are private.\n\n| Status | Meaning | Do |\n|--------|---------|----|\n| 400 | Fixable limit or path problem (file count\u002Fsize, path length, bad value) | Fix what the message names, retry |\n| 413 | Request over 25 MB, or too many parts | Shrink the bundle; many files → one ZIP |\n| 422 | No servable file left (every file has an unsupported or missing extension) | Add the `.html`\u002Fassets |\n| 408 | Upload interrupted | Retry the identical command once |\n\nUnstorable metadata (tags, names, control characters) is stored as the closest valid value with a notice;\na value that still cannot be stored is a 400, not a 409.\n\n## Notes\n\n- History writes reject symlinks, hardlinks, tracked history and directories writable by others; failure stops publication. Archive inspection caps 25 MiB compressed, 40 MiB expanded, 200 files, 400 entries, 5 MiB\u002Fmember and 1 MiB metadata; ZIP64\u002Fsplit archives are refused.\n\n- Scripts: `scripts\u002Fbrewpage-run.sh` (the only entry), `scripts\u002Fbrewpage-lib.sh` (sourced helpers), `scripts\u002Fpublish.mjs` (offline SITE bundle build\u002Fverify), `scripts\u002Fhistory.py` (secure atomic history). Requires a POSIX runtime (macOS\u002FLinux or WSL), `bash`, `curl`, `jq`, POSIX `python3` with `fcntl`, and `git` inside repositories; sites also `node`, `zip`, `unzip`. Native Windows Python is unsupported and fails before upload.\n- **`format`**: `\u002Fapi\u002Fhtml` takes `?format=` or a JSON body `format`; a non-blank body value wins over the query, neither -> default `html` (markdown stored as raw text). The scripts send a `{content}`-only body with `?format=html` for a `.html`\u002F`.htm` file or whole-document text, else `?format=markdown`.\n- History: `.\u002Fbrewpage-history.md` in the workspace (the shell's working directory), mode `600`, added to `.\u002F.gitignore` inside a git repo. Its header holds the **delete** command for the owner token.\n- Run dirs: private `brewpage.XXXXXX` under `$TMPDIR` (else `\u002Ftmp`); only `scripts\u002Fbrewpage-run.sh` creates, fills and removes them.\n- TTL default is `15` days. Namespace must match `^[a-z0-9-]{1,32}$` and be explicitly chosen; unanswered choices stop before upload.\n- Use returned `ownerLink` and stored identity metadata for owner API operations; never parse NEW root hosts for namespace\u002FID. OLD history without metadata retains its existing API identifiers.\n- To **update a published site**, `PUT` the replacement bundle to its apex owner API with `X-Owner-Token` and `-A \"brewpage-codex\u002F0.1.1 (+https:\u002F\u002Fbrewpage.app)\"` (every brewpage.app request sends this User-Agent); retain the host and omit `X-Delivery-Mode` on ordinary PUT\u002Fupdate. Old publications (made before 5 October 2026) are read-only: 409 OLD_PUBLICATION_READ_ONLY; publish anew and give the user the new link and management link; the new owner token is saved to history.\n- Owner-only `GET`\u002F`PATCH \u002Fapi\u002F{type}\u002F{ns}\u002F{id}\u002Fhosting` supports `html|files|json|kv|sites` with `X-Owner-Token`. Read current `hostingVersion`, then PATCH `deliveryMode: path|subdomain` with that `expectedVersion`. NEW publications without a required subdomain may switch, including non-public non-HTML content; OLD returns 200 unchanged with a notice. Sites and non-public HTML (format `html`) retain their forced subdomain policy; mismatches return a notice. A missing version applies against the stored version; a stale version also applies, with a notice, rather than 409. Use the returned link\u002Fversion afterward.\n- NEW password-protected links stay clean: never generate or append `?p=`. API requests still use `X-Password`; OLD password behavior remains unchanged.\n- **SITE bundles are allowlisted**: the directory build drops dot-entries (`.env`, `.git\u002F`, `.DS_Store`; the root `.well-known\u002F` stays, extension-less files included), `node_modules\u002F`, `__MACOSX\u002F`, symlinks and unknown types (`*.map`, `*.log`, `Thumbs.db`), flags kept names that look sensitive (`secret`, `token`, `password`, `credential`) for confirmation, and verifies the archive (bounded central-directory budgets, `unzip -t` with a 10-second timeout, name set) before upload. A supplied ZIP is never rewritten; anything unexpected, hidden or sensitive inside it needs confirmation (system files the server drops are left alone).\n- Preserve `.link` exactly: NEW subdomain roots retain `\u002F`; OLD links retain their existing form. Never reconstruct a host from IDs.\n- Verify NEW native sites at the exact returned URL and asset paths; a browser proves rendering. OLD sites may still use the landing-page redirect; verify those in a browser or fetch their explicit entry asset.\n\n---\n\n## Powered by\n\n| | |\n|-|-|\n| **[brewpage.app](https:\u002F\u002Fbrewpage.app)** | Free instant hosting — HTML, files, multi-file sites. No sign-up. |\n| **[brewcode](https:\u002F\u002Fgithub.com\u002Fkochetkov-ma\u002Fclaude-brewcode)** | Plugin & skill suite — skill and agent authoring, semantic search, review setups, docs tools. |\n","# brewpage-publish\n\nPublish content to **brewpage.app** — free instant hosting for HTML pages, files, and multi-file sites. No sign-up required.\n\n## Running commands\n\nEvery shell step is ONE command of the exact shape in the fences below, run with the shell tool.\n`{baseDir}` is this skill's folder; the bundled `scripts\u002Fbrewpage-run.sh` does every upload.\n\n- Fill each `'{…}'` slot with the raw value and write every `'` inside it as `'\\''`; nothing else is\n  escaped. Never wrap a value in double quotes. An empty slot stays `''` (= omitted).\n- Never prefix or chain the command (`cd`, `VAR=…`, `;`, `&&`, `|`, `$(…)`) and never inline the text in\n  any other form: single-quoted argv is what keeps the content inert.\n- Text longer than 6,000 characters goes through `stage` (Step 6).\n- The script prints one decisive line: `OK {url}` or `OK {url} | Files: N` (then `MANAGE: …`, the private management link, and any `NOTICE: …` lines:\n  what the server skipped or adjusted), `CONFIRM: …` (exit 2, nothing uploaded) or `FAILED: …` (server reason `HTTP \u003Cstatus>: \u003Cmessage>`).\n  It removes its private run directory on every exit.\n\n## Workflow\n\n### Step 1: Parse Arguments\n\nExtract from the arguments string:\n- `--ttl N` → TTL in days (default: `15`)\n- `--entry \u003Cfilename>` → entry file for SITE uploads (default: auto-detect)\n- `--delivery-mode path|subdomain` → optional creation header; omitted means server defaults. Reject other values before upload.\n- Remaining text → `content_arg`: a path, or the exact text to publish, never a summary of it.\n\n### Step 2: Detect Content Type\n\nA `content_arg` that names a path -> probe it (read-only; prints `TYPE:`, the absolute `PATH:` to use\nbelow, and the Step 3 stats) — run with the shell tool:\n\n```bash\nbash {baseDir}\u002Fscripts\u002Fbrewpage-run.sh probe '{path}'\n```\n\n| Input | Type | `publish` type + source | API |\n|-------|------|-------------------------|-----|\n| `TYPE: site-dir` | SITE | `site-dir` + `--path` | `POST \u002Fapi\u002Fsites` (ZIP built from the dir — primary path) |\n| `TYPE: site-zip` (`.zip` file) | SITE | `site-zip` + `--path` | `POST \u002Fapi\u002Fsites` (pre-built archive upload) |\n| `TYPE: html-file` (`.html`\u002F`.htm` file) | HTML | `html-file` + `--path` | `POST \u002Fapi\u002Fhtml` (format=html, content read from the file — a real page in any namespace, NOT a raw download; the script sends a non-UTF-8 file by multipart `POST \u002Fapi\u002Ffiles` instead, bytes untouched) |\n| `TYPE: markdown` (`.md`\u002F`.markdown` file) | MARKDOWN | `html` + `--path` | `POST \u002Fapi\u002Fhtml` (format=markdown, content read from the file — renders styled, NOT a raw download; the script sends a non-UTF-8 file by multipart `POST \u002Fapi\u002Ffiles` instead, bytes untouched) |\n| `TYPE: file` (any other file) | FILE | `file` + `--path` | `POST \u002Fapi\u002Ffiles` (multipart) |\n| Anything else (`TYPE: none`, inline text) | HTML | `html` + `--text` | `POST \u002Fapi\u002Fhtml` (`format=html` when the text is a whole HTML document, `\u003C!doctype html` or `\u003Chtml` first; the script decides; else `format=markdown`) |\n\nMode rule: directory\u002FZIP → SITE. `.html`\u002F`.htm` file → HTML page. `.md`\u002F`.markdown` file → MARKDOWN page. Any other single file → FILE. Everything else → HTML (whole HTML document text as HTML, the rest as markdown). `POST \u002Fapi\u002Fsites` accepts a multipart `archive=@file.zip` or repeated `files` and matching `paths` fields; the script zips a directory to preserve relative paths.\n\n### Step 3: Show Pre-Publish Stats\n\nFrom the probe lines — SITE (dir): `HTML`, `SIZE_KB`, `ENTRY`. SITE (ZIP): `BYTES`, entry override. FILE, MARKDOWN, HTML file: `BYTES` + `MIME`. TEXT: char count.\n\nFor HTML\u002FFILE:\n```\nContent:  \u003Ctype description> · \u003Csize> · \u003Capi endpoint>\nTTL:      \u003CN> days\n```\n\nFor SITE (entry = server rule: `--entry` > root `index.html` > shallowest `.html`; another page → pass `--entry`; `ENTRY: none` → fail with an explicit error, never guess):\n\n**Built-static guard (before publishing).** Publish BUILT output, never project sources:\n- No `.html` file in the directory (`ENTRY: none`) → **FAIL** with an explicit error: \"No `.html` found — build the site first, then point at the build output directory.\" Do not guess an entry.\n- The directory looks like un-built sources (has `package.json` + `src\u002F` but no top-level `.html`) → **warn and ask** the user to point at the build output instead (`dist\u002F`, `build\u002F`, `out\u002F`, `_site\u002F`, or `public\u002F`). Do not publish the source tree.\n```\nContent:  site · \u003CN> files · \u003Ctotal_size> · POST \u002Fapi\u002Fsites\nEntry:    \u003Centry_file>\nTTL:      \u003CN> days\n```\nThese are source-tree estimates: report the ARCHIVE MANIFEST that Step 6 prints before upload; its\n`ENTRY:` line is the entry `scripts\u002Fpublish.mjs` resolved in the built archive.\n\n**Site limits** (`GET https:\u002F\u002Fbrewpage.app\u002Fapi\u002Flimits` returns the current ones): 25 MB per request; a site\nholds 200 files, 5 MB per file, 20 MB total uncompressed, a ZIP expands to at most 40 MB; a path is at most\n380 characters \u002F 900 bytes, each file or folder name at most 200 bytes. A big site (`FILES` or `SIZE_KB`\nnear a limit) → check the current values first, and send many files as one ZIP (a folder is always zipped). Run:\n```bash\nbash {baseDir}\u002Fscripts\u002Fbrewpage-run.sh limits\n```\nPre-checks, folder or ZIP: system files (`.DS_Store`, `__MACOSX\u002F`, `Thumbs.db`) never count and are\ndropped; hidden files and folders are dropped too, except the root `.well-known\u002F`; at least one `.html`\nfile must remain.\n\n### Step 4: Ask Namespace\n\nAsk the user:\n\n```\nNamespace decides who can find the publication; it also appears in its address on brewpage.app.\n\nOptions:\n1) public — public pages, sites and files are listed in the public gallery and the sitemap, so Google, Bing and AI search can find and index them and people can discover them. Use it for anything meant to be found or shared: docs, guides, demos, portfolios, reports, landing pages. Public pages are served right on the brewpage.app domain, which gives them the strongest reach in search; a page whose code needs its own origin (cookies, storage) gets its own subdomain automatically. Anyone can find and read a public publication: never put secrets, tokens or personal data there.\n2) {suggested slug} — private: unlisted and not indexed; anyone who has the link can still open it (a password restricts access).\n3) Enter custom namespace (private, like 2)\n4) Skip → use suggested slug (private)\n\nReply with a number or your custom namespace (1-32 lowercase letters, digits or hyphens).\n```\n\nAuto-suggest: generate a **meaningful short slug** (3-16 chars, lowercase alphanumeric + hyphens) from content context:\n- File → topic\u002Fpurpose of the file (e.g. `api-docs`, `login-page`, `report-q2`)\n- Text\u002FHTML → main subject or title (e.g. `pricing`, `team-intro`, `changelog`)\n- Site → site title or directory name (e.g. `portfolio`, `docs-site`)\n- Fallback → project name or directory name if content is ambiguous\nNever use random strings or truncated filenames — the slug should be human-readable and describe what's being published.\n\nResolution:\n- Explicit `2` or `4` → suggested slug (private)\n- `1` → `public`\n- Custom slug → validate it; `3` alone still needs the slug.\n- An empty, unavailable, ambiguous or unanswered choice → stop before upload. Never infer publication consent from silence.\n\n### Step 5: Ask Password\n\nAsk the user:\n\n```\nPassword protection (if set, page is hidden from gallery):\n\nOptions:\n1) No password (explicit choice)\n2) Use an existing local password file (min 4 characters)\n3) Skip → no password\n\nReply with a number and, for option 2, the absolute local file path. Do not paste password contents.\n```\n\nResolution: explicit `1` or `3` → `{password_file}` = `''` (no password). `2` + an existing local file\npath → `{password_file}` = that absolute path: the script moves the bytes via private header files\n(never shell literals or curl argv) and rejects control characters (header injection). Never read,\ngenerate or print the password contents.\nAn empty, unavailable, ambiguous or unanswered choice → stop before upload. A previous explicit choice for this content\u002Fworkflow may be reused; never invent one.\n\n### Step 6: Publish and Save Token (secure)\n\nNEW sites and non-public HTML pages (format `html`) get a Dedicated subdomain: an explicit `path` is not refused, the publication lands on its subdomain and the response reports the mismatch.\nEverything else defaults to Promotion (`path`) and may select `subdomain`, including password-protected uploads.\nSend the mode only as `X-Delivery-Mode` (the `--delivery-mode` slot), never in authored content or upload fields.\nDeduplication may return an OLD or NEW winner: retain its identity, cohort, mode and exact server `link`, even when the requested mode differs.\nMissing\u002Fnull OLD routing metadata means Existing link; never infer mode from its URL.\n\n> **Owner token and management link:** the script does curl, token parsing and history save in one run. It prints the URL and the management link (`MANAGE:`); the ownerToken goes to the private history file and is printed only when that save fails. A rejected upload prints only the server's status and message.\n\nEvery slot is re-validated by the script before anything is written or uploaded:\n\n| Slot | Must match |\n|------|------------|\n| `{ns}` | `^[a-z0-9-]{1,32}$` |\n| `{days}` | positive integer; `''` = 15 |\n| `{entry}` | plain relative file name, no `..`; `''` = auto-detect; sites only |\n| `{delivery_mode}` | `''`, `path` or `subdomain` |\n| `{password_file}` | `''` or an absolute path to an existing regular file |\n\nA value failing its pattern: re-ask; never clean it up or substitute it anyway. A slot error fails before\nany run is touched, so staged text survives the retry. `{type}` comes from the Step 2 table.\n\n**SITE, MARKDOWN, HTML file, FILE** — `{path}` is the probe's `PATH:` — run with the shell tool:\n```bash\nbash {baseDir}\u002Fscripts\u002Fbrewpage-run.sh publish {type} --ns '{ns}' --ttl '{days}' --entry '{entry}' --delivery-mode '{delivery_mode}' --password-file '{password_file}' --path '{path}'\n```\n\n**HTML\u002FMarkdown text** — `{content}` is the exact text, verbatim — run with the shell tool:\n```bash\nbash {baseDir}\u002Fscripts\u002Fbrewpage-run.sh publish html --ns '{ns}' --ttl '{days}' --entry '' --delivery-mode '{delivery_mode}' --password-file '{password_file}' --text '{content}'\n```\n\n**Longer text** (over 6,000 characters): split it at line ends into chunks of at most 6,000 characters.\nThe first `stage` call passes `--run ''` and prints `RUN: brewpage.XXXXXX`; every later chunk and the\nfinal publish pass that id. The script rejoins chunks with one newline. Run once per chunk:\n```bash\nbash {baseDir}\u002Fscripts\u002Fbrewpage-run.sh stage --run '{run_id}' --text '{chunk}'\n```\nThen run:\n```bash\nbash {baseDir}\u002Fscripts\u002Fbrewpage-run.sh publish html --ns '{ns}' --ttl '{days}' --entry '' --delivery-mode '{delivery_mode}' --password-file '{password_file}' --run '{run_id}'\n```\nStaged but not published (cancelled) — run:\n```bash\nbash {baseDir}\u002Fscripts\u002Fbrewpage-run.sh cleanup --run '{run_id}'\n```\n\n### Step 7: Output Result\n\n**Success** (the script printed `OK {url}`, then `MANAGE: {manage_url}`):\n```\nPublished: {url from bash output}\nManagement link (private): {manage_url from bash output}\nOwner token saved to .\u002Fbrewpage-history.md (mode 600, git-ignored)\nOptional: sign in free (Google or any email) at https:\u002F\u002Faccount.brewpage.app to manage publications and token history, and extend publication retention up to 90 days. Publications still expire. Not needed to publish.\n```\n\n**Success for SITE** (the script printed `OK {url} | Files: {count}`, then `MANAGE: {manage_url}`):\n```\nPublished site: {url from bash output}\nEntry: {entry_file} | Files: {count}\nManagement link (private): {manage_url from bash output}\nOwner token saved to .\u002Fbrewpage-history.md (mode 600, git-ignored)\nOptional: sign in free (Google or any email) at https:\u002F\u002Faccount.brewpage.app to manage publications and token history, and extend publication retention up to 90 days. Publications still expire. Not needed to publish.\n\nShare the server URL exactly as printed, including any trailing slash.\n```\n\nFor a private (non-`public`) namespace, append one short line after the link (skip if the reply must stay brief): *Unlisted link — anyone who has it can open it, but it's not in the gallery or search. Want it discoverable? Publish to `public`.*\n\nGive the user the page link and the management link, and say once that the management link is private: anyone who has it can edit or delete the page. No `MANAGE:` line → omit that line. The owner token stays in the history file for later updates; show it (read the history file) when the user asks. Never post the management link or the token publicly (public page, repo, shared channel).\n\nMention the sign-in line only as optional; never ask the user to sign in.\nIf a NOTICE says no owner capability was saved, this publication has no management link or token to give: omit both lines and report the URL plus that notice; existing history stays unchanged.\n\n**Needs confirmation** (the script printed `CONFIRM: ...`, exit 2; nothing uploaded): show the manifest\nlines, name the flagged entries, ask the user once (publish anyway \u002F cancel). Publish anyway -> re-run the\nidentical command with ` --confirmed --review-sha256 '{review_sha256}'` appended, using the exact\n`REVIEW_SHA256` printed beside the approved manifest. Changed archive bytes produce a fresh manifest and\ndigest: ask again; never silently approve the replacement. No payload is retained between calls.\nCancel or no answer -> stop: the script already removed\nits own run directory and never touches other runs, user source files or the shared tmp directory.\n\n**Error** (the script printed `FAILED: ...`):\n```\nPublish failed: {the FAILED line, verbatim}\n```\n\n**Published but not saved** (`FAILED: published but owner token could not be saved securely`, then `URL:`, `MANAGE:` and `OWNER TOKEN:` lines): the page is live and nothing was written to history. Give the user all three values and say that the management link and the token are private.\n\n| Status | Meaning | Do |\n|--------|---------|----|\n| 400 | Fixable limit or path problem (file count\u002Fsize, path length, bad value) | Fix what the message names, retry |\n| 413 | Request over 25 MB, or too many parts | Shrink the bundle; many files → one ZIP |\n| 422 | No servable file left (every file has an unsupported or missing extension) | Add the `.html`\u002Fassets |\n| 408 | Upload interrupted | Retry the identical command once |\n\nUnstorable metadata (tags, names, control characters) is stored as the closest valid value with a notice;\na value that still cannot be stored is a 400, not a 409.\n\n## Notes\n\n- History writes reject symlinks, hardlinks, tracked history and directories writable by others; failure stops publication. Archive inspection caps 25 MiB compressed, 40 MiB expanded, 200 files, 400 entries, 5 MiB\u002Fmember and 1 MiB metadata; ZIP64\u002Fsplit archives are refused.\n\n- Scripts: `scripts\u002Fbrewpage-run.sh` (the only entry), `scripts\u002Fbrewpage-lib.sh` (sourced helpers), `scripts\u002Fpublish.mjs` (offline SITE bundle build\u002Fverify), `scripts\u002Fhistory.py` (secure atomic history). Requires a POSIX runtime (macOS\u002FLinux or WSL), `bash`, `curl`, `jq`, POSIX `python3` with `fcntl`, and `git` inside repositories; sites also `node`, `zip`, `unzip`. Native Windows Python is unsupported and fails before upload.\n- **`format`**: `\u002Fapi\u002Fhtml` takes `?format=` or a JSON body `format`; a non-blank body value wins over the query, neither -> default `html` (markdown stored as raw text). The scripts send a `{content}`-only body with `?format=html` for a `.html`\u002F`.htm` file or whole-document text, else `?format=markdown`.\n- History: `.\u002Fbrewpage-history.md` in the workspace (the shell's working directory), mode `600`, added to `.\u002F.gitignore` inside a git repo. Its header holds the **delete** command for the owner token.\n- Run dirs: private `brewpage.XXXXXX` under `$TMPDIR` (else `\u002Ftmp`); only `scripts\u002Fbrewpage-run.sh` creates, fills and removes them.\n- TTL default is `15` days. Namespace must match `^[a-z0-9-]{1,32}$` and be explicitly chosen; unanswered choices stop before upload.\n- Use returned `ownerLink` and stored identity metadata for owner API operations; never parse NEW root hosts for namespace\u002FID. OLD history without metadata retains its existing API identifiers.\n- To **update a published site**, `PUT` the replacement bundle to its apex owner API with `X-Owner-Token` and `-A \"brewpage-codex\u002F0.1.1 (+https:\u002F\u002Fbrewpage.app)\"` (every brewpage.app request sends this User-Agent); retain the host and omit `X-Delivery-Mode` on ordinary PUT\u002Fupdate. Old publications (made before 5 October 2026) are read-only: 409 OLD_PUBLICATION_READ_ONLY; publish anew and give the user the new link and management link; the new owner token is saved to history.\n- Owner-only `GET`\u002F`PATCH \u002Fapi\u002F{type}\u002F{ns}\u002F{id}\u002Fhosting` supports `html|files|json|kv|sites` with `X-Owner-Token`. Read current `hostingVersion`, then PATCH `deliveryMode: path|subdomain` with that `expectedVersion`. NEW publications without a required subdomain may switch, including non-public non-HTML content; OLD returns 200 unchanged with a notice. Sites and non-public HTML (format `html`) retain their forced subdomain policy; mismatches return a notice. A missing version applies against the stored version; a stale version also applies, with a notice, rather than 409. Use the returned link\u002Fversion afterward.\n- NEW password-protected links stay clean: never generate or append `?p=`. API requests still use `X-Password`; OLD password behavior remains unchanged.\n- **SITE bundles are allowlisted**: the directory build drops dot-entries (`.env`, `.git\u002F`, `.DS_Store`; the root `.well-known\u002F` stays, extension-less files included), `node_modules\u002F`, `__MACOSX\u002F`, symlinks and unknown types (`*.map`, `*.log`, `Thumbs.db`), flags kept names that look sensitive (`secret`, `token`, `password`, `credential`) for confirmation, and verifies the archive (bounded central-directory budgets, `unzip -t` with a 10-second timeout, name set) before upload. A supplied ZIP is never rewritten; anything unexpected, hidden or sensitive inside it needs confirmation (system files the server drops are left alone).\n- Preserve `.link` exactly: NEW subdomain roots retain `\u002F`; OLD links retain their existing form. Never reconstruct a host from IDs.\n- Verify NEW native sites at the exact returned URL and asset paths; a browser proves rendering. OLD sites may still use the landing-page redirect; verify those in a browser or fetch their explicit entry asset.\n\n---\n\n## Powered by\n\n| | |\n|-|-|\n| **[brewpage.app](https:\u002F\u002Fbrewpage.app)** | Free instant hosting — HTML, files, multi-file sites. No sign-up. |\n| **[brewcode](https:\u002F\u002Fgithub.com\u002Fkochetkov-ma\u002Fclaude-brewcode)** | Plugin & skill suite — skill and agent authoring, semantic search, review setups, docs tools. |\n",{"name":5,"license":15,"homepage":44,"description":7,"user-invocable":45},"https:\u002F\u002Fbrewpage.app",true,"main","347aedf8480cd92b21f761e97b7343a45898f5fa","plugins\u002Fkochetkov-ma\u002Fbrewpage-codex-plugin\u002Fskills\u002Fbrewpage-publish",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":45},[58,61,64],{"tool":59,"command":60},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill brewpage-publish",{"tool":62,"command":63},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill brewpage-publish",{"tool":65,"command":66},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill brewpage-publish","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fkochetkov-ma\u002Fbrewpage-codex-plugin\u002Fskills\u002Fbrewpage-publish\u002FSKILL.md",[69,75,79,83],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fbrewpage-lib.sh","SCRIPT","脚本",13409,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fkochetkov-ma\u002Fbrewpage-codex-plugin\u002Fskills\u002Fbrewpage-publish\u002Fscripts\u002Fbrewpage-lib.sh",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fbrewpage-run.sh",11137,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fkochetkov-ma\u002Fbrewpage-codex-plugin\u002Fskills\u002Fbrewpage-publish\u002Fscripts\u002Fbrewpage-run.sh",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"scripts\u002Fhistory.py",6048,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fkochetkov-ma\u002Fbrewpage-codex-plugin\u002Fskills\u002Fbrewpage-publish\u002Fscripts\u002Fhistory.py",{"path":84,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fpublish.mjs",17445,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fkochetkov-ma\u002Fbrewpage-codex-plugin\u002Fskills\u002Fbrewpage-publish\u002Fscripts\u002Fpublish.mjs",[88,97,105,113,121,129],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":96},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":96},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":96},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":96},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":96},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":96},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]