Skip to content
cccskills
FreePublished on GitHub

insight-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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (4)

  • SKILL.md2.8 KB
  • assets/insight_brief_template.md1.5 KB
  • references/insight_framework.md3.4 KB
  • references/prioritization_guide.md2.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Insight Synthesis

When to use

  • An analysis has produced many statistics but no clear "so what"
  • The team has findings but is struggling to prioritise which ones to act on
  • Stakeholders are asking "what does this mean for us?" rather than "what did you find?"
  • Multiple analyses need to be synthesised into a unified set of recommendations
  • Preparing an insight briefing for a team that doesn't have time to review the full analysis

Process

  1. List all findings — enumerate every statistically meaningful finding: trends, comparisons, correlations, anomalies, surprises. Write each as a factual statement. Don't interpret yet.
  2. Apply So What → Why → Now What to each finding — convert each fact into an insight by answering: So what (why does this matter to the business?), Why (what is the most likely explanation?), Now what (what specific action should follow?). See references/insight_framework.md.
  3. Quantify business impact — for each insight, estimate the financial, customer, or operational magnitude. An insight without a number is an observation. Use order-of-magnitude estimates if precise data is not available.
  4. Prioritise by impact × confidence × actionability — score each insight on these three dimensions (1–3 scale). Insights that score high on all three are the ones to lead with. Deprioritise insights that are high-impact but low-confidence until validated.
  5. Group and resolve conflicts — cluster related insights and check for contradictions. If two findings point in opposite directions, document the tension and state what additional data would resolve it.
  6. Produce the insight brief — present the top 3–5 insights in priority order, each with the finding, So What / Why / Now What, business impact, and confidence level. Use assets/insight_brief_template.md.

Inputs the skill needs

  • All analysis findings (statistics, charts, model outputs, anomalies)
  • Business context: current goals, OKRs, strategic priorities
  • Audience who will act on the insights (role and decision authority)
  • Confidence levels for the findings (based on sample size, method, data quality)
  • Known constraints on action (budget, timeline, team capacity)

Output

  • references/insight_framework.md — So What / Why / Now What pattern, insight quality rubric, prioritisation matrix
  • references/prioritization_guide.md — scoring insights by impact, confidence, and actionability; how to present trade-offs
  • assets/insight_brief_template.md — structured brief: top insights in priority order, each with impact, explanation, recommendation, and confidence level

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Rigorous A/B test statistical analysis. Use when analyzing experiment results, calculating statistical significance, checking for sample ratio mismatch, or validating test design before launch.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills488Updated Sep 25, 2026

Track and document analytical assumptions and decisions. Use when making analytical choices, documenting trade-offs, ensuring transparency, or creating audit trails for analytical work.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills488Updated Sep 25, 2026

Structured, reproducible analysis documentation. Use when documenting analysis findings, creating analysis notebooks, ensuring reproducibility, or building analysis archives for future reference.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills488Updated Sep 25, 2026

Structure analysis approach before starting work. Use when receiving new analysis requests, breaking down complex questions into steps, or planning iterative analysis workflows.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills488Updated Sep 25, 2026

Pre-delivery quality assurance for analysis work. Use when reviewing analysis before sharing with stakeholders, checking for completeness, validating assumptions, or ensuring clarity of recommendations.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills488Updated Sep 25, 2026

Post-analysis learning and process improvement. Use when completing major analysis projects, documenting lessons learned, or improving team analytical practices.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills488Updated Sep 25, 2026

See all skills by nimrodfisher

Report a problem with this skill