cli

Manage a Solid Imager instance and server interactions via CLI commands.

Updated Sep 21, 2025
One-click install
npx skills add https://github.com/hmjn023/solid-imager --skill cli-hmjn023
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli
Source: https://github.com/hmjn023/solid-imager/tree/main/.opencode/skills/cli
Command: npx skills add https://github.com/hmjn023/solid-imager --skill cli-hmjn023

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a command-line interface to manage a Solid Imager instance and its server interactions, enabling repeatable operations without a GUI.

Core Features & Use Cases

  • Deterministic CLI commands defined under apps/cli/src/commands/ for interacting with the server.
  • Remote management and metadata operations via oRPC, AI tagging triggers, and data workflows.

Quick Start

Run bun run --filter @solid-imager/cli dev --help to see available commands.

Frequently Asked Questions about cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage a Solid Imager instance from the command line?

You can manage a Solid Imager instance from the command line by running deterministic CLI commands defined under apps/cli/src/commands, which handle server interactions and data workflows without needing a GUI.

How does oRPC-based communication work for remote metadata operations?

oRPC-based communication enables remote management and metadata operations by facilitating deterministic CLI workflows that query data and trigger AI tagging across local and remote server sources.

Can I trigger AI tagging and data workflows without a graphical interface?

Yes, you can trigger AI tagging and execute data workflows without a graphical interface by executing specific command-line instructions that interact directly with the Solid Imager server via oRPC.

Do I need the incur library to run Solid Imager CLI commands?

Yes, the incur library is a required dependency for running the Solid Imager CLI, as the deterministic CLI workflow relies on it to execute commands and manage server interactions.

What is the best way to start automating Solid Imager server interactions via CLI?

The best way to start automating server interactions is by running bun run --filter @solid-imager/cli dev --help, which lists available commands for metadata operations and remote management.

Why use a CLI workflow instead of a GUI for Solid Imager management?

Using a CLI workflow instead of a GUI provides repeatable, deterministic operations for managing server interactions, querying metadata, and triggering data workflows without manual graphical intervention.