zy839971925-zyy/Agent--deep-research-Workflow-Skills / integrations/deepseek-harness/skills/reasoning-workflow
reasoning-workflow
VerifiedDefault silent workflow for everyday questions, research, writing, design and engineering. Match effort to the request, resolve costly ambiguity, find specialist resources and verify the requested outcome. Explicitly selectable with “调用我的 workflow skills”.
references/research-to-report.md
View on GitHub# From a research question to a report
Start with the reader's decision or question, including scope, date and what would change the answer. Allow an orientation search to discover terminology. For the deciding unknown, ask where an observable trace would exist. Search for that trace using entity names, versions, units or identifiers found in sources.
### Search and change course
An official manual establishes intended API behavior. A test on the pinned version can establish observed behavior. A study can support an effect only within its population, comparator and design. A practitioner account can reveal a failure worth testing. Choose accordingly. Open the relevant text, figure, code or release note. Follow secondary coverage to the original when the distinction changes confidence. If the leading account and its strongest rival predict different outcomes, search for the distinguishing observation. A failed search bounds that route; try a different source ecosystem, language or primary identifier when it matters.
For pivotal claims retain a short working note: claim; exact locator and scope; what it supports; lineage; counterevidence or remaining gap. Use the existing task state. For routine facts a direct source suffices. Group syndications and reports using the same dataset. Keep inaccessible sources labeled. Before compression preserve the exact locator of any result that reverses or narrows a conclusion. Reopen it when the summary cannot support the claim.
### Update the answer
When new evidence arrives, identify which premise changes. Recompute affected ranges, confidence or recommendations. Keep stable conclusions intact. Distinguish missing evidence from a negative result. Do not manufacture symmetry between a documented result and an unsupported alternative. If successive searches repeat an origin, try one genuinely discriminating route when available. End when the material decision is stable, or state exactly which unresolved condition can still reverse it.
### Write for use
Select the form by purpose: a direct answer for a bounded fact, a comparison table for matched dimensions, a narrative for a timeline, or a sourced report for a material investigation. Put the answer and its important condition early. Attach sources to the particular claims they support. Expose disagreements in terms of versions, regions, denominators, methods or time periods. Keep extrapolation visible. Preserve unknowns in the final recommendation and give the reader the implication. Inspect any decisive number, quote, attribution or clickable evidence locator before delivery.
For evaluation, use a fixed corpus to diagnose retrieval vs interpretation and a dated live-web run to assess current performance. When a decisive source is supplied directly after a failed search, a correct second answer is a clue about the bottleneck. Benchmark answers and graders must remain outside the working corpus. See [BrowseComp-Plus](https://texttron.github.io/BrowseComp-Plus/) and [ALCE](https://aclanthology.org/2023.emnlp-main.398/) for controlled retrieval and citation evaluation.
### Optional local check for consequential reports
If local text snapshots and a claim packet already exist or materially improve verification, run `python scripts/check_report_evidence.py path/to/packet.json` from the Portable Skill. Store UTF-8 snapshots beside the packet. A source has `id`, `file` and `origin` (same label for copies of one original). A claim has `id`, `text`, `status` and `evidence`; each item names a source, a verbatim quote and a role of `support` or `counter`. Use `unknown` with empty evidence for an open claim. A contested claim needs both roles. The Portable release notes include a complete JSON example. Review the meaning, source identity, dates and scope yourself. Quoted text occurring in a file cannot prove entailment, completeness or independence.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |