본문으로 건너뛰기
cccskills
무료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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(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(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

nimrodfisher/data-analytics-skills4822026년 9월 25일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

nimrodfisher/data-analytics-skills4822026년 9월 25일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

nimrodfisher/data-analytics-skills4822026년 9월 25일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

nimrodfisher/data-analytics-skills4822026년 9월 25일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

nimrodfisher/data-analytics-skills4822026년 9월 25일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

nimrodfisher/data-analytics-skills4822026년 9월 25일 업데이트

nimrodfisher의 스킬 모두 보기

이 스킬의 문제 신고