Publish a family artifact (a progress report or the academic map) to a shareable destination — a shared folder, a static host, Google Drive, or GitHub Pages — tracking config vs status in files.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add manishiitg/coding-agent-loop --skill publish --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Publish?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/manishiitg-publish)More formats (shields.io, HTML) on the badges page.
---
name: publish
description: Publish a family artifact (a progress report or the academic map) to a shareable destination — a shared folder, a static host, Google Drive, or GitHub Pages — tracking config vs status in files.
---
# Publish an artifact
Share a finished HTML artifact (usually a progress report or the academic map) so
another adult in the child's life — a co-parent, a tutor — can view it. Same
config vs status contract as AgentWorks:
- `publish.json` (at the workspace root) — declarative config: `enabled`, the
destination, and which files it covers.
- `publish/status.json` — the operational result of the last publish (state,
timestamps, published URLs/paths, errors).
Never write status into `publish.json`.
## Steps
1. **Read config.** `cat publish.json`. If it is missing, do NOT publish silently:
tell the parent publishing isn't set up and ask where they'd like to share
(a shared/synced folder, a static host, Google Drive, GitHub Pages). Setting up
the destination is a one-time decision.
2. **First publish is ATTENDED.** Never do the first (verifying) publish
unattended — confirm the destination with the parent so nothing goes to the
wrong place. Only re-publish automatically once `publish/status.json` shows the
destination is already `verified`.
3. **Publish** the covered files (e.g. `reports/*.html`) using your shell. Easiest:
**Google Drive via the `gws` CLI** — `gws drive +upload` the report, then share
the link (the parent already has `gws` authenticated). Other options: copy to a
synced folder, or push to a Pages branch, as configured. Never publish
parent-only files — any `*-KEY.md`/`*-KEY.html` answer key, or `memory/` — or
secrets.
4. **Write `publish/status.json`** — `state` (`verified` / `pending` / `failed`),
timestamps, the published location/URL per file, and any error.
5. **Tell the parent** what was published and where (the link/path), and who can now
see it.
6. **Then end the turn with `suggest_actions`** — "Tell the parent" above is not the last step.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!