Choose an app, event keys, and reporting period to organise the analytics returned by your instance.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Read session and selected event analytics for the same period.
/oo Countly: For Countly app [app ID], read session analytics and events [event key list] over the past seven days. Compare the returned metrics and explain the relationship between recorded sessions and those events.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect a Countly API key and instance root URL.
Connect Countly →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
This connection reads Countly app details, dashboard analytics, session analytics, and event analytics.
Read app context and recorded analytics.
Retrieve the Countly user associated with the connected API key.
Leina 
Wanta 
countly.get_current_user List Countly applications owned by the connected user.
countly.list_apps Retrieve Countly application metadata and its user access lists.
countly.get_app_details Retrieve Countly dashboard analytics for an application.
countly.get_dashboard_analytics Retrieve session analytics data points for a Countly application and period.
countly.list_session_analytics Retrieve event analytics for one or more Countly event keys.
countly.list_event_analytics No matching tools.
Yes. Choose the past seven days, the past thirty days, the current month, or a specific start and end time.
The event query accepts a segmentation key when that key is present in the app’s event data.
Yes. Provide the root URL of your Countly Flex, private cloud, or self-hosted instance.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.