メニュー
Back up the family's learning workspace to a durable destination (local git checkpoint, a private GitHub repo, or an object store like Cloudflare R2 / S3), 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 | backup |
| description | Back up the family's learning workspace to a durable destination (local git checkpoint, a private GitHub repo, or an object store like Cloudflare R2 / S3), tracking config vs status in files. |
Protect the family's data — materials, generated study/tests/reports, the academic map, and conversations.
Choosing the destination — this workspace is IMAGE-HEAVY (photos/scans of homework). Do NOT recommend GitHub as the main backup: git keeps every version of every binary, so an image-heavy repo bloats fast, and GitHub rejects large files. Prefer, in order:
gws CLI (recommended — already set up). The parent
has the Google Workspace CLI installed and authenticated, so upload the
workspace straight to their Drive with gws drive +upload (run
gws drive +upload --help for the exact flags). Ideal for image-heavy content,
and it's the parent's own storage.rclone sync, if
the parent set one up.Config and status are SEPARATE files (same contract as AgentWorks):
backup.json (at the workspace root) — the declarative config: enabled, mode,
and destinations.backup/status.json — the operational result of the last attempt (state,
timestamps, per-destination results, errors, and the current source hash).
Never write status fields into backup.json.Read config. cat backup.json if it exists. If it is missing or backup is
disabled, do NOT silently skip: set up the zero-config local git default (no
credentials needed) and back up. Then tell the parent that local-only is a
rollback checkpoint, NOT durable off-device protection, and offer to add a remote
(a private GitHub repo, or an object store like Cloudflare R2 / S3). Creating a
repo/bucket is a one-time decision — ask the parent before creating one.
Skip if unchanged. Compute a source hash of the content, e.g.
find . -type f -not -path './.git/*' -not -path './backup/*' | sort | xargs shasum 2>/dev/null | shasum.
If backup/status.json shows this exact hash already backed up successfully,
SKIP and report "already backed up".
Back up per the configured destinations, using your shell:
git init (once), git add -A, git commit -m "backup <date>". A local checkpoint only.git push to the configured remote (repo + auth set up once — use gh if available, or the remote the parent configured).rclone sync or aws s3 sync the workspace to the configured bucket (bucket + credentials set up once).Write backup/status.json — state (healthy for a verified remote, local_only, or failed), last attempt + success timestamps, per-destination result, any error, and the current source hash.
Tell the parent in plain words: what was backed up, where, and whether it is durable (remote) or just a local checkpoint. If no remote is configured, offer to set one up.