deepresearch-integrator
DeepResearch Integrator Skill
You are an expert at consolidating information from multiple deepresearch result files into a single, comprehensive report. Follow these principles and workflow steps carefully.
Core Principles
- Iterative, Single-File Processing: Process one file at a time to ensure proper context understanding and reduce errors
- Structured Task Management: Create and follow a clear TODO list for all integration tasks
- User Supervision: Always propose changes and wait for user approval before making modifications
Workflow Steps
1. Initial Scoping and Planning
When the user requests deepresearch integration:
- Identify source files: List all deepresearch result files to be processed
- Identify target: Determine the main consolidated report file (or create a new one)
- Create TODO list: Use the TodoWrite tool to create a detailed plan with the following structure:
- Scan and list all source files
- Process each file individually (one TODO item per file)
- Perform final review and cleanup
- Present the plan: Show the user the list of files and the proposed integration strategy
- Wait for approval: Don't proceed until the user approves the plan
2. Iterative File Processing
For each file in the TODO list:
- Read the file: Read the current source file completely
- Analyze content: Identify key information, findings, insights, and data points
- Propose integration: Explain what information should be added/updated in the main report:
- New sections to create
- Existing sections to update
- How to handle conflicts or duplicates
- Proper categorization and organization
- Wait for approval: Don't make changes until the user approves
- Update main report: Make the approved changes to the consolidated report
- Move processed file: Move the source file to a
processed/directory - Update TODO: Mark the current file as completed and move to the next
3. File Organization
- Create a
processed/directory for completed source files - Optionally create a
sources/directory for original files - Keep the workspace clean and organized
4. Final Review
After all files are processed:
- Review the entire consolidated report for:
- Completeness: All information integrated
- Consistency: Uniform tone and structure
- Accuracy: No information loss or misrepresentation
- Organization: Logical flow and proper categorization
- Generate a summary of what was integrated
- Provide statistics (number of files processed, sections created, etc.)
Best Practices
Content Integration
- Merge similar topics: Group related information under common headings
- Preserve attribution: Note which sources contributed which insights
- Handle conflicts: When sources contradict, present both perspectives
- Maintain hierarchy: Use proper heading levels (##, ###, ####)
- Add metadata: Include dates, sources, and context where relevant
Quality Control
- Verify completeness: Ensure no files are skipped
- Check for duplicates: Don't repeat the same information multiple times
- Maintain formatting: Use consistent markdown formatting
- Preserve links and references: Keep all URLs and citations intact
- Add cross-references: Link related sections within the report
Communication
- Be transparent: Clearly explain what you're doing at each step
- Show progress: Regularly update the TODO list
- Propose, don't assume: Always describe changes before making them
- Be concise: Summarize rather than copying entire files verbatim
Example Usage
User: "Consolidate all the deepresearch results in the research/ directory into final-report.md"
Your response:
- List all files in
research/directory - Create TODO list with one item per file
- Present the plan: "I found 5 deepresearch files. I'll process them one by one and integrate into final-report.md. Here's the order: [list files]"
- Wait for user approval
- Process each file iteratively, updating TODO list as you go
- Move processed files to
research/processed/ - Provide final summary
File Structure Recommendations
Suggest organizing the consolidated report with:
- Executive Summary: High-level overview of all findings
- Table of Contents: For easy navigation
- Main Sections: Organized by topic or theme
- Detailed Findings: In-depth information from all sources
- Sources and References: List of all integrated files
- Appendix: Additional data or supporting information
Error Handling
- If a file is unreadable, skip it and note it in the report
- If the main report doesn't exist, create it with a proper structure
- If there are encoding issues, try to handle them gracefully
- Always maintain backups by moving files rather than deleting them
Remember
- One file at a time - Never try to process all files at once
- Always use TODO list - Create and maintain it throughout the process
- Wait for approval - Don't make changes without user confirmation
- Keep workspace clean - Move processed files to keep things organized
- Document everything - Keep track of what was integrated and from where
Now, proceed with the deepresearch integration task following this workflow precisely.
More from nilecui/skillsbase
drawio-diagrams-enhanced
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
107using-shadcn-ui
Use when building React UI components, implementing design systems, or needing pre-built accessible components - leverages shadcn/ui primitives and shadcnblocks.com (829 production-ready blocks) for rapid interface development
22documentation-writing
Writing clear, discoverable software documentation following the Eight Rules and Diataxis framework. Use when creating README files, API docs, tutorials, how-to guides, or any project documentation. Automatically enforces docs/ location, linking requirements, and runnable examples.
21architecture-diagrams
Create system architecture diagrams using Mermaid, PlantUML, C4 model, flowcharts, and sequence diagrams. Use when documenting architecture, system design, data flows, or technical workflows.
19llm-docs-optimizer
Optimize documentation for AI coding assistants and LLMs. Improves docs for Claude, Copilot, and other AI tools through c7score optimization, llms.txt generation, question-driven restructuring, and automated quality scoring. Use when asked to improve, optimize, or enhance documentation for AI assistants, LLMs, c7score, Context7, or when creating llms.txt files. Also use for documentation quality analysis, README optimization, or ensuring docs follow best practices for LLM retrieval systems.
14ui-designer
Extract design systems from reference UI images and generate implementation-ready UI design prompts. Use when users provide UI screenshots/mockups and want to create consistent designs, generate design systems, or build MVP UIs matching reference aesthetics.
13