Process screenshots Enzo shares with comments. Save to reference library, extract content, categorize, set reminders, and log patterns. Use when Enzo sends an image with context like \"save this\", shares a screenshot of content (LinkedIn posts, tweets, articles), or sends ideas/f…
Scanned 9/19/2026
Install to Claude Code
npx -y skills add rondoflow/rondoflow --skill process-organize-shared-screenshots --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Process Organize Shared Screenshots?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/rondoflow-process-organize-shared-screenshots)More formats (shields.io, HTML) on the badges page.
---
name: process-organize-shared-screenshots
description: "Process screenshots Enzo shares with comments. Save to reference library, extract content, categorize, set reminders, and log patterns. Use when Enzo sends an image with context like \"save this\", shares a screenshot of content (LinkedIn posts, tweets, articles), or sends ideas/f…"
category: "Media"
author: community
version: "1.0.0"
icon: image
---
# Screenshot Capture
When Enzo shares a screenshot with comments, execute this workflow:
## 1. Save Screenshot
```
cp [inbound image] notes/screenshots/[descriptive-name].jpg
```
Name should reflect content (e.g., `positioning-angles.jpg`, `gpt-ads-hack.jpg`)
## 2. Categorize
Based on Enzo's comment and content, determine category:
| Category | Signals | Destination |
|----------|---------|-------------|
| **Framework** | Actionable mental model, how-to, process | `notes/frameworks.md` under main section |
| **AI Hack** | "AI porn", hackathon material, overpromises but useful | `notes/frameworks.md` under "AI Hacks & Hackathon Ideas" |
| **Idea** | Original thought, "I want to build", future project | `notes/ideas.md` |
## 3. Extract & Store
- Extract key content from screenshot
- Add to appropriate file with:
- Date saved
- Source (if visible)
- Screenshot reference
- Enzo's commentary (if provided)
- Structured summary
## 4. Set Reminder
**Always set a 1-week reminder** unless Enzo specifies otherwise.
Reminder text should prompt action:
- "Have you tested [framework] on anything?"
- "Did you try [hack]?"
- "Any progress on [idea]?"
## 5. Log Pattern
Add observation to `notes/patterns.md`:
```markdown
- [category] [topic]: [brief description] — [intent signal]
```
Intent signals: learn, build, share, remember, reference, hackathon
## 6. Confirm
Reply with:
- What was saved and where
- Reminder date
- Any commentary acknowledged
Keep confirmation brief.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!