agentleFS
rakaarwakyrakaarwaky/agents-arwaky/skills/content-creation/vision-arwaky/SKILL.md

vision-arwaky

Skill0 starsChanged 5 days agoMITView on GitHub

Unified image and video intelligence for computer vision, OCR, video analysis, object tracking, and MCP integrations.

  • Reads credentials
  • Installs packages

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    XDG layout: Keep machine-specific paths and credentials out of version control: ~/.config/vision-arwaky/config.yaml ($XDG_CONFIG_HOME), …

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Vision Arwaky

You drive Vision Arwaky, a Python computer-vision toolkit exposed through a CLI (va / vision-arwaky-cli), an MCP server (vision-arwaky-mcp), and a TUI config interface (vision-arwaky-tui).

Global Rules

  • Entry points. va (or vision-arwaky-cli) runs every command; vision-arwaky-mcp starts the MCP server over stdio; vision-arwaky-tui starts the TUI config interface. During development use uv run <command> when the project is managed by uv.
  • MCP tools. The MCP server exposes six tools: vision_init, vision_execute, vision_list_commands, vision_help, vision_status, vision_cancel. The entry point is modules/root_mcp_entry.py, and the action surface is modules/mcp/src/surface_mcp_action.py. Command details: internal/vision-arwaky/modules/mcp/FRD.md.
  • External VLM backend. analyze and analyze-video use a configured external OpenAI-compatible vision endpoint and fall back to deterministic processing when no LLM response is available. Supported config:

    backend: external
    external:
      url: "http://localhost:8080/v1"
      model: "llava"

    The repo does not bundle a model; set credentials via LLAMA_API_KEY or ~/.config/vision-arwaky/config.yaml; never commit an API key.

  • System deps. tesseract for OCR; ffmpeg + ffprobe for video; headless OpenCV runtime for image and video. Install on Debian/Ubuntu: sudo apt-get install -y ffmpeg libgl1 tesseract-ocr.
  • XDG layout. Keep machine-specific paths and credentials out of version control: ~/.config/vision-arwaky/config.yaml ($XDG_CONFIG_HOME), ~/.local/share/vision-arwaky (data & venv), ~/.cache/vision-arwaky (cache), ~/.local/state/vision-arwaky (logs & state), ~/.local/bin (executables). Use LLAMA_API_URL, LLAMA_API_KEY, and LLAMA_MODEL for env overrides.
  • Documentation levels. The vision-arwaky repository carries three documentation tiers — PRD.md (product problem, goals, scope, metrics, risks), per-feature FRD.md files (shared/system/image/video/cli/mcp), and README.md (install, commands, config, testing, contribution).
  • Current limitations. VLM analysis needs a reachable external vision endpoint. OCR needs the tesseract binary. Video needs ffmpeg. Object tracking uses OpenCV trackers, not a deep-learning detector. Smart-video analysis samples a bounded representative set of frames rather than sending every frame to the VLM.
  • Completion. The requested command returned the expected JSON or file; for VLM commands the external endpoint was reachable (or the deterministic fallback produced the expected output).

Routing

StepReferencePurpose
CLI (workspace)run va init [target_dir] — initialize workspace (XDG symlinks + .agents/skills/vision-arwaky/SKILL.md).init
CLI (image)analyze --image PATH [--prompt TEXT], ocr --image PATH [--lang CODE], compare --image1 P1 --image2 P2Image analysis, OCR, screenshot diff.
CLI (video)video-info, extract-frames, check-corruption, detect-scenes, detect-motion, track --bbox X,Y,W,H, analyze-videoVideo metadata, frame extraction, integrity, scene/motion events, object tracking, smart-video VLM summary.
Smart videoscene-change + motion + uniform sampling; caps frames at 12; bounded summary prompt; per-frame VLM fallback; removes temp frames.Owned by analyze-video.
Documentation mapinternal/vision-arwaky/ — PRD.md, README.md, and modules/{shared,system,image,video,cli,mcp}/FRD.md.Full product, install, and FRD-level specs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.