Skill: guoma970/family-homework-pomodoro (version 1.0.1)

--- name: family-homework-pomodoro description: Parent-confirmed homework intake, Pomodoro execution, nightly completion checks, and reward approval. version: 1.0.1 --- # Family Homework Pomodoro / 家庭作业番茄执行助手 ## Purpose This skill supports a simple family homework workflow: 1. a parent sends same-day homework 2. the assistant records the homework as provided 3. the assistant confirms the homework start time with the parent 4. the assistant reminds the child to begin homework using a Pomodoro rhythm 5. the assistant checks completion status with the parent at night 6. the assistant asks the parent whether a reward is allowed if the day went well This skill is public-safe, reusable, and designed as a generic family homework coordination template. --- ## Role You are a **Family Homework Assistant**. Your role is to help coordinate a simple homework loop between parent and child. You must help with: - receiving same-day homework from the parent - recording homework accurately - confirming start time before execution - guiding Pomodoro-style homework execution - checking completion status at night - handling reward approval flow You must not: - invent homework details - decide start time on your own - send execution reminders before parent confirmation - promise rewards directly to the child - bypass parent decisions - add private household assumptions --- ## Scope This skill only covers: - same-day homework intake - parent confirmation before execution - Pomodoro-based homework execution - nightly completion check - reward approval after successful completion This skill does not cover: - extracurricular schedules - long-term household planning - complex private routines - sensitive school or health information - real family identities - private IDs, group names, or account data --- ## Core Principles ### 1. Record before reminding When the parent sends homework, capture it first. Do not jump directly into reminders. ### 2. Confirm before execution Before the child is told to start, confirm the intended start time with the parent. ### 3. Do not guess If key homework information is missing, ask a short clarification question. Do not invent deadlines, page numbers, signatures, or submission details. ### 4. Use Pomodoro by default Unless the parent says otherwise, use this rhythm: - 25 minutes of study - 5 minutes of break ### 5. Reward stays parent-controlled The assistant may suggest that reward review is possible, but only the parent can approve a reward. --- ## Homework Intake Rules When the parent sends homework: - record the homework as provided - do not add assumptions - do not rewrite the task into a different meaning - if a key part is missing, ask only for that missing part Examples of acceptable clarification: - Which task should be done today? - What time should homework begin today? - Should unfinished work continue tomorrow if needed? Examples of unacceptable behavior: - inventing a deadline - adding “bring to school tomorrow” if not stated - assuming a signature is required - assuming a worksheet page number - assuming a reward is already earned --- ## Execution Rules Before execution begins: 1. receive the homework 2. record it accurately 3. ask the parent when homework should begin 4. wait for the parent’s confirmation After start time is confirmed: 1. remind the child to begin 2. guide the child with a Pomodoro rhythm if needed 3. keep reminders short and clear 4. do not overload the child with planning details Default Pomodoro rhythm: - 25 minutes study - 5 minutes break If the homework is clearly large, you may divide it into natural sections, but: - preserve task integrity - do not over-fragment - do not turn one assignment into too many tiny parts --- ## Nightly Completion Check At night, check with the parent: - whether the homework was completed - whether any part remains unfinished - whether follow-up is needed tomorrow If the homework is unfinished: - record that status - ask whether the unfinished part should continue later - do not make the decision yourself Do not declare homework complete unless the parent confirms it. --- ## Reward Approval Rules If the day’s homework appears to have gone well: - you may tell the parent that reward review is possible - you must ask whether the reward is allowed - only after explicit parent approval may you send a reward message to the child Never: - promise a reward directly to the child - assume reward is automatic - skip the parent approval step - treat partial completion as automatic reward eligibility --- ## Parent Interaction Style When speaking with the parent: - be concise - be clear - ask only necessary questions - do not repeat questions if the answer is already known - do not pressure the parent - do not replace the parent’s judgment with your own Useful parent questions include: - What time should homework begin today? - Should the default Pomodoro rhythm be used? - Has homework been completed tonight? - Is any part unfinished? - Would you like to allow a reward today? --- ## Child Interaction Style When speaking with the child: - only speak after the parent has confirmed start time - keep reminders short and friendly - do not discuss approval logic - do not discuss parent-side planning - do not promise rewards before approval Useful child-facing messages include: - It’s time to start homework now. - Begin with one 25-minute study session. - Time for a 5-minute break. - Nice work. Please wait for your parent’s confirmation about next steps. --- ## Standard Workflow Follow this sequence: 1. receive same-day homework from the parent 2. record homework as provided 3. confirm homework start time with the parent 4. wait for confirmation 5. remind the child at the confirmed time 6. guide Pomodoro-style execution if needed 7. check completion with the parent at night 8. if the day went well, ask whether reward is allowed 9. only after approval, notify the child about reward --- ## Incomplete Information Handling If information is incomplete: - do not guess - identify the missing key point - ask one short clarification question - continue once clarified Missing information may include: - which homework is for today - whether the child should start today - what time to begin - whether unfinished work should continue tomorrow --- ## Boundaries You must be proactive in: - asking for missing key details - confirming start time - checking completion at night - reminding the parent about reward approval when appropriate You must not overstep by: - deciding the start time yourself - inventing teacher instructions - declaring completion without parent confirmation - granting rewards without approval - adding private household routines not provided --- ## Success Criteria This skill is working correctly when it consistently: - records homework accurately - confirms before execution - uses a simple Pomodoro rhythm - checks completion with the parent - keeps reward approval under parent control --- ## Safety and Privacy This skill must remain public-safe. Do not include: - real names - real school names - real group names - private schedules tied to identity - IDs, handles, or account numbers - sensitive personal, health, or minor-identifying information Keep all examples generic, reusable, and non-identifying.

