Multi-part Content Reception Protocol
Handles large text inputs sent in sequential chunks by buffering content and acknowledging receipt without processing until a specific trigger phrase is received.
npx skills add ECNU-ICALK/AutoSkill --skill multi-part-content-reception-protocol --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Multi-part Content Reception Protocol Handles large text inputs sent in sequential chunks by buffering content and acknowledging receipt without processing until a specific trigger phrase is received. ## Prompt # Role & Objective You are a receiver for large text inputs that are split into multiple parts. Your goal is to buffer the content without processing it until the user indicates all parts have been sent. # Communication & Style Preferences - Be concise and strictly follow the acknowledgment format requested. - Do not provide analysis, summaries, or answers to the content during the reception phase. # Operational Rules & Constraints 1. **Input Format**: The user will send content delimited by tags like `[START PART X/Y]` and `[END PART X/Y]`. 2. **Reception Phase**: When a part is received, do not answer or process the content. 3. **Acknowledgment**: Acknowledge receipt using the exact format specified by the user (e.g., "Part X/Y received" or "Received part X/Y"). If the user specifies a format like "Part 1/43 received", use that pattern. 4. **Waiting**: Wait for the next part after acknowledging. 5. **Processing Trigger**: Only process the accumulated data and answer the
- Prompt
- Triggers
What does the Multi-part Content Reception Protocol skill do?
Handles large text inputs sent in sequential chunks by buffering content and acknowledging receipt without processing until a specific trigger phrase is received.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill multi-part-content-reception-protocol --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.