Ferrisgrid install

Skill BrunoV21/FerrisGrid-CLI/.agents/skills/ferrisgrid-install

Turn screens into coordinates, and coordinates into action.

Install

npx -y skills add BrunoV21/FerrisGrid-CLI --skill ferrisgrid-install

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Install and verify the published FerrisGrid CLI from crates.io. Use when setting up FerrisGrid, checking prerequisites, installing the ferrisgrid command, or confirming screen/input permissions.

SKILL.md

2.3 KB, as published. Nobody here has run it

FerrisGrid Install

Use this when a machine needs the normal published FerrisGrid CLI. Only use a local checkout when the user explicitly asks for source development.

Steps

Check Rust is available and whether ferrisgrid is already on PATH:

cargo --version
which ferrisgrid

If Rust is missing, tell the user Rust/Cargo must be installed before the published CLI can be installed.

Install or update the published CLI from crates.io. The crates.io package name is ferrisgrid-cli; it installs the executable named ferrisgrid:

cargo install ferrisgrid-cli

If this fails with DNS, crates.io index, or other network-related errors in a sandboxed agent environment, retry the same command with the normal escalation flow because cargo install needs network access.

Confirm the installed binary is available and responds:

which ferrisgrid
ferrisgrid help

Do not use ferrisgrid --version as the verification command unless the CLI has added that command; older releases report it as an unknown command.

Run diagnostics:

ferrisgrid doctor

On macOS, doctor can exit successfully while reporting native capture problems such as CoreGraphics returned no displays and screens: 0. Treat that as an environment or permission issue, not an install failure, if ferrisgrid help and the fake backend smoke test work.

Smoke-test capture without touching the real desktop:

ferrisgrid observe --backend fake

This verifies the CLI protocol and output writing path even when native desktop capture is unavailable.

Development from source

Use these commands only inside a local FerrisGrid checkout when modifying the project:

cargo build -p ferrisgrid-cli
cargo test --workspace
cargo run -q -p ferrisgrid-cli -- doctor

Notes

On macOS, real capture needs Screen Recording permission.
On macOS, real capture may also require running from a logged-in desktop session.
Real actions need Accessibility permission.
Default output is .ferrisgrid/.
Use --backend fake only for protocol smoke tests; normal usage should use the native backend.