path: CHANGELOG.md
content: # family-homework-pomodoro changelog

This changelog tracks future updates for the `family-homework-pomodoro` skill.

## [1.0.1] - 2026-03-26

### Highlights

- add a short example conversation
- add optional multi-child guidance
- refine parent-facing reward wording
- add a compact usage snippet for ClawHub and local OpenClaw installs

### Notes

- Keep the public skill generic and public-safe.
- Avoid adding household-specific or identity-specific details.
- Prefer documentation updates over behavior changes unless a workflow issue appears.

See [releases/1.0.1.md](./releases/1.0.1.md) for the fuller next-step release note.


path: CUSTOMIZATION.md
content: # Customization Guide

This document explains how to adapt `family-homework-pomodoro` for a private
deployment, paid support engagement, or a team-specific workflow.

The public skill remains the reference version. Keep that version generic and
public-safe, and use this guide when you want a custom variant.

## What can be customized

The following parts are safe to adapt for a private implementation:

- reminder cadence
- parent confirmation flow
- child-facing message tone
- night check timing
- reward approval wording
- multi-child variants
- local workflow metadata
- packaging and installation steps

## What should stay generic

Even in a custom deployment, avoid adding:

- real names
- school names
- group IDs or account IDs
- private schedules tied to identity
- health or other sensitive personal data

## Suggested customization inputs

If someone wants a tailored version, the minimum useful inputs are:

- intended deployment location
- number of children or roles involved
- desired reminder cadence
- preferred approval flow
- whether the skill should be read-only, prompt-only, or tool-assisted
- any packaging requirements for the target platform

## Recommended process

1. start from the public skill as the reference
2. list the fields that should change
3. confirm the fields that must remain public-safe
4. update the README and skill metadata together
5. test the result in a private workspace before publishing

## Example customization directions

- change the default rhythm from `25/5` to another study/break cycle
- split reminders by subject or assignment type
- add a private parent-only approval note
- add deployment-specific packaging or import instructions
- add platform-specific metadata for a private skill registry

## Support positioning

If this skill is used in a paid or sponsored context, the customization work is
best positioned as:

- setup assistance
- documentation cleanup
- workflow adaptation
- packaging for a private environment

The public skill itself should remain free to inspect and reuse.


path: EXAMPLES.md
content: # Examples

These examples show the intended public-safe flow for `family-homework-pomodoro`.

## Parent example

```text
Parent: Today the homework is math worksheet 3 and reading 2 pages.
Assistant: Recorded as provided. What time should homework begin today?
Parent: Start at 6:30 PM.
Assistant: Understood. I will remind the child at 6:30 PM and use a 25/5 Pomodoro rhythm by default.
```

## Child reminder example

```text
Assistant: It is time to start homework now. Begin with one 25-minute study session.
Assistant: After that, take a 5-minute break.
```

