Results for “install”

Use when a subscriber admin is installing, upgrading, or rolling back a managed package (1GP or 2GP) sourced from AppExchange or a private install URL — covers pre-install evaluation, sandbox dry runs, license and dependency checks, the install/upgrade audit trail, post-install configuration the package's InstallHandler cannot perform, and uninstall fallback. NOT for building managed packages as an ISV (use devops/managed-package-development), unlocked-package development (use devops/unlocked-package-development), or AppExchange listing setup. Trigger keywords: InstalledPackage, installedPackages, securityType, activateRSS, sf package install, sf package installed list, PackageLicense, UserPackageLicense, AllowedLicenses, UsedLicenses, push upgrade, PackageSubscriber, namespace prefix, 04t, certified managed package limits.

The English summary is being prepared. Showing the original description.

Find available Codex skills and install selected ones from a curated list or a GitHub repository. Supports public and private repositories, marks skills already installed, and lets you specify source paths and installation destinations.

• Browse available skills and check which are already installed
• Install a skill from the curated list
• Install skills from a private GitHub repository

Manage KubeSphere extensions from discovery through installation, configuration, upgrades, and removal. Check dependencies and exact versions, prepare an InstallPlan deployment resource, and inspect status and logs to investigate installation or upgrade failures.

• Find extensions and available versions
• Install a specific extension version
• Change settings or upgrade an extension

Manage MATLAB packages with the in-product MATLAB Package Manager (mpm) on MATLAB R2026b or later: install, uninstall, update, search, or inspect packages; declare package dependencies in a matlab.toml project; install a shareable .mltbx package; or manage repositories. Covers dependency-resolution errors and anything involving mpminstall / mpmuninstall / mpmupdate / mpmlist / mpmsearch / mpmAddRepository / matlab.mpm.*. MATLAB *packages* are distinct from MathWorks products, toolboxes, and support packages: a bare "what packages are installed?" means MPM packages (mpmlist / matlab.mpm.Package) — this skill — unless the user explicitly says products, toolboxes, or support packages. NOT for installing MATLAB, Simulink, or toolboxes from a shell via the standalone mpm executable (the OS-level product installer), nor for listing installed products / toolboxes (ver, installedAddons) — use matlab-install-products for those.

The English summary is being prepared. Showing the original description.

Check whether Nasiko CLI is installed, preview installation of a fixed, verified version, and remove an ECC-managed installation. The workflow uses ECC commands, requires consent for installation, and checks ownership before removal.

• Checking whether Nasiko CLI is installed
• Previewing installation of a verified version
• Removing an ECC-managed CLI installation

Browse available Codex skills and install them from a curated list or a specified GitHub location. Supports experimental skills, private repositories with credentials, and installing several skill folders in one operation.

• Browse available skills and see which are already installed
• Install a named skill from the curated list
• Add a skill from a private GitHub repository

Find and install Codex skills from a curated catalog or a GitHub path. Check which skills are already installed, explore experimental options, and add skills from private repositories when credentials are available.

• Browse available skills and check installed ones
• Install a skill by name from the curated catalog
• Add a skill from a private GitHub repository

Set up the OpenViking long-term memory plugin for OpenClaw through conversation. The skill handles installation, configuration, and verification so chat facts can be saved and relevant memories recalled across sessions, using an existing OpenViking server.

• Add long-term memory to OpenClaw
• Recall saved facts across chat sessions
• Separate memories by assistant or sender

Runnable end-to-end validation playbook for the Rembric TUI installer — catch breakage before merging/deploying, AND a sandboxed manual walkthrough to evaluate/iterate its UI/UX without polluting your real env. Apply before shipping any change touching `apps/plugin/install.sh`, the repo-root `install.sh` shim, any per-client `install.sh`/`uninstall.sh`, or distribution docs, or when you want to preview/try/demo the installer and polish how it looks and feels. Layered: CI-safe headless (vitest + `sh -n`), local install round-trips, operator interactive pty smoke, an optional full Docker `up` smoke, plus a sandboxed manual UX walkthrough. For the installer contract/what-not-to-break, see `rembric-tui-installer`.

The English summary is being prepared. Showing the original description.

The Rembric TUI installer contract — the single, canonical install/setup/upgrade/uninstall path (`apps/plugin/install.sh`, fronted by the repo-root `install.sh` shim). Apply when touching `install.sh`, the root shim, any per-client `install.sh`/`uninstall.sh`, `marketplace.json`, or distribution docs (README, `docs/agents.md`, plugin/client READMEs). Covers the orchestrator model, what must not break, and where the source of truth lives. For running the validation suite, use `rembric-tui-installer-e2e`.

The English summary is being prepared. Showing the original description.

Configure ECC in Claude Code, Codex, or Kimi with a guided setup workflow. It checks the current installation, previews supported changes, requests confirmation, applies them, and verifies the result.

• Installing or updating ECC
• Changing installation scope in Claude Code
• Adjusting ECC hook automation in Claude Code

Set up zvec-grep (zg) for use with Qwen Code. Check existing installation and settings, explain the integration changes, and request approval before installing the package and registering it with Qwen Code.

• Install zg and connect it to Qwen Code
• Check existing zg installation and integration settings
• Review configuration changes before installation

Install and configure WizTelemetry Platform Service, the shared API backend for KubeSphere observability extensions. Generate configuration based on installed extensions, update installation settings, and inspect service health, pods, and logs.

• Install the shared backend for observability extensions
• Regenerate configuration after changing extensions
• Check API server and console health

Find available Codex skills in a curated list and install them by name or GitHub path. Supports multiple skills in one run, custom destinations, and private repositories using available credentials.

• Browse curated skills and see which are already installed
• Install a curated skill by name
• Add skills from a public or private GitHub repository

Manage community skills installed through legal-builder-hub by uninstalling, disabling, or re-enabling them. It checks installation records and file locations, requires explicit confirmation before file operations, preserves configuration by default, and logs each action.

• Uninstalling a community skill that is no longer needed
• Temporarily disabling a skill and its hooks or agents
• Re-enabling a previously disabled skill

Remove a community skill installed through the hub after showing every file path and receiving explicit confirmation. Check installation records, protect first-party plugin skills, and record the uninstall action with a timestamp for the audit trail.

• Completely removing an unused community skill
• Reviewing deletion paths before uninstalling
• Keeping an audit trail of skill removals

Install or update the M365 Agents Toolkit (ATK) CLI and VS Code extension. Triggers: "install atk", "update atk", "install agents toolkit", "update agents toolkit", "install the toolkit", "setup atk", "get atk", "install atk cli", "install atk extension", "install atk vsix", "update the vs code extension", "install latest atk", "upgrade atk"

The English summary is being prepared. Showing the original description.

Prepare to audit a codebase spanning several technologies by installing the external repo-scan skill from a fixed, reviewable commit. This entry provides the installation procedure; the code audit requires invoking the installed skill separately.

• Installing the audit skill before reviewing a legacy codebase
• Preparing an audit before a major refactor
• Preparing to inspect third-party code bundled in source

Package Python apps as Windows installers using Nuitka and Inno Setup. Review compilation settings, remove unnecessary files, and analyze DLLs, shared library files, to reduce package size and improve startup behavior.

• Build a Windows installer for a Python desktop app
• Find large dependencies and reduce distribution size
• Investigate apps that fail on a clean Windows system

Find installable agent skills for a task you want help with. Search using relevant keywords, explain matching options with installation commands and detail links, and install a chosen skill through the provided script when requested.

• Finding skills for a specific task
• Exploring skills for a new area of work
• Checking what a skill does and how to install it

Find agent skills for a specific task, compare candidates using their capabilities, sources, and installation history, and install a selected skill into Cherry after the user has expressed an intent to install it.

• Finding a skill for a specific task
• Comparing skill sources and installation history
• Installing a selected skill into Cherry

Find installable agent skills for a specific task, check their sources and adoption, and present relevant options with explanations, links, and installation commands. Help install a selected skill when the user wants to proceed.

• Find skills for a specific task or field
• Compare skill sources and adoption before installation
• Get installation commands and links for relevant skills

Find installable agent skills for a specific task, check their sources and adoption, and present relevant options with explanations, links, and installation commands. Help install a selected skill when the user wants to proceed.

• Find skills for a specific task or field
• Compare skill sources and adoption before installation
• Get installation commands and links for relevant skills

Install LifeOS into an existing AI agent environment, then use a guided interview to capture current circumstances and goals for the Pulse dashboard. The skill also handles installation checks, updates, and removal.

• Set up LifeOS in an existing AI agent environment
• Capture current circumstances and goals through an interview
• Check installation problems and suggested fixes