数据分析
- 作者仓库星标 8,497
- 作者更新于 实时读取
- 作者仓库 blog
- 领域
- 写作
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @digoal · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: finance-core-analysis
description: Generate stage-2 publishable deep financial analysis markdown from a daily-finance brief plus cu…
category: 写作
runtime: 无特殊运行时
---
# finance-core-analysis 输出预览
## PART A: 任务判断
- 适用问题:文章、文案、发言稿、润色或结构化表达。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Overview / Input / External data step”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于文章、文案、发言稿、润色或结构化表达,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Overview / Input / External data step”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、执行终端命令、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件、执行终端命令;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件、执行终端命令。
先用一个小任务确认它会围绕“Overview / Input / External data step”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: finance-core-analysis
description: Generate stage-2 publishable deep financial analysis markdown from a daily-finance brief plus cu…
category: 写作
source: digoal/blog
---
# finance-core-analysis
## 什么时候使用
- 用于组织测试、定位失败并形成修复闭环 适合处理文章、文案、润色、翻译、总结和结构化表达,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤;通常不需要额外 AP…
- 面向文章、文案、发言稿、润色或结构化表达,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Overview / Input / External data step」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件、执行终端命令;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "finance-core-analysis" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Overview / Input / External data step
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件、执行终端命令 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Core Financial Analysis
Overview
Generate a deep mechanism analysis from the stage-1 daily finance brief.
This is stage 2 of the daily finance pipeline:
daily-finance → finance-core-analysis → finance-explosive-article
Use the stage-1 file as the factual base, verify/update key data from current external sources, then produce a standalone publishable markdown analysis that can also feed the final 德哥风格爆款文章.
Input
Prefer reading:
markdown/daily-finance-YYYY-MM-DD.md
If the file is not provided:
- Use the newest matching file by filename/date only when the user clearly asks for the latest report; state this assumption in the output metadata
- Ask which report date or file to use when multiple plausible dates exist and "latest" is not implied
- If the user gives raw daily-finance content in chat, use that content
- Do not invent missing facts
Extract a reusable fact table before analysis:
| Field | What to capture |
|---|---|
| Report date | Date used for file naming and source alignment |
| Key facts | 3-5 source-backed facts from daily-finance |
| Numbers | Actual, expected/previous, unit, direction, close/intraday status |
| Sources | Inherited source names/links and any reliability limits |
| Open questions | Facts that require current re-check or must be excluded |
External data step
Always access current external data when producing a current analysis.
Use web search, browser, finance tools, or available MCP tools to:
- Re-check major market prices, yields, exchange rates, commodities, and volatility indicators
- Verify policy statements, macro data, earnings data, and geopolitical facts
- Update stale numbers from the stage-1 brief when newer reliable data exists
- Add only source-verifiable data
Use source hierarchy:
- Primary: official releases, central banks, exchanges, regulators, company filings, Reuters, Bloomberg, FT, WSJ
- Chinese reliable sources: 财新, 第一财经, 财经, 21世纪经济报道, 经济观察报
- Secondary sources require backtracking to original data
Current-data pull should be narrow and decision-relevant. Prioritize:
- Rates: US 10Y/2Y, China 10Y, major central-bank signal
- Liquidity: DXY, CNH, SHIBOR/DR007 or equivalent local liquidity indicator when relevant
- Risk appetite: major equity index, VIX or local volatility/breadth proxy
- Commodities: oil, gold, copper only when linked to the day's thesis
If a value cannot be verified, remove it or mark it as 【待】; never build the core judgment on 【待】.
Core model
Explain market behavior through these variables:
- Liquidity
- Interest rates
- Risk appetite
- Capital flows
- Policy direction
- Balance-sheet pressure
- Incentive constraints
Use first-principles reasoning:
事件 → 约束变化 → 资金行为 → 定价结果 → 风险信号
Analysis rules
- Separate confirmed facts from interpretation
- Reuse source-backed numbers from daily-finance
- Add new data only when it is necessary and source-verifiable
- Mark uncertainty clearly
- Write as a serious publishable 公众号 deep-analysis article; save the strongest viral packaging for finance-explosive-article
- Do not give explicit buy/sell recommendations
- For every major conclusion, name the constraint that changed and the observable signal that would prove it wrong
- Avoid analyzing every lens mechanically; select the 3-5 lenses that actually explain the fact base
Validation checklist
Before final output, check:
- Data correctness: dates, units, directions, actual vs expected, intraday vs close
- Source consistency: important claims have reliable sources
- Logic integrity: each conclusion follows from a mechanism, not from mood words
- Causal chain: event, constraint, capital behavior, pricing result, risk signal
- Counter-case: include what would make the judgment wrong
- Publication readiness: title, subheadings, short paragraphs, clear conclusion
Required structure
1. Title
- Use a clear 公众号-style title
- Prefer tension and mechanism over clickbait
2. Executive judgment
- State the single most important market judgment
- Explain what changed today
- Include one "what would change my mind" sentence
3. Fact base
- Summarize the 3-5 key facts inherited from daily-finance
- Preserve important numbers and source labels
- Add newly verified external data when necessary
- Use a compact table with columns:
标签,事实,数值,来源,状态
4. Mechanism analysis
Analyze through 3-5 lenses as relevant:
- Liquidity
- Interest rates
- Risk appetite
- Capital flows
- Policy
- Balance sheets
For each lens, explain:
- What changed
- Why it matters
- How it transmits into asset prices
- What data would confirm or falsify this lens
5. Core contradiction
Identify the main tension, for example:
- Growth vs inflation
- Policy easing vs currency pressure
- Risk appetite vs earnings pressure
- Liquidity repair vs balance-sheet contraction
6. Scenario deduction
Provide:
- Base case
- Alternative case
- Falsification signal
Each scenario must specify:
- Trigger condition
- Asset-pricing implication
- Observable confirmation signal
7. Key variables to watch
List 3-6 observable indicators for the next update.
8. Non-advisory implication
Explain directional exposure and risk, not ticker calls.
9. Sources
List inherited sources and any new verified sources.
10. Disclaimer
本文仅供参考,不构成投资建议。
File output
If environment allows:
Save to:
markdown/finance-core-analysis-YYYY-MM-DD.md
Rules:
- Use the same report date as the input
daily-financefile - Create directory if missing
- Use UTF-8 encoding
- Output a complete publishable markdown article, not notes
- If write fails → fallback to chat output
Writing style
- Use 公众号-readable structure: strong title, short paragraphs, numbered sections
- Keep the tone sharp but rational
- Explain mechanisms in plain Chinese
- Use contrast where helpful: "不是A,而是B"
- Avoid empty emotional phrases and unexplained jargon
Goal
Produce a reusable deep-analysis document that answers:
- What changed
- Why it changed
- What mechanism connects facts to asset pricing
- What would prove the analysis wrong
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核