メニュー
Translate technical analysis into business language. Use when explaining statistical concepts to non-analysts, simplifying technical findings, or bridging communication between data teams and business stakeholders.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Track and document analytical assumptions and decisions. Use when making analytical choices, documenting trade-offs, ensuring transparency, or creating audit trails for analytical work.
Structured, reproducible analysis documentation. Use when documenting analysis findings, creating analysis notebooks, ensuring reproducibility, or building analysis archives for future reference.
Create standardized metadata for data assets. Use when documenting new datasets, building data catalogs, improving data discoverability, or creating data dictionaries for teams.
Trace and resolve discrepancies when the same metric shows different values in two or more sources. Use before reporting, after pipeline changes, or when stakeholders question a number.
Document column-level mappings between source and target schemas. Use when integrating data from multiple systems, designing ETL transformations, or documenting how raw fields become analytical assets.
Translate SQL queries into plain language business logic. Use when documenting queries, explaining analysis to non-technical stakeholders, code reviewing for correctness, or building a query catalog.
| name | technical-to-business-translator |
| description | Translate technical analysis into business language. Use when explaining statistical concepts to non-analysts, simplifying technical findings, or bridging communication between data teams and business stakeholders. |
When technical output (model results, statistical tests, query findings) needs to be understood by a business audience. Also use to review your own writing before sending — it is easy to slip into jargon without noticing.
scripts/jargon_detector.py on the draft text to flag technical terms that need translation.scripts/readability_scorer.py to get Flesch-Kincaid grade level and sentence complexity metrics; target ≤ grade 10 for executive audiences.references/stakeholder_personas.md to select the persona that best matches your reader; each persona has vocabulary preferences and typical questions.references/translation_pattern_library.md to swap technical language for business equivalents (e.g., "p-value < 0.05" → "we're 95% confident this isn't random chance").references/metaphor_bank.md.assets/translation_template.md to produce the parallel technical/business version; keep the original in an appendix for technical reviewers.translation_template.md)