daycare-cli 0.0.1

package/dist/skills/skills/scheduling/SKILL.md

@@ -0,0 +1,131 @@
+---
+name: scheduling
+description: Schedule recurring or time-based tasks. Use for alarms, reminders, periodic reviews, automated reports, or any task that should run at specific times or intervals.
+---
+
+# Scheduling
+
+Daycare supports two scheduling mechanisms: **cron** for precise timing and **heartbeats** for periodic check-ins.
+
+## When to Use Cron
+
+Use cron when:
+- Exact timing matters (e.g., "every day at 9am")
+- Tasks need their own isolated agent and memory
+- One-off scheduled tasks (with `deleteAfterRun`)
+- Tasks that produce artifacts in a dedicated workspace
+
+**Cron tools:** `cron_add`, `cron_read_task`, `cron_read_memory`, `cron_write_memory`, `cron_delete_task`
+
+### Cron Routing
+
+Cron tasks run in their own dedicated cron agent by default. If you want the cron
+notification to land in an existing agent (e.g. a user chat), include `agentId`
+in `cron_add` to route the prompt to that agent instead.
+
+## When to Use Heartbeats
+
+Use heartbeats when:
+- Approximate timing is acceptable (~30 minute intervals)
+- Tasks need ongoing context from the main agent
+- Prompts evolve over time and need periodic review
+- Lightweight status checks or reminders
+
+**Heartbeat tools:** `heartbeat_add`, `heartbeat_list`, `heartbeat_run`, `heartbeat_remove`
+
+## Optional Exec Gate
+
+Both cron and heartbeat tasks can define an optional `gate` command to decide
+whether to run the LLM. The command runs first; exit code `0` means "run" and
+non-zero means "skip." This keeps checks cheap (ex: HTTP health check before notifying).
+Trimmed gate output is appended to the prompt under `[Gate output]`.
+Gates run within the target agent permissions. If `gate.permissions` are not already
+allowed, a system message is posted and the task still runs (the gate is treated as
+successful).
+
+`gate` supports:
+- `command` (required)
+- `cwd`, `timeoutMs`, `env`
+- `permissions` (required tags; must already be allowed by the target agent)
+- `packageManagers` (`dart` | `dotnet` | `go` | `java` | `node` | `php` | `python` | `ruby` | `rust`; auto-adds language ecosystem hosts; requires `@network`)
+- `allowedDomains` (network allowlist; requires `@network`)
+
+## Examples
+
+**Cron with routing + gate (`TASK.md` frontmatter):**
+
+```yaml
+---
+name: API health
+schedule: "*/10 * * * *"
+agentId: cu3ql2p5q0000x5p3g7q1l8a9
+gate:
+  command: "curl -fsS https://api.example.com/healthz >/dev/null"
+  packageManagers:
+    - node
+  allowedDomains:
+    - api.example.com
+---
+If the API is down, notify me with a short summary.
+```
+
+## Selection Examples
+
+### Choose Cron
+
+| User Input | Why Cron |
+|------------|----------|
+| "Remind me every day at 9am to check my emails" | Specific time (9am daily) |
+| "Run a backup script every Sunday at midnight" | Exact schedule needed |
+| "Send me a weather report every morning at 7:30" | Precise daily timing |
+| "Every hour, check if the server is up" | Strict hourly repetition |
+| "At 5pm on weekdays, summarize my tasks" | Complex schedule (weekdays only) |
+| "Once tomorrow at noon, remind me about the meeting" | One-off scheduled task |
+| "Every 15 minutes, poll the API for updates" | Precise interval timing |
+| "On the 1st of each month, generate a report" | Calendar-based schedule |
+
+### Choose Heartbeats
+
+| User Input | Why Heartbeat |
+|------------|---------------|
+| "Periodically check on my project status" | Ongoing review, flexible timing |
+| "Keep an eye on my git branches" | Continuous monitoring, evolving context |
+| "Remind me about my todos from time to time" | Lightweight, approximate timing |
+| "Check in on code quality occasionally" | Periodic review that needs reasoning |
+| "Monitor my open PRs and update me" | Ongoing task that evolves |
+| "Review my notes and suggest improvements" | Needs main agent context |
+| "Periodically summarize what I've been working on" | Flexible interval, ongoing |
+| "Keep track of my daily progress" | Continuous, evolving check-in |
+
+### Ambiguous Cases
+
+| User Input | Resolution |
+|------------|------------|
+| "Remind me about X regularly" | Ask: need exact times? Cron. Flexible? Heartbeat. |
+| "Check something every day" | Ask: specific time? Cron. Anytime during day? Heartbeat. |
+| "Monitor Y" | Heartbeat (monitoring implies ongoing, evolving context) |
+| "Schedule Z" | Cron (scheduling implies specific timing) |
+
+## Workflow
+
+**For cron tasks:**
+1. Determine the schedule (cron expression: `minute hour day month weekday`)
+2. Use `cron_add` with name, schedule, and prompt (optional `agentId` + `gate`)
+3. Each task gets isolated agent, memory file, and workspace
+
+**For heartbeats:**
+1. Run `heartbeat_list` to see existing tasks
+2. Use `heartbeat_add` with title and prompt (optional `gate`)
+3. Use `heartbeat_run` to trigger immediately
+4. Use `heartbeat_remove` for cleanup
+
+## Key Differences
+
+| Feature | Cron | Heartbeats |
+|---------|------|------------|
+| Timing | Exact (cron expression) | ~30 minute intervals |
+| Agent | Isolated per task | Shared main agent |
+| Memory | Persistent `MEMORY.md` | Main agent context |
+| Workspace | Dedicated `files/` dir | None |
+| One-off | Yes (`deleteAfterRun`) | No |
+| Best for | Time-sensitive tasks | Ongoing reviews |

