Eva Creator Routing Entry

Problem

In creator work, drafting, Brief breakdown, pre-publish review, retrospection, learning, and custom Link integration often arrive in one ambiguous request. Writing immediately can skip constraints or treat rough ideas as finished drafts. Eva-skill acts as a routing entry point, separating the request into project information, dynamic navigation, or a concrete business task.

How It Works

• Route first, then execute: it determines whether the user is asking about licensing or origin, asking for the next step, or entering eva-brief, eva-create, eva-preflight, eva-review, or eva-think.
• Load the source on demand: after routing to a business entry, it reads the corresponding module.md and continues the same-turn gate and execution; project information reads only the relevant README section.
• Separate workflows: commercial work starts with Brief; short videos and long-form articles go to Create; pre-publish checks go to Preflight; published content goes to Review; vague thinking goes to Think.

Boundaries

It does not directly write generic Moments, Weibo, or Xiaohongshu posts, nor does it call external search or platform APIs to find benchmarks. Legal, medical, financial, and tax questions receive only general principle structuring, not professional advice.