object-panel

Coordinate Kubernetes object detail tabs, YAML workflows, logs, and docked panel UX.

411|21|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/luxury-yacht/app --skill object-panel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: object-panel
Source: https://github.com/luxury-yacht/app/tree/main/.agents/skills/object-panel
Command: npx skills add https://github.com/luxury-yacht/app --skill object-panel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines working with Kubernetes object details by unifying YAML, logs, related objects, and actionable tabs into a single object panel workflow.

Core Features & Use Cases

  • Object detail surfaces: Navigate overview/detail tabs and related objects while preserving complete object identity and cluster scoping.
  • YAML read/apply/edit flows: Load, edit, and manage object YAML while using the shared YAML editor mechanics and workflow state.
  • Logs and shell/debug: View container and node logs with shared presentation utilities, plus shell/debug tabs for deeper investigation.
  • Imperative actions and panel docking: Execute object actions, manage Helm content, and maintain consistent docked/refresh behavior across cluster and namespace changes.
  • Tests and workflow guardrails: Validate capability/permission handling, status rendering, and object identity linkages, backed by focused test runs.

Quick Start

Use the object-panel skill to implement or update an object detail tab, including YAML and logs, with correct cluster-scoped GVK identity and synchronized frontend/backend DTO bindings.

Frequently Asked Questions about object-panel

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

FAQPage Schema
How do I implement a Kubernetes object detail panel with YAML editing and log viewing?

Build the Kubernetes object detail panel by coordinating object detail fetching, YAML read/apply/edit flows, and log/shell/debug tabs into a unified docked panel UX. Route typed detail fetchers through exact-GVK capability metadata and centralize YAML editor mechanics in the shared YamlEditor component.

How do I preserve cluster scoping and object identity when navigating related Kubernetes objects?

Preserve Kubernetes object identity and cluster scoping during related object navigation by using backend-provided ResourceLink.ref values. This ensures accurate GVK identity linkage is maintained across overview and detail tabs within the docked panel workflow.

Can I view container and node logs within the same panel used for editing Kubernetes object YAML?

View container and node logs alongside YAML editing using shared presentation utilities within the object panel. The workflow integrates log tabs and shell/debug tabs for deeper investigation while maintaining synchronized docked and refresh behavior across cluster and namespace changes.

How do I manage Helm content presentation within a Kubernetes object panel workflow?

Manage Helm content presentation through the object panel workflow by executing imperative object actions and maintaining consistent docked panel behavior. Use backend-provided statusPresentation to render content accurately across cluster and namespace changes.

What tests should I run when updating Kubernetes object panel behavior and YAML workflows?

Run focused tests that validate capability and permission handling, status rendering, and object identity linkages across frontend and backend DTO bindings. These test automation guardrails ensure the YAML editor mechanics and workflow state remain synchronized during object-panel updates.