package/dist/skills/skills/skill-creator/SKILL.md

@@ -0,0 +1,372 @@
+---
+name: skill-creator
+description: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Daycare's capabilities with specialized knowledge, workflows, or tool integrations.
+license: Complete terms in LICENSE.txt
+---
+
+# Skill Creator
+
+This skill provides guidance for creating effective skills.
+
+## About Skills
+
+Skills are modular, self-contained packages that extend Daycare's capabilities by providing
+specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific
+domains or tasks—they transform Daycare from a general-purpose agent into a specialized agent
+equipped with procedural knowledge that no model can fully possess.
+
+### What Skills Provide
+
+1. Specialized workflows - Multi-step procedures for specific domains
+2. Tool integrations - Instructions for working with specific file formats or APIs
+3. Domain expertise - Company-specific knowledge, schemas, business logic
+4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks
+
+## Core Principles
+
+### Concise is Key
+
+The context window is a public good. Skills share the context window with everything else Daycare needs: system prompt, conversation history, other Skills' metadata, and the actual user request.
+
+**Default assumption: Daycare is already very smart.** Only add context Daycare doesn't already have. Challenge each piece of information: "Does Daycare really need this explanation?" and "Does this paragraph justify its token cost?"
+
+Prefer concise examples over verbose explanations.
+
+### Set Appropriate Degrees of Freedom
+
+Match the level of specificity to the task's fragility and variability:
+
+**High freedom (text-based instructions)**: Use when multiple approaches are valid, decisions depend on context, or heuristics guide the approach.
+
+**Medium freedom (pseudocode or scripts with parameters)**: Use when a preferred pattern exists, some variation is acceptable, or configuration affects behavior.
+
+**Low freedom (specific scripts, few parameters)**: Use when operations are fragile and error-prone, consistency is critical, or a specific sequence must be followed.
+
+Think of Daycare as exploring a path: a narrow bridge with cliffs needs specific guardrails (low freedom), while an open field allows many routes (high freedom).
+
+### Anatomy of a Skill
+
+Every skill consists of a required SKILL.md file and optional bundled resources:
+
+```
+skill-name/
+├── SKILL.md (required)
+│   ├── YAML frontmatter metadata (required)
+│   │   ├── name: (required)
+│   │   └── description: (required)
+│   └── Markdown instructions (required)
+└── Bundled Resources (optional)
+    ├── scripts/          - Executable code (Python/Bash/etc.)
+    ├── references/       - Documentation intended to be loaded into context as needed
+    └── assets/           - Files used in output (templates, icons, fonts, etc.)
+```
+
+#### SKILL.md (required)
+
+Every SKILL.md consists of:
+
+- **Frontmatter** (YAML): Contains `name` and `description` fields. These are the only fields that Daycare reads to determine when the skill gets used, thus it is very important to be clear and comprehensive in describing what the skill is, and when it should be used.
+- **Body** (Markdown): Instructions and guidance for using the skill. Only loaded AFTER the skill triggers (if at all).
+
+#### Bundled Resources (optional)
+
+##### Scripts (`scripts/`)
+
+Executable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten.
+
+- **When to include**: When the same code is being rewritten repeatedly or deterministic reliability is needed
+- **Example**: `scripts/rotate_pdf.py` for PDF rotation tasks
+- **Benefits**: Token efficient, deterministic, may be executed without loading into context
+- **Note**: Scripts may still need to be read by Daycare for patching or environment-specific adjustments
+
+##### References (`references/`)
+
+Documentation and reference material intended to be loaded as needed into context to inform Daycare's process and thinking.
+
+- **When to include**: For documentation that Daycare should reference while working
+- **Examples**: `references/finance.md` for financial schemas, `references/mnda.md` for company NDA template, `references/policies.md` for company policies, `references/api_docs.md` for API specifications
+- **Use cases**: Database schemas, API documentation, domain knowledge, company policies, detailed workflow guides
+- **Benefits**: Keeps SKILL.md lean, loaded only when Daycare determines it's needed
+- **Best practice**: If files are large (>10k words), include grep search patterns in SKILL.md
+- **Avoid duplication**: Information should live in either SKILL.md or references files, not both. Prefer references files for detailed information unless it's truly core to the skill—this keeps SKILL.md lean while making information discoverable without hogging the context window. Keep only essential procedural instructions and workflow guidance in SKILL.md; move detailed reference material, schemas, and examples to references files.
+
+##### Assets (`assets/`)
+
+Files not intended to be loaded into context, but rather used within the output Daycare produces.
+
+- **When to include**: When the skill needs files that will be used in the final output
+- **Examples**: `assets/logo.png` for brand assets, `assets/slides.pptx` for PowerPoint templates, `assets/frontend-template/` for HTML/React boilerplate, `assets/font.ttf` for typography
+- **Use cases**: Templates, images, icons, boilerplate code, fonts, sample documents that get copied or modified
+- **Benefits**: Separates output resources from documentation, enables Daycare to use files without loading them into context
+
+#### What to Not Include in a Skill
+
+A skill should only contain essential files that directly support its functionality. Do NOT create extraneous documentation or auxiliary files, including:
+
+- README.md
+- INSTALLATION_GUIDE.md
+- QUICK_REFERENCE.md
+- CHANGELOG.md
+- etc.
+
+The skill should only contain the information needed for an AI agent to do the job at hand. It should not contain auxilary context about the process that went into creating it, setup and testing procedures, user-facing documentation, etc. Creating additional documentation files just adds clutter and confusion.
+
+### Progressive Disclosure Design Principle
+
+Skills use a three-level loading system to manage context efficiently:
+
+1. **Metadata (name + description)** - Always in context (~100 words)
+2. **SKILL.md body** - When skill triggers (<5k words)
+3. **Bundled resources** - As needed by Daycare (Unlimited because scripts can be executed without reading into context window)
+
+#### Progressive Disclosure Patterns
+
+Keep SKILL.md body to the essentials and under 500 lines to minimize context bloat. Split content into separate files when approaching this limit. When splitting out content into other files, it is very important to reference them from SKILL.md and describe clearly when to read them, to ensure the reader of the skill knows they exist and when to use them.
+
+**Key principle:** When a skill supports multiple variations, frameworks, or options, keep only the core workflow and selection guidance in SKILL.md. Move variant-specific details (patterns, examples, configuration) into separate reference files.
+
+**Pattern 1: High-level guide with references**
+
+```markdown
+# PDF Processing
+
+## Quick start
+
+Extract text with pdfplumber:
+[code example]
+
+## Advanced features
+
+- **Form filling**: See [FORMS.md](FORMS.md) for complete guide
+- **API reference**: See [REFERENCE.md](REFERENCE.md) for all methods
+- **Examples**: See [EXAMPLES.md](EXAMPLES.md) for common patterns
+```
+
+Daycare loads FORMS.md, REFERENCE.md, or EXAMPLES.md only when needed.
+
+**Pattern 2: Domain-specific organization**
+
+For Skills with multiple domains, organize content by domain to avoid loading irrelevant context:
+
+```
+bigquery-skill/
+├── SKILL.md (overview and navigation)
+└── reference/
+    ├── finance.md (revenue, billing metrics)
+    ├── sales.md (opportunities, pipeline)
+    ├── product.md (API usage, features)
+    └── marketing.md (campaigns, attribution)
+```
+
+When a user asks about sales metrics, Daycare only reads sales.md.
+
+Similarly, for skills supporting multiple frameworks or variants, organize by variant:
+
+```
+cloud-deploy/
+├── SKILL.md (workflow + provider selection)
+└── references/
+    ├── aws.md (AWS deployment patterns)
+    ├── gcp.md (GCP deployment patterns)
+    └── azure.md (Azure deployment patterns)
+```
+
+When the user chooses AWS, Daycare only reads aws.md.
+
+**Pattern 3: Conditional details**
+
+Show basic content, link to advanced content:
+
+```markdown
+# DOCX Processing
+
+## Creating documents
+
+Use docx-js for new documents. See [DOCX-JS.md](DOCX-JS.md).
+
+## Editing documents
+
+For simple edits, modify the XML directly.
+
+**For tracked changes**: See [REDLINING.md](REDLINING.md)
+**For OOXML details**: See [OOXML.md](OOXML.md)
+```
+
+Daycare reads REDLINING.md or OOXML.md only when the user needs those features.
+
+**Important guidelines:**
+
+- **Avoid deeply nested references** - Keep references one level deep from SKILL.md. All reference files should link directly from SKILL.md.
+- **Structure longer reference files** - For files longer than 100 lines, include a table of contents at the top so Daycare can see the full scope when previewing.
+
+## Skill Creation Process
+
+Skill creation involves these steps:
+
+1. Understand the skill with concrete examples
+2. Plan reusable skill contents (scripts, references, assets)
+3. Initialize the skill in workspace
+4. Edit the skill (implement resources and write SKILL.md)
+5. Deploy the skill to config/skills/
+6. Iterate based on real usage
+
+Follow these steps in order, skipping only if there is a clear reason why they are not applicable.
+
+### Step 1: Understanding the Skill with Concrete Examples
+
+Skip this step only when the skill's usage patterns are already clearly understood. It remains valuable even when working with an existing skill.
+
+To create an effective skill, clearly understand concrete examples of how the skill will be used. This understanding can come from either direct user examples or generated examples that are validated with user feedback.
+
+For example, when building an image-editor skill, relevant questions include:
+
+- "What functionality should the image-editor skill support? Editing, rotating, anything else?"
+- "Can you give some examples of how this skill would be used?"
+- "I can imagine users asking for things like 'Remove the red-eye from this image' or 'Rotate this image'. Are there other ways you imagine this skill being used?"
+- "What would a user say that should trigger this skill?"
+
+To avoid overwhelming users, avoid asking too many questions in a single message. Start with the most important questions and follow up as needed for better effectiveness.
+
+Conclude this step when there is a clear sense of the functionality the skill should support.
+
+### Step 2: Planning the Reusable Skill Contents
+
+To turn concrete examples into an effective skill, analyze each example by:
+
+1. Considering how to execute on the example from scratch
+2. Identifying what scripts, references, and assets would be helpful when executing these workflows repeatedly
+
+Example: When building a `pdf-editor` skill to handle queries like "Help me rotate this PDF," the analysis shows:
+
+1. Rotating a PDF requires re-writing the same code each time
+2. A `scripts/rotate_pdf.py` script would be helpful to store in the skill
+
+Example: When designing a `frontend-webapp-builder` skill for queries like "Build me a todo app" or "Build me a dashboard to track my steps," the analysis shows:
+
+1. Writing a frontend webapp requires the same boilerplate HTML/React each time
+2. An `assets/hello-world/` template containing the boilerplate HTML/React project files would be helpful to store in the skill
+
+Example: When building a `big-query` skill to handle queries like "How many users have logged in today?" the analysis shows:
+
+1. Querying BigQuery requires re-discovering the table schemas and relationships each time
+2. A `references/schema.md` file documenting the table schemas would be helpful to store in the skill
+
+To establish the skill's contents, analyze each concrete example to create a list of the reusable resources to include: scripts, references, and assets.
+
+### Step 3: Initializing the Skill in Workspace
+
+**Important:** Always create and edit skills in the workspace folder first, never directly in `config/skills/`. This ensures atomic deployment and prevents partial/broken skills from being loaded.
+
+Create a new skill directory in the workspace:
+
+```bash
+mkdir -p workspace/skills/<skill-name>
+```
+
+Then create the SKILL.md with proper frontmatter:
+
+```markdown
+---
+name: <skill-name>
+description: <clear description of what the skill does and when to use it>
+---
+
+# <Skill Name>
+
+<instructions>
+```
+
+Create subdirectories as needed:
+
+```bash
+mkdir -p workspace/skills/<skill-name>/scripts
+mkdir -p workspace/skills/<skill-name>/references
+mkdir -p workspace/skills/<skill-name>/assets
+```
+
+### Step 4: Edit the Skill
+
+When editing a skill, remember that it is being created for another instance of Daycare to use. Include information that would be beneficial and non-obvious to Daycare. Consider what procedural knowledge, domain-specific details, or reusable assets would help another Daycare instance execute these tasks more effectively.
+
+**Editing an existing skill:** Copy the skill from `config/skills/<skill-name>` to `workspace/skills/<skill-name>` first, make edits in the workspace copy, then deploy back.
+
+```bash
+# Copy to workspace for editing
+cp -r config/skills/<skill-name> workspace/skills/
+
+# ... make edits ...
+
+# Deploy back (see Step 5)
+```
+
+#### Learn Proven Design Patterns
+
+Consult these helpful guides based on your skill's needs:
+
+- **Multi-step processes**: See references/workflows.md for sequential workflows and conditional logic
+- **Specific output formats or quality standards**: See references/output-patterns.md for template and example patterns
+
+These files contain established best practices for effective skill design.
+
+#### Start with Reusable Skill Contents
+
+To begin implementation, start with the reusable resources identified above: `scripts/`, `references/`, and `assets/` files. Note that this step may require user input. For example, when implementing a `brand-guidelines` skill, the user may need to provide brand assets or templates to store in `assets/`, or documentation to store in `references/`.
+
+Added scripts must be tested by actually running them to ensure there are no bugs and that the output matches what is expected. If there are many similar scripts, only a representative sample needs to be tested to ensure confidence that they all work while balancing time to completion.
+
+Any example files and directories not needed for the skill should be deleted.
+
+#### Update SKILL.md
+
+**Writing Guidelines:** Always use imperative/infinitive form.
+
+##### Frontmatter
+
+Write the YAML frontmatter with `name` and `description`:
+
+- `name`: The skill name
+- `description`: This is the primary triggering mechanism for your skill, and helps Daycare understand when to use the skill.
+  - Include both what the Skill does and specific triggers/contexts for when to use it.
+  - Include all "when to use" information here - Not in the body. The body is only loaded after triggering, so "When to Use This Skill" sections in the body are not helpful to Daycare.
+  - Example description for a `docx` skill: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. Use when Daycare needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks"
+
+Do not include any other fields in YAML frontmatter.
+
+##### Body
+
+Write instructions for using the skill and its bundled resources.
+
+### Step 5: Deploy the Skill
+
+Once the skill is ready in the workspace, deploy it atomically to `config/skills/`:
+
+```bash
+# Remove existing skill (if updating)
+rm -rf config/skills/<skill-name>
+
+# Copy from workspace to config
+cp -r workspace/skills/<skill-name> config/skills/
+```
+
+This atomic operation ensures:
+- The skill is never in a partial/broken state in config
+- Other agents don't see incomplete changes
+- Easy rollback by keeping the workspace copy
+
+After deployment, optionally clean up the workspace copy:
+
+```bash
+rm -rf workspace/skills/<skill-name>
+```
+
+### Step 6: Iterate
+
+After testing the skill, users may request improvements. Often this happens right after using the skill, with fresh context of how the skill performed.
+
+**Iteration workflow:**
+
+1. Copy skill back to workspace: `cp -r config/skills/<skill-name> workspace/skills/`
+2. Make changes in workspace
+3. Test the changes
+4. Deploy atomically: `rm -rf config/skills/<skill-name> && cp -r workspace/skills/<skill-name> config/skills/`
+5. Repeat as needed

