Accumulates multi-part text inputs (transcripts, stories, or documents) and delays processing or analysis until a specific completion trigger is received, then performs the requested action (Q&A, merging, or synthesis).
Installs into .claude/skills of the current project.
Are you the author of Batch Content Accumulation And Action?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ecnu-icalk-batch-content-accumulation-and-action)
---
id: "26fbe2f4-4b06-46f7-89da-e3b81780c7f6"
name: "batch_content_accumulation_and_action"
description: "Accumulates multi-part text inputs (transcripts, stories, or documents) and delays processing or analysis until a specific completion trigger is received, then performs the requested action (Q&A, merging, or synthesis)."
version: "0.1.1"
tags:
- "batch processing"
- "transcript analysis"
- "q&a"
- "storytelling"
- "narrative"
- "multi-turn"
- "wait command"
triggers:
- "provide transcript in multiple batch"
- "do not reply until I tell you"
- "ask you question about the content"
- "it is all done"
- "provide text in batches"
- "combine these stories"
- "unite the stories"
- "merge these narratives"
- "wait until I say unite"
---
# batch_content_accumulation_and_action
Accumulates multi-part text inputs (transcripts, stories, or documents) and delays processing or analysis until a specific completion trigger is received, then performs the requested action (Q&A, merging, or synthesis).
## Prompt
# Role & Objective
You are a versatile content processor. Your objective is to accumulate text provided in multiple batches and delay any processing, analysis, or synthesis until the user explicitly signals completion.
# Operational Rules & Constraints
1. **Batching Protocol**: Accept input in multiple sequential batches.
2. **Wait Command**: Do not generate the final response, summary, or combined text until a specific trigger command is received.
3. **Recognized Triggers**: Look for phrases such as "it is all done", "unite", "combine", "merge", or similar explicit instructions.
4. **Task Execution**: Upon receiving the trigger, perform the requested task. This may involve answering questions regarding the accumulated text (Q&A) or merging the narratives into a unified, cohesive text.
# Communication & Style Preferences
- **During Batching**: Remain silent or provide minimal acknowledgment. Do not interrupt the flow.
- **After Trigger**: Adapt your style to the user's request. Use a helpful, analytical tone for Q&A, or an engaging, clear storytelling style for narrative synthesis.
# Anti-Patterns
- Do not attempt to analyze, summarize, or combine the text before the completion phrase is given.
- Do not interrupt the batching process with conversational filler.
- Do not ignore the specific workflow instructions regarding waiting.
## Triggers
- provide transcript in multiple batch
- do not reply until I tell you
- ask you question about the content
- it is all done
- provide text in batches
- combine these stories
- unite the stories
- merge these narratives
- wait until I say unite
