daily-routine

Routes daily automation requests to briefing, cron maintenance, or health audit skills.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill daily-routine-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-routine
Source: https://github.com/yakeworld/Synthos/tree/main/skills/private/core/daily-routine
Command: npx skills add https://github.com/yakeworld/Synthos --skill daily-routine-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Daily automation requests (intelligence briefings, cron maintenance, system health checks) often arrive at a single entry point, and this Skill prevents logic duplication by acting as a pure routing gate that directs each request to the correct specialized skill instead of implementing automation itself. ## Core Features & Use Cases - Request Routing: Classifies incoming routine requests and redirects them to one of three whitelisted targets: research/daily-intelligence-briefing, devops/cron-system-maintenance, or devops/project-health-audit. - Boundary Enforcement: Refuses to execute automation logic inline; unmatched requests trigger a clarification prompt rather than a guessed execution. - Golden Test Suite: Ships weighted test cases (critical/high) verifying correct routing decisions and detecting REDIRECT boundary violations. - Use Case: A user asks to "generate today's arXiv/PubMed briefing"; the Skill returns a routing decision to research/daily-intelligence-briefing and loads it via skill_view without producing any execution result itself. ## Quick Start Ask the assistant to route your daily automation request, such as generating today's arXiv intelligence briefing or checking cron task health, and it will redirect you to the correct specialized skill.

Frequently Asked Questions about daily-routine

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

FAQPage Schema
How do I route daily automation requests to the right skill?

Submit a routine_request describing your need, and the Skill returns a routing decision to one of three whitelisted targets: daily-intelligence-briefing, cron-system-maintenance, or project-health-audit. It loads the target via skill_view without executing any automation itself.

What happens when a request does not match any routing target?

Unmatched requests receive a clarification prompt asking the user to state their intent explicitly. The Skill never guesses or executes unmatched requests, following rule DAIL-005.

Can this skill generate the daily intelligence briefing directly?

No. It is a pure redirect entry point and produces no execution results. Briefing generation is delegated to research/daily-intelligence-briefing, which handles arXiv, HN, and PubMed collection.

What are the limitations of a redirect-only routing skill?

It only supports three fixed targets and cannot handle requests outside that whitelist. Any new automation domain requires adding a new target skill rather than extending this entry point with implementation logic.

How is routing correctness tested?

A golden test suite with weighted cases (critical and high) verifies routing outputs, null execution results, and boundary violations. Passing requires a weighted score of at least 0.80 with all critical checks green.