methodology-explainer
/methodology-explainer
Explain analysis methodology to diverse audiences. Use when documenting 'how we did this' sections, building trust through transparency, or teaching analytical approaches to stakeholders.
- Author
- nimrodfisher ↗
- Repository
- data-analytics-skills ↗
- Licence
- MIT
- Last repository change
- 25.09.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Explain analysis methodology to diverse audiences. Use when documenting 'how we did this' sections, building trust through transparency, or teaching analytical approaches to stakeholders.
Triggers from the description
Original author description
Explain analysis methodology to diverse audiences. Use when documenting 'how we did this' sections, building trust through transparency, or teaching analytical approaches to stakeholders.
How it works
SKILL.md has no level-two headings · 26 lines, 224 words
SKILL.md preview
--- name: methodology-explainer description: Explain analysis methodology to diverse audiences. Use when documenting 'how we did this' sections, building trust through transparency, or teaching analytical approaches to stakeholders. --- # When to use Any time you deliver findings that require the audience to trust the method — A/B tests, attribution models, forecasts, statistical analyses, or anything where "how did you get that?" is a likely question. Write the methodology section before distributing results, not after questions arrive. # Process 1. **Identify the audience tier** — use `references/audience_depth_guide.md` to determine the appropriate level: executive (why/what), business analyst (what/how at high level), or technical peer (full detail). 2. **Select the explanation pattern** — use `references/methodology_explanation_patterns.md` to pick the structure: narrative, layered (short summary + appendix), or Q&A format. 3. **Draft the core explanation** — cover: what question was asked, what data was used, what method was applied, what assumptions were made, and what the key limitation is. 4. **Apply plain-language rewrites** — replace statistical terms with business equivalents per the translation table in `references/methodology_explanation_patterns.md`. 5. **Add a limitations paragraph** — every methodology explanation must include at least one honest limitation and what it means for the conclusions. 6. **Produce deliverables** — write-up using `assets/methodology_writeup_template.md`; if the methodology will be presented, use `assets/methodology_slide_template.md`. # Inputs the skill needs - Description of the analytical method used (technique, data, steps) - Audience type (executive / business / technical) - Any assumptions or known limitations # Output - Plain-language methodology write-up - Limitations section - Completed `methodology_writeup_template.md` or `methodology_slide_template.md`
Files in this package (5)
- SKILL.md 2 KB
- assets/methodology_slide_template.md 2 KB
- assets/methodology_writeup_template.md 1 KB
- references/audience_depth_guide.md 3 KB
- references/methodology_explanation_patterns.md 4 KB
Versions
The database has no other skills named methodology-explainer.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version eb41fd473005 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90stakeholder-requirements-gathering
Structured requirements elicitation for analysis requests. Use when scoping new analysis projects, clarifying ambiguous business questions, or documenting analysis acceptance criteria with stakeholders.