sec_filing_question_answer_skill

SEC Filing Question Answer Skill

Data dependencies and execution prerequisites

It is recommended to use Wind wind-mcp-skill to obtain underlying data. Before execution, first check whether wind-mcp-skillis already available locally; if not, prompt the user to install it:

# 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 provide precise answers to specific questions in regulatory filings, focusing on answering "what exactly the filing says, which passage is most relevant, what the direct conclusion is, what is explicitly stated, and what is merely a reasonable inference." The output focus is not to write a summary of the entire filing, but to provide a traceable, verifiable, and clearly bounded answer to the user's question.

Execution workflow

Step 1: Clarify the question, subject, and filing scope

First confirm what the user actually wants to ask, and lock down the corresponding company, filing type, and time range. Prioritize determining:

• Whether the question concerns business, risks, accounting treatment, governance structure, or capital arrangements
• Whether what needs to be reviewed is an annual report, quarterly report, prospectus, announcement attachment, or other formal document
• Whether the user needs a one-sentence answer or a complete explanation with background

If the scope of the question is too broad, it should first be narrowed to a clear, answerable question.

Step 2: Locate the filing passage most relevant to the question

Based on the user's question, prioritize locating the sections most likely to contain the answer, such as:

• Business overview, risk factors, management discussion and analysis
• Financial notes, accounting policies, customer concentration, contract liabilities
• Equity structure, lock-up periods, related-party transactions, litigation or regulatory matters

Do not browse the entire filing evenly; instead, search for the most relevant parts in a question-oriented manner.

Step 3: Distinguish direct answers from supporting evidence

After finding the relevant content, first determine whether there is an explicit statement:

• If the filing directly answers the question, the direct conclusion should be given first
• If the filing provides only partial facts, a limited inference should be made based on them
• If the filing does not contain enough information, it should be clearly stated that it cannot be confirmed from the current filing

Any inference must be based on specific information in the filing, and speculation must not be written as fact.

Step 4: Supplement necessary context

The text in regulatory filings is often highly legalized or accounting-oriented. To help users truly understand it, key content should be translated into research language:

• What this statement means commercially
• What the impact is on operations, finances, or shareholder interests
• How it corresponds to issues the market usually cares about
• Which details are easily misread

Step 5: Indicate boundaries and matters still to be confirmed

If uncertainty remains regarding the question, it is necessary to clearly point out:

• The parts not covered by the current filing
• Points that can only be confirmed by combining other filings or subsequent announcements
• What conservative conclusion can currently be drawn

Step 6: Integrate into a precise Q&A final draft

The final output should directly answer the user's question, without showing a large retrieval process or rewriting the entire filing into a summary.

Output structure

---

{Stock name} Regulatory Filing Q&A ({YYYY-MM-DD})

I. Question

{User question}

II. Direct answer

{First answer the question directly in 2-4 sentences, clearly defining the boundaries of the conclusion.}

III. Key Points of Basis

• Basis 1:{corresponding content and significance}
• Basis 2:{corresponding content and significance}
• Basis 3:{corresponding content and significance}

IV. How to Understand It

• {business or financial interpretation 1}
• {business or financial interpretation 2}

V. Parts Still to Be Confirmed

• {uncovered point 1}
• {uncovered point 2}

---

Quality Requirements

1. It must answer around the user's question and must not turn the Q&A into a summary of the entire document.
2. Give the direct answer first, then add the basis and explanation, so that readers do not have to search for the conclusion in a long text.
3. Strictly distinguish between what is explicitly stated in the document and inferences made based on the document.
4. Information not covered by the document must be clearly stated and must not be made up.
5. The output should help users locate key clauses and research implications more quickly, rather than stopping at a legalistic restatement of the original text.