Best use case
sse is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Server-Sent Events implementation, streaming patterns, and real-time updates.
Teams using sse should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/sse/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How sse Compares
| Feature / Agent | sse | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Server-Sent Events implementation, streaming patterns, and real-time updates.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# SSE Skill
Expert assistance for implementing Server-Sent Events for real-time streaming.
## Capabilities
- Implement SSE endpoints
- Handle streaming responses
- Manage client connections
- Build event-driven updates
- Implement reconnection
## Usage
Invoke this skill when you need to:
- Stream updates to clients
- Implement live feeds
- Build notification systems
- One-way real-time communication
## Implementation
```typescript
// Server
app.get('/events', (req, res) => {
res.setHeader('Content-Type', 'text/event-stream');
res.setHeader('Cache-Control', 'no-cache');
res.setHeader('Connection', 'keep-alive');
const sendEvent = (event: string, data: object) => {
res.write(`event: ${event}\n`);
res.write(`data: ${JSON.stringify(data)}\n\n`);
};
// Send initial data
sendEvent('connected', { timestamp: Date.now() });
// Subscribe to updates
const unsubscribe = eventEmitter.on('update', (data) => {
sendEvent('update', data);
});
req.on('close', () => {
unsubscribe();
});
});
// Client
const eventSource = new EventSource('/events');
eventSource.addEventListener('update', (event) => {
const data = JSON.parse(event.data);
console.log('Update:', data);
});
```
## Best Practices
- Handle reconnection
- Use event types for routing
- Implement keep-alive
- Clean up on disconnect
## Target Processes
- real-time-updates
- live-feeds
- notification-systemsRelated Skills
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.
observe
Observe, inspect, or monitor a Babysitter run.
model
Inspect or change Babysitter model-routing policy by phase.
issue
Run an issue-centric Babysitter workflow.