anycap-human-interaction
Collect structured visual feedback from humans using AnyCap's annotation tool, or create and iterate on diagrams using the interactive whiteboard (Excalidraw). Covers image annotation, URL/web page review with screen recording, video review, audio feedback, and collaborative diagramming with Mermaid input. Use when you need a human to point at things, mark regions, draw on screenshots, review a web page or UI, narrate feedback over a recording, provide any spatially-grounded visual input, create or iterate on architecture diagrams, flowcharts, or wireframes. Also use when you need to present work-in-progress to a human for approval or revision. Trigger on: get feedback, show to user, review UI, annotate, mark up, visual feedback, screen recording, user review, human-in-the-loop, approval flow, interactive review, whiteboard, diagram, draw, flowchart, wireframe, or architecture chart.
anycap-ai · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add anycap-ai/anycap --skill anycap-human-interaction技能说明
name: anycap-human-interaction description: "Collect structured visual feedback from humans using AnyCap's annotation tool, or create and iterate on diagrams using the interactive whiteboard (Excalidraw). Covers image annotation, URL/web page review with screen recording, video review, audio feedback, and collaborative diagramming with Mermaid input. Use when you need a human to point at things, mark regions, draw on screenshots, review a web page or UI, narrate feedback over a recording, provide any spatially-grounded visual input, create or iterate on architecture diagrams, flowcharts, or wireframes. Also use when you need to present work-in-progress to a human for approval or revision. Trigger on: get feedback, show to user, review UI, annotate, mark up, visual feedback, screen recording, user review, human-in-the-loop, approval flow, interactive review, whiteboard, diagram, draw, flowchart, wireframe, or architecture chart." metadata: version: 0.6.2 website: https://anycap.ai license: MIT compatibility: Requires anycap CLI binary and internet access. Works with any agent that supports shell commands.
AnyCap Human Interaction
Read this entire file before starting. Skipping sections leads to incorrect workflows -- each media type has different capabilities and constraints.
Workflow guide for collecting structured visual feedback from humans using AnyCap's annotation tool. This skill teaches you when and how to involve humans in your workflow through visual annotation and screen recording.
For CLI command reference, read the anycap-cli skill. For media generation workflows, read the anycap-media-production skill.
Prerequisites
AnyCap CLI must be installed and authenticated. Read the anycap-cli skill if setup is needed.
Two Core Scenarios
AnyCap annotation excels at two distinct review workflows. Choose the one that fits your situation:
| Scenario | Best for | Primary artifact | Highlight |
|---|---|---|---|
| URL / Web Page Review | Web pages, local dev servers, live UIs | Screen recording with narration | Browse, annotate, and narrate -- the recording captures everything |
| Image Collaborative Review | Generated images, screenshots, designs | Annotated image with merged feedback | Multiple reviewers annotate simultaneously in real-time |
Both scenarios support all annotation tools (Rect, Arrow, Point, Freehand) and text labels. The difference is in what you get back and how the review is conducted.
Command Quick Reference
# Blocking -- opens browser, waits for Done click, outputs result
anycap annotate <target> [-o output.png]
# Non-blocking -- starts background server, returns session info
anycap annotate <target> --no-wait [-o output.png]
# Poll for result after human confirms done
anycap annotate poll --session <session_id>
# Stop background server
anycap annotate stop --session <session_id>
# List all active sessions (useful for recovery after context loss)
anycap annotate list
<target> is auto-detected by content: image file, URL (http:// or https://), video file, or audio file.
Key Flags
| Flag | Description |
|---|---|
--no-wait | Non-blocking mode (recommended for agents) |
-o, --output | Save annotated image to this path |
--port <port> | Bind to a fixed port (default: random) |
--bind <addr> | Bind address (default: 127.0.0.1) |
Tip: Use --port with a consistent value (e.g., --port 8888) across sessions. The browser stores each user's display name in localStorage, which is scoped by origin (host + port). A fixed port means returning collaborators are recognized automatically without re-entering their name.
Browser Auto-Open
Both blocking and non-blocking modes automatically attempt to open the annotation URL in the default browser. In headless environments (SSH, container), the CLI prints the URL to stderr instead. No error is raised.
Presenting to the Human -- Guidelines
When presenting an annotation session to the human, adapt your message based on context. Key points to communicate:
- Browser auto-open: On desktop, the page opens automatically -- acknowledge this ("the review page should already be open"). In headless/SSH, share the URL and tell them how to access it.
- Always mention Done: Tell the human to click Done when finished. This is how feedback gets saved.
- Recording for URL mode: Emphasize recording (Rec button) because URL mode cannot export an annotated screenshot. The recording is the primary artifact.
- Multi-user: If multiple reviewers will participate, mention real-time collaboration and that each person can save independently. Exception: URL/iframe mode is single-user (recording is the primary feedback artifact, and multiple users' cursors would make it confusing).
- Headless access: When using
--bind 0.0.0.0, share the URL with the actual host IP. If behind SSH, suggest port forwarding. - What to annotate: Briefly describe what tools are available (Rect, Arrow, Point, Freehand) and that each annotation can have a text label.
Do NOT use canned messages. Compose naturally based on the situation (what you just generated/modified, whether it is desktop or headless, single or multi-reviewer).
Headless / Remote Access
When running in a headless environment (SSH, container, cloud VM), the human cannot access 127.0.0.1 directly. Use --bind and --port to make the annotation server accessible:
# Bind to all interfaces on a fixed port
anycap annotate screenshot.png --no-wait --bind 0.0.0.0 --port 8888
The human can then access the annotation UI via:
- Direct access:
http://<server-ip>:8888(if the port is exposed) - SSH port forward:
ssh -L 8888:localhost:8888 user@host, then openhttp://localhost:8888 - Container port mapping:
docker run -p 8888:8888 ..., then openhttp://localhost:8888 - **Reverse proxy: