メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Build a designed, self-contained HTML academic map of the child's subjects, topics, and materials, plus real coaching notes for the parent on how to teach them better.
Build a designed, self-contained HTML progress report for the child — how she's actually doing, and what to work on next — surfaced in the Progress tab for both parent and child.
Create clear, child-ready study material (notes, worked examples, a revision sheet) for a topic, matched to the child's level and their own uploaded materials, packaged as one activity.
Create a practice test for the child from their materials and progress — child-facing questions with a separate parent-only answer key, packaged as one activity.
Extract genuine interest signals from the child's own conversations and keep memory/interests.md current — a Pulse-only skill, not triggered by a direct parent request.
Extract durable things the parent has said in chat and keep memory/preferences.md current — a Pulse-only skill, not triggered by a direct parent request.
| 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. |
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.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.
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.
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.
Write publish/status.json — state (verified / pending / failed),
timestamps, the published location/URL per file, and any error.
Tell the parent what was published and where (the link/path), and who can now see it.