论文测试
- 作者仓库星标 8,497
- 作者更新于 实时读取
- 作者仓库 blog
- 领域
- 写作
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @digoal · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- Windows
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: finance-weekly-outlook
description: Generate a source-backed weekly financial trading outlook from daily-finance, finance-core-analy…
category: 写作
runtime: 无特殊运行时
---
# finance-weekly-outlook 输出预览
## PART A: 任务判断
- 适用问题:文章、文案、发言稿、润色或结构化表达。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Overview / Required Inputs / Mandatory External Data Step”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于文章、文案、发言稿、润色或结构化表达,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Overview / Required Inputs / Mandatory External Data Step”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件。
先用一个小任务确认它会围绕“Overview / Required Inputs / Mandatory External Data Step”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: finance-weekly-outlook
description: Generate a source-backed weekly financial trading outlook from daily-finance, finance-core-analy…
category: 写作
source: digoal/blog
---
# finance-weekly-outlook
## 什么时候使用
- 把写作方向的常用动作沉淀成 Agent 可调用的技能 适合处理文章、文案、润色、翻译、总结和结构化表达,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤;通常…
- 面向文章、文案、发言稿、润色或结构化表达,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Overview / Required Inputs / Mandatory External Data Step」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "finance-weekly-outlook" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Overview / Required Inputs / Mandatory External Data Step
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Finance Weekly Outlook
Overview
Generate a Markdown weekly outlook that identifies high-probability bullish and bearish industries and stocks for the next trading week, covering both US equities and China A-shares. The report must combine upstream finance articles, fresh authoritative data, market-behavior validation, expectation-gap reasoning, scenario falsification, and explicit trading action plans.
This skill is downstream of:
daily-finance -> finance-core-analysis -> finance-explosive-article -> finance-weekly-outlook
It can also run independently when upstream files are absent, but never invent missing data.
Required Inputs
Prefer the newest available files in the current project's markdown/ directory:
markdown/daily-finance-YYYY-MM-DD.mdmarkdown/finance-core-analysis-YYYY-MM-DD.mdmarkdown/finance-explosive-article-YYYY-MM-DD.md
If multiple dates exist, use the most recent trading-relevant date unless the user specifies a date. Preserve upstream facts and sources, but re-check any number used in the final thesis.
Resolve the forecast window explicitly:
- For US markets, use the next US trading week.
- For A-shares, use the next China trading week.
- If holidays make the US and China windows different, show both date ranges in the header.
- If the user asks for "next week" during an active session, use the next full trading week unless they ask for the remaining days of the current week.
If upstream files are absent, run independently with fresh data and state 上游文件:未使用 in the report metadata.
Mandatory External Data Step
Always access current external data before writing a current weekly outlook. Use primary/authoritative sources where possible:
- Official: central banks, statistics agencies, exchanges, regulators, listed-company filings, investor relations, earnings releases
- Market data: exchange pages, ETF/fund issuer data, CBOE/FRED/Treasury/Nasdaq/NYSE, HKEX, SSE/SZSE, CSRC/PBOC, Wind/Eastmoney/同花顺 only when official data is unavailable
- News: Reuters, Bloomberg, FT, WSJ, 财新, 第一财经, 财经, 21世纪经济报道, 经济观察报
Read references/data-checklist.md when planning the data pull. Read references/tradingagents-method.md when structuring the reasoning and risk review.
Do not rely on self-media, unverified social posts, headlines without source traceability, or a single isolated stock example to support an industry conclusion.
Current data must be no older than the latest completed trading session unless a source publishes less frequently. Label stale indicators and avoid using them as decisive evidence.
Workflow
1. Build the Fact Base
Extract upstream facts from daily/core/explosive articles, then add fresh data:
- Macro liquidity: Fed/PBOC signal, US 10Y, China 10Y, DXY, SHIBOR/DR007, Treasury/TGA or Fed balance-sheet context when relevant
- Risk appetite: VIX, put/call, market breadth, new highs/new lows, major index trend
- Capital flow: US sector ETF flow when available, A-share northbound/southbound if available, margin financing, main-board/STAR/ChiNext turnover structure
- Sector behavior: weekly relative strength vs S&P 500 and CSI 300, volume confirmation, support/resistance, breakout/failure
- Expectations and crowding: earnings revisions, revenue/EPS consensus direction, valuation percentile if available, fund positioning/crowdedness proxies
- Catalysts: earnings calendar, macro data calendar, policy events, product/order/legal/regulatory events
Tag data clearly:
【实】confirmed actual data【预】market expectation or consensus【估】model/analyst estimate【待】reported but not independently verified; avoid using as core evidence
Produce an internal evidence matrix before selecting sectors:
| Market | Constraint | Indicator | Latest value/status | Source | Decision impact |
|---|---|---|---|---|---|
| US | Rates/liquidity/risk | e.g. 10Y, DXY, VIX | value + date | source | supports/weakens/neutral |
| China A | Liquidity/policy/breadth | e.g. DR007, turnover, margin | value + date | source | supports/weakens/neutral |
2. Decide Macro Positioning
State whether next week should be 偏进攻, 中性偏进攻, 中性偏防守, or 偏防守.
Use this chain:
宏观约束 -> 资金行为 -> 风格偏好 -> 仓位上限 -> 证伪信号
Do not say "risk appetite improves" without naming the observable variable that improved.
Positioning must include:
- Gross exposure ceiling, expressed as a range, not a false precision point.
- Conditions for increasing exposure.
- Conditions for cutting exposure.
- One correlated-risk warning if several trades depend on the same macro factor.
3. Select Bullish and Bearish Industries
Cover both US equities and A-shares. Output at least:
- 2-4 bullish industries across the two markets
- 2-4 bearish industries across the two markets
- At least one bullish and one bearish view for each market unless data quality makes this unsafe; if so, explain why
For each industry, require:
- Industry-level evidence, not only a single stock move
- Market-behavior validation: price, volume, relative strength, breadth, or fund flow
- Catalyst and expectation-gap judgment
- Assumptions and what changes if assumptions fail
- Crowding/overpricing risk check
Avoid hindsight logic:
- Do not mark a current hot theme bullish merely because it is hot.
- Do not mark a falling industry bearish merely because it fell.
- Ask: "what is not yet priced for the coming week?"
Use confidence labels:
高: thesis has macro support, industry confirmation, catalyst, and clear invalidation.中: thesis has 2-3 supports but one important uncertainty.低: watchlist only; do not force a trading plan.
4. Select Stocks and Trading Plans
For each market, provide a small number of stock calls. Prefer quality over quantity:
- US equities: 2-4 stocks total, including bullish and bearish/avoid candidates
- A-shares: 2-4 stocks total, including bullish and bearish/avoid candidates
Each stock must include:
- Name, ticker/code, market
- Direction: buy/add/hold/reduce/sell/avoid/watch
- Thesis with 2-4 evidence points
- Three-factor score: earnings expectation, valuation/sentiment, liquidity/risk premium
- Expectation-gap quadrant:
- Good news + high expectation = risk of "priced in"
- Good news + low expectation = bullish catalyst
- Bad news + high expectation = bearish shock
- Bad news + low expectation = possible exhaustion/reversal
- Concrete action plan:
- Entry trigger or buy zone
- Staged position sizing
- Stop-loss or invalidation level
- Take-profit or reduction plan
- Hold/sell/buy decision for existing positions
- Daily tracking indicators and action timetable
If precise price levels are unavailable from reliable data, use technical conditions instead of fabricated numbers, such as "daily close above prior 20-day high with volume above 20-day average".
Trading action rules:
- Do not give a
buy/add/sellaction unless entry, invalidation, sizing, and review date are all present. - Use
watch/avoid/holdwhen data quality is insufficient or the setup lacks confirmation. - Position sizing must be bounded by thesis confidence and correlated exposure; avoid all-in or certainty language.
- For existing positions, distinguish
持有观察,减仓, and止损退出conditions.
5. Run TradingAgents-Style Internal Review
Before finalizing, simulate these roles in writing or internally:
- Fundamental analyst: earnings, balance sheet, valuation, guidance
- News/policy analyst: catalysts, official data, regulatory and geopolitical events
- Technical/market analyst: trend, volume, breadth, support/resistance
- Bull researcher: best case and upside path
- Bear researcher: strongest counterargument and downside path
- Trader: translate thesis into action rules
- Risk manager: position sizing, invalidation, drawdown, correlated exposures
Use structured findings rather than long dialogue. The final article should show the result of the debate through assumptions, alternatives, and risk controls.
For each final stock call, include the review result in compact form:
多头证据 / 空头反驳 / 最终处理 / 证伪信号
6. Validate Before Saving
Check:
- Every major number has a source.
- Dates, units, direction, actual vs expected, intraday vs close are correct.
- US and A-share coverage is explicit.
- Bullish and bearish views are both present.
- Industry calls have industry-level evidence.
- Stock calls include clear trading actions, not vague "关注".
- Each key thesis has assumptions and falsification signals.
- The report includes charts/tables/Mermaid diagrams.
- The article ends with a disclaimer.
If a claim cannot be verified, weaken it, label it, or remove it.
Legal and suitability boundary:
- Write actions as scenario-based public-information plans, not personalized advice.
- Do not imply guaranteed returns, target certainty, or suitability for all investors.
- Keep the disclaimer, but do not use it to justify unsupported precision.
Output Structure
Save the final Markdown to:
markdown/finance-weekly-outlook-YYYY-MM-DD.md
Use the report date, create markdown/ if needed, and write UTF-8.
Required structure:
# 未来一周中美股多空展望|YYYY-MM-DD 至 YYYY-MM-DD
> 执行摘要:...
## 一、结论先行:下周仓位与主线
Include: forecast window, report date, upstream files used, macro positioning, gross exposure ceiling, top bullish/bearish themes.
## 二、数据仪表盘
Include tables and at least one Mermaid diagram showing:
触发变量 -> 数据验证 -> 预期差 -> 交易计划 -> 证伪信号
## 三、行业多空矩阵
## 四、美股个股操盘计划
## 五、A股个股操盘计划
## 六、情景推演:前提、备选观点、证伪信号
## 七、下周关键日历与跟踪清单
## 八、数据来源
## 免责声明
本文仅供参考,不构成投资建议。市场有风险,投资需谨慎。文中观点基于公开信息、特定前提假设和当时可得数据,未来可能因宏观政策、流动性、财报、监管、地缘政治和市场情绪变化而失效。任何买入、卖出、持有或仓位安排都不应被视为个性化投资建议,投资者应结合自身风险承受能力独立决策。
Writing Rules
- Write in Chinese unless the user requests another language.
- Be direct, structured, and source-backed.
- Use "不是A,而是B" only when it exposes a real mechanism mismatch.
- Do not overstate probability; use "基准情景/备选情景/尾部风险" instead of false certainty.
- Give explicit actions for individual stocks, but keep the disclaimer and assumption boundaries clear.
- Prefer concise tables over long prose where decisions need comparison.
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核