daycare-intake-router

Classifies inbound teacher messages and routes them to daycare workflows or ProviderConsole escalation.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/carlosmsanchezm/daycare-agent --skill daycare-intake-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daycare-intake-router
Source: https://github.com/carlosmsanchezm/daycare-agent/tree/main/workspaces/teacher-ops/skills/daycare_intake_router
Command: npx skills add https://github.com/carlosmsanchezm/daycare-agent --skill daycare-intake-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teachers send messages that require routing to the correct daycare workflow. This skill automates classification and directing intents to the proper sub-skills or human review when needed.

Core Features & Use Cases

  • Classification: Automatically identify the interaction type of each inbound teacher message.
  • Routing: Dispatch to the correct workflow skill (e.g., teacher_clarifications, printing_requests, activity_submission_prescreen).
  • Escalation: Draft or escalate to ProviderConsole for Tier 2 cases in ambiguous scenarios.

Quick Start

Provide an inbound teacher message to be classified and routed to the appropriate workflow or escalation path.

Frequently Asked Questions about daycare-intake-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route teacher messages to the correct daycare workflow?

Routing teacher messages involves classifying the sender, interaction type, and entities to direct messages to workflows like teacher clarifications or activity submissions. This skill automates that dispatch process and escalates ambiguous cases.

How does teacher message classification work for daycare interactions?

Classification reads inbound messages to identify the sender and extract key entities. It determines the interaction type, such as material requests or check-ins, emitting a boundary event with type, tier, and entities for workflow dispatch.

Can I use Python to classify and route daycare check-ins and material requests?

Yes, this Python-based classifier reads inbound teacher messages and uses daycarectl commands to handle routing. It supports common interactions including material requests, activity submissions, check-ins, and clarifications.

What is the best way to handle ambiguous teacher messages requiring provider approval?

Ambiguous teacher messages are handled through Tier 2 escalation to ProviderConsole for provider approval. Tier 1 auto-routing manages standard interactions, while unclear scenarios are escalated for human review.

When should I escalate a teacher message instead of using auto-routing?

Escalation to ProviderConsole is required for Tier 2 cases when scenarios are ambiguous. Standard interactions like clarifications and check-ins are handled by Tier 1 auto-routing, ensuring only complex messages require manual review.

Does daycare message routing require specific workflow dependencies for activity submissions?

Daycare message routing dispatches to existing workflow skills like activity_submission_prescreen and printing_requests. It acts as a router without strict dependencies, classifying messages and directing them to the appropriate sub-skill.