Result Integrator
Documentsresult-integratorResult Integrator is an Agent Skill for documents published in the GongLingRui/screen-creative-skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Integrate multiple plot point analysis results into comprehensive reports, generating high-quality analysis through deduplication, classification, sorting, and summarization. Suitable for integrating multiple analysis sources, generating unified reports
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/GongLingRui/screen-creative-skills/blob/HEAD/english-version/category/result-processing/result-integrator/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/result-integrator, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Result Integration Tool
Functionality
Integrate multiple plot point analysis results into comprehensive reports, generating high-quality comprehensive analysis through deduplication, classification, sorting, and summarization.
Use Cases
- Integrate plot point results from multiple analysis sources, generate unified comprehensive reports.
- Remove duplicate and redundant information, ensure report conciseness and accuracy.
- Provide structured plot point analysis summary for quick understanding of story core.
- Optimize report logical coherence, improve readability and professionalism.
Integration Principles
- Deduplication: Remove duplicate or similar plot points, ensure each plot point is unique.
- Classification: Classify plot points by dramatic function, provide clear structured view.
- Sorting: Arrange plot points in order of appearance in story, ensure timeline coherence.
- Summarization: Provide overall dramatic structure analysis, give professional insights and recommendations.
Core Steps
Receive multiple analysis results
↓
Identify and remove duplicate content
↓
Classify by dramatic function
↓
Sort by story order
↓
Generate overall analysis summary
↓
Output final comprehensive report
Input Requirements
- Plot Point Analysis Results: Multiple plot point analysis reports or data from different agents.
- Analysis Source Weights (optional): Specify priority or weights of different analysis source results.
Output Format
[Plot Point Integration Analysis Report]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
I. Overall Analysis Summary
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[Overall dramatic structure analysis and professional insights]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
II. Plot Point Analysis
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[Plot Point]: [Description]
[Dramatic Function]: [Analysis]
- [Specifically describe function and impact of this plot point]
[Plot Point]: [Description]
[Dramatic Function]: [Analysis]
- [Specifically describe function and impact of this plot point]
...
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
III. Dramatic Structure Evaluation
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[Professional evaluation and improvement recommendations for integrated dramatic structure]
Constraints
- Ensure all input plot point information is complete and parseable.
- Integration process must maintain objectivity, not introduce new subjective judgments.
- Report content must be logically coherent, easy to read and understand.
- Ensure final output report format is standardized and meets expected requirements.
Examples
See {baseDir}/references/examples.md directory for more detailed examples:
examples.md- Contains detailed report examples of multi-agent plot point analysis result integration, deduplication, classification, sorting, and summarization.
Detailed Documentation
See {baseDir}/references/examples.md for detailed guidance and cases on result integration.
Version History
| Version | Date | Changes |
|---|---|---|
| 2.1.0 | 2026-01-11 | Optimized description field to be more concise and comply with imperative language specifications; added allowed-tools (Read) and model (opus) fields; optimized descriptions of functionality, use cases, integration principles, core steps, input requirements, output format, and integration requirements to comply with imperative language specifications; added constraints, examples, and detailed documentation sections. |
| 2.0.0 | 2026-01-11 | Refactored according to official specifications |
| 1.0.0 | 2026-01-10 | Initial version |