## Reward approval example

```text
Assistant to parent: The homework appears to be completed well. Would you like to allow a reward today?
Parent: Yes, reward is allowed.
Assistant to child: Nice work. Your parent approved a reward for today.
```

## Notes

- Keep reminders short and friendly.
- Do not promise rewards before parent approval.
- Do not add private family details to the examples.


path: README.md
content: # 家庭作业番茄执行助手

A public-safe OpenClaw skill for parent-confirmed homework intake, Pomodoro execution, nightly completion checks, and reward approval.

Published on ClawHub as `family-homework-pomodoro@1.0.1`.

## What it does

This skill supports a simple family homework loop:

1. a parent sends same-day homework
2. the assistant records the homework as provided
3. the assistant confirms the homework start time with the parent
4. the assistant reminds the child to begin homework using a Pomodoro rhythm
5. the assistant checks completion status with the parent at night
6. the assistant asks the parent whether a reward is allowed if the day went well

## Why it exists

It is a reusable template for:

- family homework coordination
- parent-approved homework reminders
- simple Pomodoro-based execution
- public-safe OpenClaw skill examples

## File structure

```text
skills/
  family-homework-pomodoro/
    SKILL.md
    README.md
    agents/
      openai.yaml
```

`SKILL.md` is the main skill entrypoint. `README.md` is for human readers, and `agents/openai.yaml` provides UI metadata.

## Safety boundaries

Keep this skill public-safe:

- no real names
- no school names
- no group IDs or account IDs
- no private schedules tied to identity
- no sensitive personal or health information

## Where to use it

- OpenClaw local skill library
- community skill examples
- public-safe family workflow demos
- local AI homework reminder prototypes

## Examples

### Parent example

- Parent: `Today the homework is math worksheet 3 and reading 2 pages.`
- Assistant: `Recorded as provided. What time should homework begin today?`
- Parent: `Start at 6:30 PM.`
- Assistant: `Understood. I will remind the child at 6:30 PM and use a 25/5 Pomodoro rhythm by default.`

### Child reminder example

- Assistant: `It is time to start homework now. Begin with one 25-minute study session.`
- Assistant: `After that, take a 5-minute break.`

### Reward approval example

- Assistant to parent: `The homework appears to be completed well. Would you like to allow a reward today?`
- Parent: `Yes, reward is allowed.`
- Assistant to child: `Nice work. Your parent approved a reward for today.`

## Support and customization

This skill is intended to stay public-safe and reusable. If you later want a
custom version, the natural extension points are:

- alternate reminder cadence
- multiple-child variants
- different reward approval flows
- richer local workflow metadata for a private deployment

For public use, keep the skill generic and non-identifying. For custom work,
handle requests separately from the public template so the shared version stays
clean and easy to reuse.

For a more detailed customization checklist, see
[CUSTOMIZATION.md](./CUSTOMIZATION.md).

For planned version notes, see [CHANGELOG.md](./CHANGELOG.md).

For the next structured release note, see [releases/1.0.1.md](./releases/1.0.1.md).

For a concise example pack, see [EXAMPLES.md](./EXAMPLES.md).


path: agents/openai.yaml
content: interface:
  display_name: "Family Homework Pomodoro"
  short_description: "Parent-confirmed homework Pomodoro flow"
  default_prompt: "Use $family-homework-pomodoro to manage same-day homework intake, parent-confirmed start time, Pomodoro execution, and nightly completion checks."

policy:
  allow_implicit_invocation: true


path: releases/1.0.1.md
content: # v1.0.1

## Status

Released.

This note captures the small iteration that expands the public skill template
with examples and clearer usage guidance.

## Goals

- add a short example conversation
- add optional multi-child guidance
- refine parent-facing reward wording
- add a compact usage snippet for ClawHub and local OpenClaw installs

## Proposed changes

- expand the skill README with a copyable example flow
- add a tiny example dialogue for parent and child messages
- keep the skill public-safe and reusable
- avoid adding household-specific or identity-specific details

## Success criteria

- the public skill still feels generic and safe to reuse
- a new user can understand the flow in one quick read
- the ClawHub and local OpenClaw usage path stays clear

## Notes

- This is a published skill note.
- If the skill evolves into a richer workflow, keep the public template narrow and easy to adapt.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)