User Context

This skill is the Data Analytics plugin's source-routing, semantic-layer registry, setup, and onboarding layer. It loads explicit future source-routing choices, semantic-layer pointers, onboarding progress, and reusable setup obligations for Data Analytics workflows. It does not act as general Data Analytics memory.

Mandatory Pre-Answer Gate

• For ordinary Data Analytics preflight, use scripts/data_analytics_preflight.py as the default state-read path when local shell access is available.
• Apply the same gate on behalf of other Data Analytics skills that call data-analytics:user-context as part of their own mandatory preflight before answering, searching connectors, retrieving evidence, creating artifacts, or drafting output.
• When running the preflight script through a command tool, set the tool's max_output_tokens to at least 25000 so the complete payload remains visible as the registry grows. If the tool output is truncated, warn the user that Data Analytics could not load all source-routing preferences and semantic-layer registry entries in one pass, then rerun with a higher cap and do not use the payload until the complete output is visible.
• Treat the script payload as satisfying the read requirement only when it reports read status for $CODEX_HOME/state/plugins/{marketplace_id}/{plugin_id}/user-context.md and renders the compact context it will use in context.user_context, context.source_preferences, context.source_category_config, context.connector_confirmation, context.connector_setup_summary, context.semantic_layers, context.hero_prompt_candidates, context.primary_hero_prompt, context.extra_hero_prompt_candidates, and control.
• Do not treat listing files, checking that files exist, or saying they should be read as sufficient; source-routing preferences, semantic-layer pointers, source category mapping, and onboarding obligations must be loaded and applied.
• If the script fails, cannot render the compact Data Analytics context the workflow will use, local shell access is unavailable, or the request is direct context maintenance, actually read the relevant state files manually before answering or writing.
• If the user-context file is absent or unavailable, follow references/onboarding.md for first-run behavior.
• Read $CODEX_HOME/state/plugins/{marketplace_id}/{plugin_id}/onboarding-state.json only when onboarding state, semantic-layer refresh setup, hero prompt progress, or progressive nudges are relevant.

Skill Configuration

Audience And Language