All skills
nimrodfisher avatar

/insight-synthesis

@fcb0454

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.

Use this Skill: https://skilld.dev/gh/nimrodfisher/data-analytics-skills/insight-synthesis

This session only. Nothing lands on disk.

referencesprioritization_guide.md

≈636 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Prioritization Guide for Analytical Insights

Why prioritization is necessary

An analysis that presents 15 equally-weighted findings makes no decision easier. The analyst's job is to do the cognitive work of prioritization so the audience doesn't have to.


Impact × Confidence matrix

Plot each insight on two axes:

  • Impact: How large is the business effect? (revenue, users, cost, risk)
  • Confidence: How certain are we? (data quality, assumption strength, sample size)
High confidence Low confidence
High impact Priority 1 — act now Priority 2 — validate fast
Low impact Priority 3 — background context Priority 4 — omit

Priority 4 insights should be cut from the deliverable. Including them dilutes the signal.


Urgency overlay

After the impact × confidence sort, apply urgency:

  • Time-sensitive (decision in < 1 week): Surface immediately, even if confidence is medium
  • Strategic (decision in 1–3 months): Can wait for validation
  • Exploratory (no current decision): Document for future reference; do not include in executive outputs

Actionability filter

Before finalising the insight list, filter for actionability:

  • Actionable: The audience can take a specific action that addresses this insight
  • Informational: The audience can use this to calibrate their model but cannot act directly
  • Background: Provides context but changes nothing

Lead with actionable insights. Include informational ones if they affect the credibility of the actionable ones. Cut background-only insights from the main narrative.


Scoring rubric

Quick scoring for prioritization when you have many findings:

Criterion 1 2 3
Revenue / cost impact < $10K $10K–$100K > $100K
Users / customers affected < 1% 1–10% > 10%
Decision urgency Months away Within a month This week
Confidence Low Medium High
Actionability None Indirect Direct

Total score range: 5–15. Prioritise 12–15 first; present 8–11 as supporting; omit 5–7.


Presenting the prioritization logic

Be explicit about what you prioritised and why. "The top three findings account for 85% of the revenue impact" is a justification, not just a claim.

If you cut findings, say so: "We identified seven areas of interest; the three below represent the highest-impact, highest-confidence opportunities."

This builds trust — it signals rigour, not selection bias.

Source: SKILL.md on GitHub

No alerts16d4 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill provides a framework for analytical insight synthesis and includes markdown templates for reporting. It contains no code, network operations, or security risks.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at fcb0454. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 days ago.

Activeupdated 5 months ago

README badge

README badge for nimrodfisher/data-analytics-skills/insight-synthesis