package/dist/skills/skills/skill-creator/references/output-patterns.md

@@ -0,0 +1,82 @@
+# Output Patterns
+
+Use these patterns when skills need to produce consistent, high-quality output.
+
+## Template Pattern
+
+Provide templates for output format. Match the level of strictness to your needs.
+
+**For strict requirements (like API responses or data formats):**
+
+```markdown
+## Report structure
+
+ALWAYS use this exact template structure:
+
+# [Analysis Title]
+
+## Executive summary
+[One-paragraph overview of key findings]
+
+## Key findings
+- Finding 1 with supporting data
+- Finding 2 with supporting data
+- Finding 3 with supporting data
+
+## Recommendations
+1. Specific actionable recommendation
+2. Specific actionable recommendation
+```
+
+**For flexible guidance (when adaptation is useful):**
+
+```markdown
+## Report structure
+
+Here is a sensible default format, but use your best judgment:
+
+# [Analysis Title]
+
+## Executive summary
+[Overview]
+
+## Key findings
+[Adapt sections based on what you discover]
+
+## Recommendations
+[Tailor to the specific context]
+
+Adjust sections as needed for the specific analysis type.
+```
+
+## Examples Pattern
+
+For skills where output quality depends on seeing examples, provide input/output pairs:
+
+```markdown
+## Commit message format
+
+Generate commit messages following these examples:
+
+**Example 1:**
+Input: Added user authentication with JWT tokens
+Output:
+```
+feat(auth): implement JWT-based authentication
+
+Add login endpoint and token validation middleware
+```
+
+**Example 2:**
+Input: Fixed bug where dates displayed incorrectly in reports
+Output:
+```
+fix(reports): correct date formatting in timezone conversion
+
+Use UTC timestamps consistently across report generation
+```
+
+Follow this style: type(scope): brief description, then detailed explanation.
+```
+
+Examples help Claude understand the desired style and level of detail more clearly than descriptions alone.

package/dist/skills/skills/skill-creator/references/workflows.md

@@ -0,0 +1,28 @@
+# Workflow Patterns
+
+## Sequential Workflows
+
+For complex tasks, break operations into clear, sequential steps. It is often helpful to give Claude an overview of the process towards the beginning of SKILL.md:
+
+```markdown
+Filling a PDF form involves these steps:
+
+1. Analyze the form (run analyze_form.py)
+2. Create field mapping (edit fields.json)
+3. Validate mapping (run validate_fields.py)
+4. Fill the form (run fill_form.py)
+5. Verify output (run verify_output.py)
+```
+
+## Conditional Workflows
+
+For tasks with branching logic, guide Claude through decision points:
+
+```markdown
+1. Determine the modification type:
+   **Creating new content?** → Follow "Creation workflow" below
+   **Editing existing content?** → Follow "Editing workflow" below
+
+2. Creation workflow: [steps]
+3. Editing workflow: [steps]
+```