agentleFS
ThinkingAIAgenticEngineThinkingAIAgenticEngine/scenario-skills/skills/acquisition/ae-drama-creative-evaluation/SKILL.md

ae-drama-creative-evaluation

Skill6 starsChanged 30 days agoNo licenceView on GitHub

Evaluate and diagnose the placement performance of short-drama ad creatives. Use when short-drama, mini-drama, web novel/comic drama and other content-type customers ask questions such as "how to evaluate creative quality", "which creative is worth scaling up", "why is CTR high but payment poor", "analyze creative tags, channels, audiences, lifecycle, ROAS/LTV", or when they need a creative analysis report based on ThinkingData/ThinkingEngine(AE) data. First verify the feasibility of ad platform data, attribution fields, and in-product events (graded A/B/C/D) via ae-cli, then break down creative, channel, and product conversion issues by attraction efficiency, acquisition efficiency, and value efficiency. Supports IAP, subscription, IAA, and hybrid monetization. Do not use for pure tracking-plan design, placement strategy without AE data, or report/dashboard-only creation without business diagnosis.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.