Menu
Use after finishing meaningful code changes. Run a deliberate self-check, then ask a fresh reviewer agent to inspect the work before merge.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create and update robust Daycare tasks (task_create/task_update + task_trigger_add) and permanent agents (create_permanent_agent) with minimal Python orchestration, explicit parameter schemas, reproducible exec/process usage, and performance-first skip() behavior. Use when users ask for cron/webhook automation, recurring checks, scheduled reports, permanent agents, or resilient background task workflows.
Create reusable Daycare voice agents with the hidden-by-default `voice_agent_create` tool. Use when users want a new voice persona, a realtime call prompt, client-side voice tools, or a saved voice agent that appears in the app Voice screen.
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.
Understand what Daycare tasks are, how cron and webhook triggers work, and when to use each. Use when users ask about tasks, scheduling, triggers, or want to inspect existing tasks.
Friendship mechanics for daycare agents. Use when the user wants to add friends, manage friend requests, send messages to friends, share or unshare subusers with friends, or understand what nametags are.
Work with user-scoped PostgreSQL databases (PGlite). Use when the user asks to store structured data, create tables, query rows, track records, build a database, or manage any tabular/relational information. Covers database creation, additive schema design, CRUD operations, and SQL queries.
| name | requesting-code-review |
| description | Use after finishing meaningful code changes. Run a deliberate self-check, then ask a fresh reviewer agent to inspect the work before merge. |
Fresh reviewers catch the problems you have already rationalized away.
Before asking another agent to review:
Preferred pattern:
start_background_agent.agent_ask.Use a prompt like this:
Review this implementation for correctness and quality.
Requirements:
- ...
Files changed:
- path/to/file-a.ts
- path/to/file-b.spec.ts
Check:
- correctness against requirements
- edge cases and regressions
- security and permission mistakes
- missing tests
- obvious performance issues
Return findings first, ordered by severity, with file paths and line numbers.
If there are no findings, say so and mention residual risks.
If you disagree with a finding, answer with code-level reasoning, not preference.