portal-ops

Orchestrate the portal-ops CLI to manage instances, configs, secrets, and logs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/meganide/claude --skill portal-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: portal-ops
Source: https://github.com/meganide/claude/tree/main/skills/portal-ops
Command: npx skills add https://github.com/meganide/claude --skill portal-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Portal operations often require switching between consoles and tools to manage instances, configs, secrets, logs, and service restarts. This Skill provides a centralized Portal Ops CLI workflow to streamline common operational tasks across environments.

Core Features & Use Cases

  • List Portal instances across environments and filter by status or environment.
  • Retrieve, view, and export instance configurations and their histories.
  • Manage secrets and perform basic maintenance tasks like viewing logs and restarting services.
  • Monitor and diagnose Portal deployments with consolidated CLI commands.
  • Use with export conventions to capture reproducible state dumps.

Quick Start

Run portal-ops to list all Portal instances: portal-ops list Then export a config for a specific instance using the repo's convention: portal-ops config export -i <instance> -o tmp/<instance>-$(date +%Y-%m-%d-%H%M).json

Frequently Asked Questions about portal-ops

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

FAQPage Schema
How do I manage Portal instances across multiple environments from the CLI?

Portal instance management across environments is handled by orchestrating the portal-ops CLI to list, configure, and monitor instances. You apply deterministic commands spanning customer and test portals to execute operational tasks centrally without switching consoles.

How do I export Portal instance configurations reproducibly?

Reproducible Portal instance configuration exports are generated using the portal-ops config export command. Specifying the target instance and an output path with a timestamped filename captures a deterministic state dump of the configuration.

Can I view and manage Portal deployment logs and secrets using a single CLI tool?

Portal deployment logs and secrets can be managed centrally using the portal-ops CLI. It consolidates basic maintenance tasks, enabling you to view logs, manage secrets, and restart services across environments without switching tools.

What do I need to run portal-ops commands for instance monitoring?

Running portal-ops commands for instance monitoring requires the portal-ops CLI installed and basic authentication setup. This prerequisite allows the tool to execute deterministic commands across customer and test portal environments.

What is the best way to diagnose Portal deployments without switching consoles?

Diagnosing Portal deployments without switching consoles is achieved by using the portal-ops CLI. It provides consolidated commands to monitor instances, view logs, and export configuration histories for centralized troubleshooting.

Does portal-ops support filtering Portal instances by status or environment?

Portal-ops supports filtering Portal instances by status and environment using the portal-ops list command. This allows you to quickly retrieve and monitor specific subsets of your deployments across customer and test portals.