How do I install the Ferrisgrid Install skill?

Run npx skillmds@latest add brunov21/ferrisgrid-install in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ferrisgrid Install safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ferrisgrid Install?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ferrisgrid Install free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ferrisgrid Install?

BrunoV21 (@brunov21) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ferrisgrid Install by brunov21 — Agent Skill

Name: Ferrisgrid Install
Author: BrunoV21

File contents

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.

---name: ferrisgrid-installdescription: 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.---# FerrisGrid InstallUse this when a machine needs the normal published FerrisGrid CLI. Only use a local checkout when the user explicitly asks for source development.## Steps1. Check Rust is available and whether `ferrisgrid` is already on `PATH`:```bashcargo --versionwhich ferrisgrid```If Rust is missing, tell the user Rust/Cargo must be installed before the published CLI can be installed.2. Install or update the published CLI from crates.io. The crates.io package name is `ferrisgrid-cli`; it installs the executable named `ferrisgrid`:```bashcargo 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.3. Confirm the installed binary is available and responds:```bashwhich ferrisgridferrisgrid 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.4. Run diagnostics:```bashferrisgrid 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.5. Smoke-test capture without touching the real desktop:```bashferrisgrid observe --backend fake```This verifies the CLI protocol and output writing path even when native desktop capture is unavailable.## Development from sourceUse these commands only inside a local FerrisGrid checkout when modifying the project:```bashcargo build -p ferrisgrid-clicargo test --workspacecargo 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.

Frequently asked questions

Ferrisgrid Install