Data dependencies and prerequisites for execution
It is recommended to use Wind wind-mcp-skill to obtain underlying data. Before execution, first check whether there is already a local wind-mcp-skill; if not, prompt the user to install:
# GitHub
npx skills add Wind-Information-Co-Ltd/wind-skills --skill wind-mcp-skill -g -y
# Gitee 镜像(国内)
npx skills add https://gitee.com/wind_info/wind-skills.git --skill wind-mcp-skill -g -y
Skill positioning
This skill is used to organize scattered individual stock research results into a clearly structured research memo that is easy to share and reuse. The output focus is not simply listing materials, but consolidating the five most critical parts: "conclusion, basis, disagreements, risks, and follow-up tracking," so that team members can quickly take over and continue advancing the research.
Execution process
Step 1: Confirm the memo's purpose and depth
First clarify whether this memo is for:
- A phased summary after initial research
- Morning meetings, weekly meetings, or internal sharing
- Establishing a unified draft for subsequent deeper investigation
If the user does not specify, write by default according to the standard of "for the team to quickly understand internally and continue tracking."
Step 2: Distill the core investment conclusion
First compress the conclusion you most want to express into a few clear sentences:
- Why it is worth paying attention to
- Where the current biggest opportunity comes from
- What the current biggest risk is
- At the current stage, is it more suitable to act, observe, or continue researching
The conclusion section should appear before the stacking of materials.
Step 3: Organize the facts and logic supporting the conclusion
Extract the truly important basis around the conclusion, including:
- Business model and core variables
- Operating and financial performance
- Industry and competitive position
- Market expectations and valuation position
Do not stuff all the content found into the memo; keep only the key materials that can support the conclusion.
Step 4: Write the core disagreements clearly
A useful research memo must explain:
- Why the market would agree with this view
- Why the market might disagree
- Which variable is most likely to falsify the conclusion
This step can make the memo truly valuable for discussion, rather than a one-way statement.
Step 5: Complete the risks and tracking checklist
In addition to the conclusion itself, also list:
- The assumptions the current conclusion most depends on
- Events and indicators that need continuous tracking
- Which signals, once they appear, should lead to updating or withdrawing the view
In this way, the memo can be upgraded from a "static summary" to a "dynamic research draft."
Step 6: Organize into a standardized final draft
Finally output in a unified structure to ensure that memos for different individual stocks can be compared horizontally, continuously updated, and reused by the team. The main text presents only the final draft and does not show the internal organizing process.
Output structure
{Stock Name} Research Memo ({YYYY-MM-DD})
I. Conclusion summary
- Current conclusion: {bullish / neutral / cautious / continue observing}
- One-sentence reason: {explanation}
- Most important verification variable: {variable}
II. Company and logic overview
- What the company is doing: {one sentence}
- Current logic worth watching: {one sentence}
- Main point of controversy: {one sentence}
III. Supporting evidence
| Dimension | Key content | Significance for the conclusion |
|---|---|---|
| Business | {description} | {explanation} |
| Financials | {description} | {explanation} |
| Industry/Competition | {description} | {explanation} |
| Valuation | {description} | {explanation} |
IV. Bull-bear divergence
Bull case
- {reason 1}
- {reason 2}
Bear case
- {reason 1}
- {reason 2}
V. Risks and invalidation conditions
- {risk 1}
- {risk 2}
- {conclusion invalidation condition}
VI. Follow-up tracking checklist
- {tracking item 1}
- {tracking item 2}
- {tracking item 3}
VII. Current action recommendation
- Recommended action: {continue tracking / conduct in-depth research / wait for verification / take no action for now}
- Reason: {explanation}
Quality requirements
- The memo must give the conclusion first, then the evidence; the reader must not have to guess the conclusion from a pile of materials.
- All content should serve future reuse and avoid being written as a one-off chat record.
- Bull-bear divergence and risks must not be omitted; otherwise the memo lacks discussion value.
- If there are gaps in data or information, the direction for filling them should be clearly stated in the tracking checklist.
- The text style should be compressed, clear, and transferable, suitable for internal sharing and continuous updating.