Stream Processing Windowing Designer
DevelopmentStream Processing Windowing Designer is an Agent Skill for development published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Designs optimal windowing strategies for stream processing
QUICK START
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.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/specializations/data-engineering-analytics/skills/stream-processing-windowing-designer/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/stream-processing-windowing-designer, 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.
Stream Processing Windowing Designer
Overview
Designs optimal windowing strategies for stream processing. This skill provides expertise in window types, watermarks, and trigger strategies for streaming applications.
Capabilities
- Window type selection (tumbling, sliding, session, global)
- Watermark strategy design
- Late data handling
- Trigger configuration
- Window aggregation optimization
- State management recommendations
- Exactly-once semantics configuration
Input Schema
{
"useCase": "string",
"eventTimeField": "string",
"latencyRequirements": {
"maxLatencyMs": "number",
"allowedLateMs": "number"
},
"aggregations": ["object"]
}
Output Schema
{
"windowConfig": {
"type": "string",
"size": "string",
"slide": "string"
},
"watermarkConfig": "object",
"triggerConfig": "object",
"lateDataHandling": "object"
}
Target Processes
- Streaming Pipeline
- Feature Store Setup
Usage Guidelines
- Define use case and event time field
- Specify latency requirements
- List aggregation operations needed
- Consider late data arrival patterns
Best Practices
- Choose window type based on business requirements
- Configure watermarks based on expected lateness
- Use appropriate triggers for latency vs completeness tradeoff
- Plan state management for long windows
- Test with realistic event time distributions