Choose a website and scope, then define what matters for prioritization. AI can connect reported issues with affected pages and their capture context.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Read issues and their affected pages to propose priorities grounded in the reported scope.
/oo Conductor: Read Conductor Monitoring issues for website [website ID], scope [whole-site or segment scope value]. Read affected pages for issues [issue identifiers] and prioritize a repair checklist using [criteria], including capture time.
Read a page and website statistics to describe the recorded page context.
/oo Conductor: Read Conductor Monitoring website [website ID], page [URL], and statistics for scope [scope]. Explain the recorded fields for [page review question], preserving data capture times.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect with a Conductor Monitoring Reporting API token.
Connect Conductor →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
Conductor Monitoring reporting data describes captured website statistics, pages, issues, and segments. It supplies the evidence for a scoped website repair checklist.
List websites and segments, read scoped statistics, and list or retrieve pages.
List scoped issues and retrieve the pages affected by a selected issue.
List websites available in the connected Conductor Monitoring account.
Leina 
Wanta 
conductor.list_websites List Conductor Monitoring segments for one website.
conductor.list_segments Retrieve Conductor Monitoring statistics for a whole website or a segment scope.
conductor.get_statistics List pages for a Conductor Monitoring website with pagination.
conductor.list_pages Retrieve data for one URL in a Conductor Monitoring website.
conductor.get_page List Conductor Monitoring issues for a whole website or a segment scope.
conductor.list_issues List pages affected by one Conductor Monitoring issue.
conductor.list_affected_pages No matching tools.
Yes. List the website’s segments and supply the appropriate scope when reading statistics or issues.
Yes. Use the issue identifier to retrieve its affected pages and ask for that relationship in the checklist.
These operations read captured reporting data. Check its capture time and data state rather than assume a new crawl.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.