openedge-cli
Skill8 starsChanged 5 days agoApache-2.0View on GitHub
Use the openedge-cli installer to install, start, stop, or remove Open Edge Platform (OEP) modules and profiles on an edge system. Trigger on requests like "install OpenVINO", "set up DL Streamer", "run the smart parking sample", "deploy the Metro / Manufacturing / Retail / Robotics AI Suite", "what OEP components can I install", or "uninstall <OEP component>".
In this repository38 other files it gives its agents.
- anomalib-adding-a-datamoduleSkill
- anomalib-adding-a-modelSkill
- anomalib-benchmarkingSkill
- anomalib-tiled-ensembleSkill
- anomalib-trainingSkill
- chatqna-docker-deploySkill
- chatqna-helm-deploySkill
- dlsps-userSkill
- dlstreamer-coding-agentSkill
- getitune-discovering-modelsSkill
- getitune-exporting-a-modelSkill
- getitune-optimizing-a-modelSkill
- getitune-preparing-datasetsSkill
- getitune-running-inferenceSkill
- getitune-training-a-modelSkill
- geti-using-the-pipelineSkill
- manufacturing-ai-app-builderSkill
- manufacturing-app-recipeSkill
- metro-ai-app-builderSkill
- metro-ai-app-recipeSkill
- model-download-userSkill
- multimodal-dataprep-userSkill
- multimodal-embedding-serving-userSkill
- pai-benchmark-policySkill
- pai-configure-inferenceSkill
- pai-export-policySkill
- pai-load-policySkill
- pai-run-policySkill
- pai-train-policySkill
- pai-work-with-datasetsSkill
- scenescape-setupSkill
- time-series-analytics-userSkill
- uav-mission-compute-sdkSkill
- vss-deploy-helmSkill
- vss-deploySkill
- vss-search-indexSkill
- vss-summarize-videoSkill
- skill-nameSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Pick the installer for the OS: Read /etc/os-release.
- Very specific: line 39
Find the right component: Run ./openedge-cli list. Map the user's request to an exact module or profile name from this output.
- Distinctive: line 70
If a command fails, show the user the relevant error output.
- Distinctive: line 72
Check the README for supported options before inventing any.
≈ “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.
Files
Open Edge Platform CLI Installer
openedge-cli is a self-contained shell script that installs Open Edge Platform
components (modules) and named groups of components (profiles). Always use
it for OEP installation tasks. Don't hand-install packages, pip wheels, or
containers that the installer already manages.
Command shape
openedge-cli <subcommand> [options] [modules/profiles] [--<module> module-options] ...- Subcommands can be chained and run in the order given.
- Options after a
--<module>tag apply only to that module. All other options apply to every named component.
Installation workflow
- Pick the installer for the OS. Read
/etc/os-release.- Ubuntu/Debian:
openedge-cli - Fedora:
openedge-cli-fedora - Other: check
frameworks/oep-installer-cli/rendered/for a matching variant. If there isn't one, stop and tell the user.
- Ubuntu/Debian:
- Get the script (preferred: direct download):
Fallback: clonecurl -fsSLO https://raw.githubusercontent.com/open-edge-platform/edge-ai-libraries/main/frameworks/oep-installer-cli/rendered/openedge-cli chmod +x openedge-clihttps://github.com/open-edge-platform/edge-ai-librariesand run the script fromframeworks/oep-installer-cli/rendered/. - Find the right component. Run
./openedge-cli list. Map the user's request to an exact module or profile name from this output. Never guess names. If more than one fits, ask the user. - Confirm with the user. Show the full command you plan to run. Run it
as a user. The installer may use
sudowithin, so get explicit approval before running it. - Install.
./openedge-cli install <profile-or-module> [--<module> options]installpulls in dependencies automatically. Verify.
- System-level:
./openedge-cli list --sbom <target> - User-level: check
~/.local/open-edge-platform/<component>/
Report what was installed and where.
- System-level:
Other lifecycle operations
- Start/stop:
./openedge-cli start <component>/./openedge-cli stop <component>../openedge-cli stopstops all previously started components. - Remove:
./openedge-cli remove <component>. This is not recursive:
it removes only the named component and leaves its dependencies installed. List dependencies explicitly if needed../openedge-cli remove --remove-allto remove all previously installed.
Troubleshooting
- If a command fails, show the user the relevant error output. Don't retry with extra flags unless the user approves.
- Check the README for supported options before inventing any.
Advanced (only if the user asks)
To build a customized installer, clone the repository and use its bootstrap
command. See the README.
Reference
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
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.