# Evals — youtube-api

These are routing and coverage checks for the skill harness, not live API tests. `should_trigger` asserts the skill fires on YouTube transport + ingestion prompts (upload, metadata edit, Analytics pulls, quota/token debugging, "write stats to the wiki"), including the non-obvious 7-day-refresh-token and `uploadLimitExceeded` cases and a Spanish phrasing. `should_not_trigger` asserts an intent-level prompt routes to the named real sibling instead (youtube-strategy / youtube-packaging / youtube-ideation for what-to-make-and-how-to-package, social-publisher for multi-network, remotion-video for rendering, api-connector-builder for generic OAuth wrapping). The single `capability` case is a rubric scored against a generated answer for the weekly-cron scenario. No live YouTube or Google API calls are made — run them through whatever harness loads `cases.yaml`.
