drama-quality-assessment
drama-quality-assessment
CRITICAL - This skill orchestrates a multi-step analysis flow. Execute in the order of
references/steps/; do not skip steps or fabricate data. CRITICAL - Step 01 is a mandatory gate. The analysis target (short drama name) and analysis time range must be explicitly confirmed by the user before data collection begins. Never infer the drama name automatically when it is missing. CRITICAL - Use onlyae-clifor all data operations. Command patterns are inreferences/adapters/ae-cli.md. Do not guess command names, flags, JSON payloads, project_id, event names, or property names. CRITICAL -references/config/event_mapping.yamlis the bridge between business concepts and fields. The standard event/property candidate-name lists live in this file; reuse it to complete the mapping when switching projects (mapping results go to user memory, never written back to this file).
Applicable Scenarios
- Post-launch performance evaluation of a drama
- Locating problematic episodes and their root causes
- Providing data support for content optimization and promotion decisions
- Supports three formats: vertical mini-drama (Douyin/Kuaishou), horizontal short drama (iQiyi/Youku/Tencent), and private-platform drama
Global Conventions
Interaction Checkpoints
The whole flow has two mandatory interaction checkpoints that let the user participate in decisions instead of running through to completion in one go: