CJA Anomaly → Copy-Paste Annotation Builder
[OVERVIEW]
A saved Coworker skill that turns a Customer Journey Analytics finding into a ready-to-paste annotation. After you run any CJA analysis (e.g. anomaly detection on a daily metric), you say "create an annotation" — or "annotate this" / "make an annotation", optionally naming the finding ("annotate the May 31 drop") — and Coworker returns a formatted table with every field the CJA annotation form needs: Name, Description (with actual vs. expected numbers and % change), Data view + ID, date/range, exact metric and dimension names + component IDs, segments, a suggested color, and whether to apply it to all panels. Because it reuses the exact component names and IDs from the analysis, the values paste straight into CJA without re-lookup. It formats the annotation for manual entry; it doesn't write to CJA via API.
[TRYABLE]
Save this as a personal Coworker skill (Skills settings → create a skill), then:
Run a CJA analysis in Coworker — e.g. "Run anomaly detection on daily occurrences for the last 90 days in [data view]."
When a finding appears, say: "Create an annotation" (or "annotate this" / "make an annotation"). Optionally name the finding, e.g. "annotate the May 31 drop."
Coworker returns a table titled "📝 CJA Annotation — ready to paste" with: Name, Description (actual vs. expected + % change), Data view (+ID), Date/range, Metric(s) (+ID), Dimension(s) (+ID), Segment(s), Color, Apply to all applicable panels.
Copy each value into the CJA annotation form (Components → Annotations).
Skill behavior to configure: trigger on "create an annotation" / "annotate this" / "make an annotation"; honor any named finding; if multiple findings exist and none is named, ask which one; pull all values from the analysis in context and never invent them; use exact metric/dimension names and IDs.
[SETUP]
CX Enterprise Coworker access with CJA connected, a Customer Journey Analytics license, and the ability to save a personal/user skill in Coworker.
[IMPACT]
Removes the manual step of re-finding the right metric, dimension, and data-view details when documenting a finding. Turns "I spotted an anomaly" into a complete, paste-ready annotation in one prompt — roughly a few minutes saved per annotation and consistent, well-described annotations across a team.
[LESSONS]
Add trigger variants ("annotate this", "make an annotation") so you can also pass context about which finding you mean. Pin the output format explicitly (a fixed table) so results are consistent. Keep component names/IDs verbatim from the report — approximations won't match the CJA form. Note the scope limit up front: it builds the fields for manual entry, it does not create annotations through an API.
