Summary Line Chart

線ひとつ、文ひとつ、ノイズなし。

AIがチャートエディターになります。乱れた時系列を、結論自体を述べるすっきりした折れ線グラフひとつに変え、転換点に注釈を付け、それ以外をすべて取り除きます。

こんな方におすすめ

自ら説明するチャートがひとつ必要なアナリスト、創業者、ライターの皆さま

所要時間

~25分

レベル

初心者向け

3ステップでインストール

登録不要。CLIツールも不要です。お使いのAIを選んで、1行コピーして貼るだけです。

Pro — 全511件のスキル

ご自分で入れたい場合は、スキルを購入（$4.99）し、購入完了画面からZIPをダウンロードして、上のディレクトリに展開し、AIのセッションを再起動してください。結果は同じです。すでに購入済みの場合は、AIアシスタントにダウンロードしてもらうこともできます。

パックの内容

SKILL.md（手順書）1点とスターターテンプレート1点が入っています。プレビューはこちらです：

Summary Line Chart

When to use

A report, deck, or post needs one chart that a reader can understand in five seconds without you standing next to it
A time series has a story — growth, a drop, a recovery — but the raw chart buries it under gridlines, legends, and noise
You're summarizing weekly or monthly numbers for people who don't read charts for a living
A dashboard export shows everything and therefore communicates nothing; you need the one-line version
You're comparing two periods and want the chart itself to say which way things moved and by how much

Workflow

Find the one sentence (input: raw time series + context → output: chart headline)
Before touching any chart tool, write the sentence the chart must prove: "Sign-ups doubled after the March launch, then held steady." If you can't write that sentence, you don't have a chart yet — you have data to explore. The headline decides the time range, the annotations, and what gets cut. A chart without a sentence is decoration; a chart with one is an argument.
Clean the series (input: raw data → output: chart-ready series)
Pick one metric, one time range, and one granularity — daily noise becomes weekly totals, hourly spikes become daily averages. Fix gaps honestly: a missing week is a break in the line or a labelled gap, never a silently interpolated slope. Drop secondary series that don't serve the headline; if a second line is essential, it earns its place by changing the conclusion, not by adding context.
Draw the line (input: chart-ready series → output: bare chart)
One line, one color, minimal chrome: a light baseline, value labels only at the start, end, and turning points, no legend (the headline names the metric), no gridlines beyond the baseline. The line itself should carry the story — if the reader needs the axis labels to know whether things went up or down, the chart has failed at its one job.
Annotate the turning points (input: bare chart → output: annotated chart)
Mark at most three events on the line — the moments that explain the shape: launch, outage, price change, campaign. Each annotation is a date plus ≤6 words, placed so it never covers the line. Everything else is trivia for the appendix. If you can't name three events, mark fewer; an unannotated honest chart beats a chart decorated with guesses about why the line moved.
Check the takeaway (input: annotated chart → output: publish-ready chart)
Show the chart to someone who hasn't seen the data and ask one question: "What happened?" If their answer matches your headline sentence, ship it. If they hedge, squint, or answer a different question, the headline, the range, or the annotations are wrong — fix the chart, not the reader. Export at a size that stays sharp in its real home (slide, doc, or feed), and keep the source data linked so the number can be re-checked.