Skip to content

florianbonnet14/ThePowerOfAnalytics_ClaudeSkills / analysis-results-collector

analysis-results-collector

Verified

Transform completed analysis work into structured, communication-ready documentation by conducting guided conversations that extract key findings, evidence, and recommendations. Use when a user has completed an analysis (typically following an analysis plan created by the analysis-planner skill) and needs to document results, create findings summaries, build executive reports, or prepare analysis outcomes for stakeholder communication. This skill systematically gathers what was tested, what was found, and what should be done next, then generates a professional markdown document ready for distribution.

assets/analysis_results_template.md

View on GitHub
# Analysis Results: [Problem Title]

**Analysis Plan:** [Link or reference to original plan]
**Analysis Period:** [Start Date] - [End Date]
**Lead Analyst:** [Name]
**Status:** Complete

---

## Executive Summary

### Problem Statement
[Brief restatement of the problem being investigated]

### Key Findings
[3-5 bullet points summarizing the most critical discoveries]

### Primary Root Causes
[Ranked list of validated causes with their contribution to the problem]

### Recommended Actions
[Top 3-5 prioritized recommendations]

---

## Analysis Overview

### Objective
[What question(s) this analysis aimed to answer]

### Scope
[What hypotheses were tested, which tiers reached]

### Timeline
[Actual timeline of analysis phases]

---

## Hypotheses Tested

### Summary Table

| # | Hypothesis | Status | Result | Impact on Decline |
|---|-----------|--------|--------|-------------------|
| H1 | [Hypothesis statement] | Analyzed | Validated/Invalidated | [X%] |
| H2 | [Hypothesis statement] | Analyzed | Validated/Invalidated | [X%] |
| H3 | [Hypothesis statement] | Not Analyzed | N/A | N/A |

---

## Detailed Findings

### [H1: Hypothesis Name] - VALIDATED/INVALIDATED

**Status:** Analyzed
**Result:** Validated/Invalidated
**Confidence Level:** High/Medium/Low
**Impact:** Contributes [X]% to the overall [Y]% decline

#### What We Found
[2-4 paragraphs describing key findings in clear, business-friendly language]

#### Supporting Evidence
- **Data point 1:** [Specific metric or finding]
- **Data point 2:** [Specific metric or finding]
- **Data point 3:** [Specific metric or finding]

#### Analysis Performed
[Brief description of analyses conducted]

#### Why This Matters
[Business implication of this finding]

---

### [H2: Hypothesis Name] - VALIDATED/INVALIDATED

[Same structure as H1]

---

## Hypotheses Not Analyzed

### [H5: Hypothesis Name]
**Reason not analyzed:** [e.g., "Tier 1 hypotheses explained 95% of decline, making further analysis unnecessary"]

---

## Impact Quantification

### Overall Decline Breakdown
- **Total decline in North Star Metric:** [X]%
- **Explained by validated hypotheses:** [Y]%
- **Unexplained variance:** [Z]%

### Contribution by Root Cause
1. **[Root Cause 1]:** [X]% of total decline
2. **[Root Cause 2]:** [Y]% of total decline
3. **[Root Cause 3]:** [Z]% of total decline

---

## Recommendations

### Priority 1: [Recommendation Title]
**Root cause addressed:** [Which hypothesis/finding]
**Expected impact:** [Projected improvement in North Star Metric]
**Effort required:** [High/Medium/Low]
**Timeline:** [Implementation timeframe]

**Action items:**
1. [Specific action]
2. [Specific action]
3. [Specific action]

**Success metrics:**
- [How to measure if this recommendation worked]

---

### Priority 2: [Recommendation Title]
[Same structure as Priority 1]

---

### Priority 3: [Recommendation Title]
[Same structure as Priority 1]

---

## Implementation Roadmap

### Immediate Actions (Week 1-2)
- [ ] [Action item]
- [ ] [Action item]

### Short-term Actions (Weeks 3-4)
- [ ] [Action item]
- [ ] [Action item]

### Medium-term Actions (Months 2-3)
- [ ] [Action item]
- [ ] [Action item]

---

## Appendix

### Methodology
[Brief description of analytical approach used]

### Data Sources
- [List of data sources used]

### Limitations
- [Any caveats or limitations in the analysis]

### Follow-up Questions
- [Unanswered questions that may need future analysis]

---

## Document Control

**Created:** [Date]
**Last Updated:** [Date]
**Version:** 1.0
**Reviewed by:** [Names/Roles]
**Distribution:** [Who should receive this document]
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall