context-packager
When to use
Before starting an AI-assisted analysis session when the task requires more than a single prompt — complex investigations, multi-step analyses, or work that depends on project-specific knowledge. A well-packaged context bundle reduces back-and-forth and produces better first responses.
Process
- Identify required context layers — use
references/context_layering_guide.mdto decide which layers are needed: task definition, business context, data schema, prior findings, constraints, and output format. - Collect and deduplicate sources — run
scripts/context_bundler.pyto merge multiple context files into a single structured bundle; it deduplicates and applies the layering order. - Check token budget — run
scripts/token_counter.pyon the bundle to estimate token count; trim lower-priority layers if over budget (seereferences/context_layering_guide.mdfor trimming priority). - Score context quality — evaluate the bundle against
references/context_quality_rubric.md; a good bundle scores ≥ 7/10 on completeness, clarity, and relevance. - Write the prompt header — prepend a clear task statement to the bundle: what you need, what output format you expect, and any hard constraints.
- Save the package — store the bundle using
assets/context_package_template.mdso it can be reused or updated for follow-up sessions.
Inputs the skill needs
- Task description (what you want the AI to do)
- List of context source files or snippets (schema docs, prior reports, business definitions)
- Token budget (default: 100k tokens)
Output
- Merged context bundle (single text file)
- Token count estimate
- Context quality score
- Ready-to-use prompt with task header (
context_package_template.md)
More from nimrodfisher/data-analytics-skills
funnel-analysis
Conversion funnel analysis with drop-off investigation. Use when analyzing multi-step processes, identifying conversion bottlenecks, comparing segments through a funnel, or optimizing user journeys.
37metric-reconciliation
Cross-source metric validation and discrepancy investigation. Use when metrics from different sources don't match, investigating data quality issues between systems, or validating data migration accuracy.
31insight-synthesis
Transform data findings into compelling insights. Use when converting analysis results into actionable insights, connecting findings to business impact, or preparing insights for stakeholder communication.
31dashboard-specification
Design specifications for effective dashboards. Use when planning new dashboards, improving existing ones, or documenting dashboard requirements before development starts.
30data-quality-audit
Comprehensive data quality assessment against business rules, schema constraints, and freshness expectations. Activate when validating data pipeline outputs before production use, auditing a dataset against defined business rules, or producing a quality scorecard for a data asset.
30root-cause-investigation
Systematic investigation of metric changes and anomalies. Use when a metric unexpectedly changes, investigating business metric drops, explaining performance variations, or drilling into aggregated metric drivers.
30