Connected evidence for selected Checks
Require only the storefront URL. GitHub, Shopify and Google Analytics are optional integrations declared in the entrypoint's glue-review-setup. Individual analytics-backed Checks may require specific source evidence; missing access blocks those decisions, not the whole audit. The operating contract owns permitted sources, privacy and read-only boundaries.
Connection setup outside evaluation
Explain the missing source, target and decision it would support, then offer its supported connection flow or continuing without it. An explicit connection request already authorizes starting that flow; do not ask again. Never request passwords, keys or tokens in chat.
Present one question per missing integration
Ask about one useful missing source at a time, with its verified status and two choices. For a verified, available and permitted Composio fallback outside Glue:
You don’t have access to Google Analytics.
- Use Composio for Google Analytics
- Continue without Google Analytics
Substitute the relevant integration/status, such as “Your Shopify connection needs to be reconnected.” With only a native host flow, offer “Connect Google Analytics” or “Reconnect Shopify” and “Continue without …”. Never offer unavailable/prohibited Composio or combine integrations, connection methods and exports in one question.
Request another source only for a specific unresolved decision. Shopify or GA4 alone may supply the funnel; Search Console is optional for requested acquisition context. Analytics are optional for the audit. If the user declines or has not answered, continue independent work and retain dependent gaps. Explain consequences briefly in progress/results; do not repeat declined requests or treat silence as consent.
Choose the connection flow
In Glue, use its connection/setup flow exclusively and resume when the host supplies access. Never invoke Composio CLI or bypass guarded evaluation with CLI, proxies or browser automation.
Outside Glue, prefer the host connector/UI. An execution-capable host may use already available, permitted Composio as a fallback. Check command -v composio and composio link --help; install nothing and create no auth configuration during evaluation. Confirm the toolkit: github, shopify, google_analytics, or google_search_console only for Funnel.
After authorization:
composio link <toolkit>
If the host cannot open a browser, use composio link <toolkit> --no-browser --no-wait and show only the provider-returned authorization URL. Keep this temporary URL out of reports, repos and evidence. The user completes sign-in/consent and reviews actual scopes; never approve for them or claim the grant is read-only because this skill only reads.
Have the user select among multiple accounts using account/alias controls; preserve other connections. Verify completion through supported status/list operations (composio link <toolkit> --list when available), then bind the intended repo/store/property before business reads. Discover read schemas and select accounts explicitly; do not probe ambient identity or use business mutations.
Missing tools, failed linking, declined consent or absent responses leave only dependent decisions blocked. Retain completed evidence; do not loop on authorization, substitute accounts or weaken host guards.
Bind the source and query
Start from the configured storefront and supplied repository/property identity, never an ambient account. Verify GitHub repository/revision, Shopify permanent or primary domain, or GA4 property/web-stream URI against that target before reading business data. Record documented market/domain redirects and cross-domain setup. If binding is ambiguous, stop only the affected read.
Discover current permitted read schemas. Use GitHub source/history, Shopify catalog/configuration or safe aggregates, and GA4 metadata/aggregate reports only for the selected Checks. Do not consume Search Console, ads, CRM, sales, session replay or other undeclared integrations. Search Console remains optional acquisition context in $report-shopify-funnel when separately requested.
Record query/report provenance, reporting timezone, currency, freshness, consent/filter coverage, dimensions, windows, segments and denominators needed to interpret the evidence. Missing, thresholded, sampled or delayed data is unavailable, not zero. Keep each numerator and denominator within one source and definition; Shopify and GA4 may legitimately differ. Query the smallest safe aggregate scope and avoid identifiable rows.
For landing outcomes, confirm that the source exposes actual eligible sessions and compatible session outcomes for that route. Traffic-only acquisition reports, page views, generic key-event counts and product-catalog access do not establish purchase-session conversion or analytics-report access. Preserve pagination, truncation and incomplete row coverage rather than claiming store-wide ranking.
Default comparison windows
Unless the user supplies a more appropriate business period, use 28 complete days ending yesterday and the immediately preceding 28 complete days, in the selected source's reporting timezone. Add a weekday-aligned year-over-year comparison only when useful for seasonality. Record promotions, stock, price, market, tracking, consent, theme or outage changes that impair comparability; disclose sparse or incomplete periods.
Use the evidence
The selected Check owns source requirements and event-integrity tests; funnel investigation and landing comparison coordinate shared collection. Reuse compatible supplied $report-shopify-funnel and $report-shopify-performance evidence without requiring those skills or adding their report catalogs. Analytics alone cannot prove a UX cause.
Record availability in the Check context ledger. Missing supporting evidence is a material gap when relevant; missing required decision evidence blocks only the owning Checks.