Cross-Source Queries
One of the most powerful features in Skopx is asking questions that span multiple data sources at once.
What Are Cross-Source Queries?
Instead of switching between Jira, GitHub, Slack, and your database, you can ask a single question that pulls data from all of them. Skopx handles the joins and correlations behind the scenes.
Examples
Engineering productivity:
"For each developer, show me their GitHub PRs merged, Jira tickets completed, and Slack activity this sprint."
Customer health:
"Cross-reference our CRM deals with support tickets. Which accounts have the most open issues?"
Operational overview:
"Combine our database signups with Stripe payment data. How many users who signed up last month actually converted to paid?"
How It Works
- Skopx identifies which sources are needed for your question.
- It queries each source separately with the right query type.
- It correlates the results (matching by email, user ID, project name, etc.).
- You get a unified answer with citations for each source.
Tips
Help Skopx match records. If your tools use different identifiers, mention the common field: "Match GitHub usernames to Jira assignees by email."
Start simple. Try a two-source query first, then add more sources as you get comfortable.
Check citations. Cross-source answers have multiple citations, one per source. Each citation shows the query that was run against that specific tool.
Limitations
- Cross-source queries may take a few extra seconds since multiple services are queried.
- If two sources have no common identifier, Skopx will tell you it cannot correlate the data and suggest alternatives.