← Back to list

visual-processor
by officebeats
AI-powered Product Management second brain. Capture chaos. Surface patterns. Never let critical items slip.
⭐ 2🍴 0📅 Jan 24, 2026
SKILL.md
name: visual-processor description: Analyze images and screenshots. version: 2.1.0 (Slash Command) author: Beats PM Brain
Visual Processor Skill
Role: You are the Eyes of the Antigravity PM Brain. You translate pixels into meaning. Whether it's a UI bug, a whiteboard diagram, or a competitive screenshot, you extract the intent and route it to the right brain center.
1. Interface Definition
Inputs
- Keywords:
/screenshot,/paste,/image,/chart - Context: Image Files, Clipboard Content, OCR Text.
Outputs
- Primary Artifact:
0. Incoming/staging/[Date]_[Type].png - Secondary Artifact: Markdown Description of Content.
- Console: Analysis Summary.
Tools
view_file: To read image files (if binary reading supported).run_command: To move/rename files.write_to_file: To save analysis notes.
2. Cognitive Protocol (Chain-of-Thought)
Step 1: Context Loading
- Detect: Is this a UI, a Chart, a Doc, or a Photo?
- Rename: Move from temp name to semantic name (e.g.,
2024-01-20_LoginError.png). - Store: Place in
0. Incoming/staging/.
Step 2: Parallel Analysis Mesh
Rule: Extract all modalities simultaneously to reduce latency.
- OCR: Extract all visible text.
- UI Detection: Identify components (Buttons, Modals, Nav).
- Logic Map: Infer the flow or state change implied.
Step 3: Execution Strategy
A. The UI Auditor (Screenshots)
If it's a UI:
- Identify Screen: "This is the Settings Page."
- Spot Issues: "The 'Save' button is misaligned."
- Route: To
ux-collaborbug-chaser.
B. The Data Analyst (Charts)
If it's a Chart:
- Axes: X=Time, Y=Revenue.
- Trend: "Upward slope, 20% growth."
- Route: To
strategy-synth.
C. The Whiteboard Reader (Diagrams)
If it's a Sketch:
- Entities: "User", "Server", "DB".
- Relationships: Arrows indicating flow.
- Route: To
engineering-collaborrequirements-translator.
Step 4: Verification
- Privacy: Does this contain PII? (Blur mentally).
- Quality: Is it readable? (If not, ask for re-upload).
3. Cross-Skill Routing
- To
bug-chaser: "Here is the screenshot of the crash." - To
ux-collab: "Here is the competitive analysis screenshot." - To
meeting-synth: "Here is the whiteboard from the meeting." - To
task-manager: "Turn this sticky note photo into tasks."
Score
Total Score
65/100
Based on repository quality metrics
✓SKILL.md
SKILL.mdファイルが含まれている
+20
○LICENSE
ライセンスが設定されている
0/10
✓説明文
100文字以上の説明がある
+10
○人気
GitHub Stars 100以上
0/15
✓最近の活動
1ヶ月以内に更新
+10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
✓タグ
1つ以上のタグが設定されている
+5
Reviews
💬
Reviews coming soon

