Skip to content

a5c-ai/babysitter / library/specializations/desktop-development/skills/screen-capture-api

screen-capture-api

Verified

Cross-platform screen and window capture for screenshots and recording

FileKindSize
README.mdmarkdown451 B
SKILL.mdskill md1.5 KB
---
name: screen-capture-api
description: Cross-platform screen and window capture for screenshots and recording
allowed-tools: Read, Write, Edit, Bash, Glob, Grep
tags: [screen-capture, screenshots, recording, desktop, media]
graph:
  domains: [domain:software-engineering]
  specializations: [specialization:desktop-development]
  skillAreas: [skill-area:desktop-system-integration, skill-area:desktop-ui-frameworks]
  roles: [role:desktop-developer, role:fullstack-engineer]
  workflows: [workflow:feature-development, workflow:release-management]
---

# screen-capture-api

Implement cross-platform screen and window capture for screenshots and recording capabilities.

## Capabilities

- Capture full screen
- Capture specific windows
- Capture screen regions
- Handle multiple displays
- Stream screen content
- Handle permissions

## Input Schema

```json
{
  "type": "object",
  "properties": {
    "projectPath": { "type": "string" },
    "framework": { "enum": ["electron", "native"] },
    "captureTypes": { "type": "array" }
  },
  "required": ["projectPath"]
}
```

## Electron Example

```javascript
const { desktopCapturer } = require('electron');

async function captureScreen() {
    const sources = await desktopCapturer.getSources({
        types: ['screen'],
        thumbnailSize: { width: 1920, height: 1080 }
    });

    for (const source of sources) {
        const screenshot = source.thumbnail.toPNG();
        // Save or use screenshot
    }
}
```

## Related Skills

- `power-management-monitor`
- `system-services-integration` process
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall