Skill 詳細
finance-explainer
Creates personal-finance educational articles rather than helping manage finances directly.
使用前に確認
自動レビューは関連性のみを確認し、安全性や推奨を保証しません。使用前に出典の説明を読んでください。
SKILL.md
これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。
---
name: finance-explainer
version: 1.0.0
description: >-
Turn the depth of the planfi financial toolset into ONE long-form "noob → seasoned expert" blog
post by fanning out a workflow of agents that research, distill, architect a table of contents, and
write. Runs in two modes: a BROAD whole-of-personal-finance guide, or a DEEP single-topic deep dive
(e.g. "529 college investing", "Roth conversions", "rent vs buy"). Invoke when someone says "write a
beginner-to-expert personal finance guide", "distill all the planfi tools into a blog post", "write
a deep-dive post on <topic>", "explain <topic> from scratch to mastery", "run finance explainer on
529 investing", or wants a single cohesive long-read that takes a complete beginner to confident.
Produces a finished markdown article.
---
# Finance Explainer — distill the toolset into a noob→expert guide
A content-generation skill. It fans out a **Workflow** of agents over the planfi tool catalog to
write **one long-form blog post** that walks a complete beginner all the way to near-expert. The
planfi engine/MCP is the source of truth for the *depth*; the agents translate that depth into
plain-English teaching prose. The output is a finished markdown article — it does **not** change any
user data and invents no figures (illustrative examples only; the real math stays in planfi).
It runs in **two modes**, auto-selected by whether you pass a `topic`:
- **BROAD** (no `topic`) — one post spanning the whole personal-finance journey across all ~11 domain
clusters (the showcase guide).
- **DEEP** (`topic` set) — a focused deep dive on ONE topic (e.g. "529 college investing"). A scoping
agent reads the catalog, picks the tools relevant to that topic, and derives the sub-angle clusters;
the SAME distill → architect → write → edit pipeline then produces a tightly-scoped article. This is
the reusable mode for per-topic content flows.
This skill is the user's explicit opt-in to multi-agent orchestration — run the workflow; don't try
to write the whole guide solo in the main loop.
## When to use vs. not
- **Use (broad)** for a single cohesive long-read that teaches personal finance start-to-mastery, or
to showcase the breadth of planfi's ~94 tools as an educational narrative.
- **Use (deep)** when the user names a topic — "write a post on 529 investing", "deep dive on Roth
conversions", "explain rent vs buy from scratch to mastery". Pass it as `topic`.
- **Don't use** for analyzing a specific person's plan (that's `comprehensive-plan` /
`financial-forecast`) or for a short LinkedIn post (that's the `linkedin-finance-marketer` agent).
## Step 0 — Confirm scope (ask only if the user left it open)
Optional inputs — all have defaults, so you can run cold:
- **topic** — set this for a DEEP single-topic deep dive (e.g. `"529 college investing"`). Omit for a
BROAD whole-of-personal-finance guide. If the user named a subject, pass it here.
- **title** — the post title (defaults sensibly per mode).
- **audience** — who it's for (default: "a smart, motivated beginner who knows almost nothing").
- **focus** — narrow the angle further (default: the whole journey, or "master `<topic>`" in deep mode).
- **out** — where to save the finished markdown (default: `drafts/finance-explainer-guide.md`).
If the user named a topic/title/audience/angle, pass it through; otherwise take the defaults and proceed.
## Progress updates (Discord)
Keep the user updated in Discord, the same way Feature Factory does. Read the webhook URL from your
memory/config (the `discord-webhook` reference) — **never hardcode it**. The workflow runs in the
background, so post at the checkpoints the main loop controls, via
`curl -H 'Content-Type: application/json' -d '{"content":"..."}' <webhook>`:
- **Kickoff** — when you launch the workflow (mode + topic/title, e.g. "🚀 Finance Explainer: deep dive on Roth conversions started").
- **Done** — after Step 2 saves the article: title, mode, chapter count, GitHub で全文を読む (外部ページ)