How do I install the Share Page skill?

Run npx skillmds@latest add ci/share-page in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Share Page safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Share Page?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Share Page free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Share Page?

ci (@ci) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Share Page by ci — Agent Skill

Name: Share Page
Author: ci

Publish an HTML page to the personal share domain share.ca7.ir. Explicit trigger only: /share-page, 'publish this on share.ca7.ir', 'put this on my share domain'. Do NOT trigger on generic 'share' wording, Artifacts, or claude.ai sharing.

ci 21084c1 2 files · 2.9 KB Updated Sep 17, 2026

File contents

Publish a standalone HTML file at https://share.ca7.ir/<random-hash> for sharing with others. Invoke only on an explicit ask ("publish on share.ca7.ir", "give me a share link on my domain", /share-page) — never proactively, and never for the word "share" alone (sharing to Slack, sharing context, Claude Artifacts, etc. are not this skill).

Setup facts

Cloudflare Worker share-pages serves KV-backed pages on route share.ca7.ir/* (zone ca7.ir). Proxied AAAA share → 100:: exists.
Pages live in Workers KV namespace share-pages; key = hash, value = full HTML.
All credentials/IDs live in the 1Password item op://Private/cloudflare-api-token: fields credential (API token, also scoped for zones catalinirimie.com and viii.cm), account_id, and share_pages_kv_namespace_id. Follow the one-password skill rules for op reads; never print the token.
The worker serves text/html with x-robots-tag: noindex and 404s every key not in KV (including /). Unlisted-URL security only — do not publish secrets or private data.

Publish

The page must be a complete self-contained document (<!doctype html> … inline CSS/JS, no external assets required by CSP anywhere, just good practice). Then:

HASH=$(openssl rand -hex 12)
TOKEN=$(op read "op://Private/cloudflare-api-token/credential")
ACCT=$(op read "op://Private/cloudflare-api-token/account_id")
NS=$(op read "op://Private/cloudflare-api-token/share_pages_kv_namespace_id")
curl -s -X PUT "https://api.cloudflare.com/client/v4/accounts/$ACCT/storage/kv/namespaces/$NS/values/$HASH" \
  -H "Authorization: Bearer $TOKEN" --data-binary "@page.html"
curl -s -o /dev/null -w "%{http_code}\n" "https://share.ca7.ir/$HASH"   # expect 200

Give the user the full URL. To update a page in place, re-PUT the same key. To unpublish, DELETE the same KV values endpoint.

List / cleanup

curl -s -H "Authorization: Bearer $TOKEN" \
  "https://api.cloudflare.com/client/v4/accounts/$ACCT/storage/kv/namespaces/$NS/keys" | jq -r '.result[].name'

Guardrails

Never touch the ca7.ir apex or its DNS record — it points at a legacy EC2 box that serves the old site.
One page = one KV write. Do not re-upload or modify the worker script for publishing; only change the worker if the serving behavior itself must change.
Hashes are the only access control: always openssl rand -hex 12, never guessable names.

---name: share-pagedescription: Publish an HTML page to the personal share domain share.ca7.ir. Explicit trigger only: /share-page, 'publish this on share.ca7.ir', 'put this on my share domain'. Do NOT trigger on generic 'share' wording, Artifacts, or claude.ai sharing.---# Share PagePublish a standalone HTML file at `https://share.ca7.ir/<random-hash>` forsharing with others. Invoke only on an explicit ask ("publish on share.ca7.ir","give me a share link on my domain", `/share-page`) — never proactively, andnever for the word "share" alone (sharing to Slack, sharing context, ClaudeArtifacts, etc. are not this skill).## Setup facts- Cloudflare Worker `share-pages` serves KV-backed pages on route `share.ca7.ir/*` (zone `ca7.ir`). Proxied AAAA `share` → `100::` exists.- Pages live in Workers KV namespace `share-pages`; key = hash, value = full HTML.- All credentials/IDs live in the 1Password item `op://Private/cloudflare-api-token`: fields `credential` (API token, also scoped for zones `catalinirimie.com` and `viii.cm`), `account_id`, and `share_pages_kv_namespace_id`. Follow the `one-password` skill rules for `op` reads; never print the token.- The worker serves `text/html` with `x-robots-tag: noindex` and 404s every key not in KV (including `/`). Unlisted-URL security only — do not publish secrets or private data.## PublishThe page must be a complete self-contained document (`<!doctype html>` …inline CSS/JS, no external assets required by CSP anywhere, just goodpractice). Then:```bashHASH=$(openssl rand -hex 12)TOKEN=$(op read "op://Private/cloudflare-api-token/credential")ACCT=$(op read "op://Private/cloudflare-api-token/account_id")NS=$(op read "op://Private/cloudflare-api-token/share_pages_kv_namespace_id")curl -s -X PUT "https://api.cloudflare.com/client/v4/accounts/$ACCT/storage/kv/namespaces/$NS/values/$HASH" \ -H "Authorization: Bearer $TOKEN" --data-binary "@page.html"curl -s -o /dev/null -w "%{http_code}\n" "https://share.ca7.ir/$HASH" # expect 200```Give the user the full URL. To update a page in place, re-PUT the same key.To unpublish, DELETE the same KV values endpoint.## List / cleanup```bashcurl -s -H "Authorization: Bearer $TOKEN" \ "https://api.cloudflare.com/client/v4/accounts/$ACCT/storage/kv/namespaces/$NS/keys" | jq -r '.result[].name'```## Guardrails- Never touch the `ca7.ir` apex or its DNS record — it points at a legacy EC2 box that serves the old site.- One page = one KV write. Do not re-upload or modify the worker script for publishing; only change the worker if the serving behavior itself must change.- Hashes are the only access control: always `openssl rand -hex 12`, never guessable names.

Frequently asked questions

Share Page