Workspace Improvement

Cross-reference workspace documentation with live Kubernetes deployments and create pull requests for discrepancies.

9|3|Updated Apr 16, 2024
One-click install
npx skills add https://github.com/keiretsu-labs/kubernetes-manifests --skill workspace-improvement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Workspace Improvement
Source: https://github.com/keiretsu-labs/kubernetes-manifests/tree/main/openclaw/workspaces/main/skills/workspace-improvement
Command: npx skills add https://github.com/keiretsu-labs/kubernetes-manifests --skill workspace-improvement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, kubectl, jq, yq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that your workspace documentation accurately reflects the live deployment, preventing inconsistencies and outdated information.

Core Features & Use Cases

  • Cross-referencing: Compares workspace documentation (container names, volume mounts, model providers, agent lists, skill directories) against the actual deployed state.
  • Staleness Detection: Identifies outdated image tags, configuration values, or version numbers in documentation.
  • PR Generation: Automatically creates pull requests to fix identified discrepancies in the kubernetes-manifests repository.
  • Use Case: After deploying a new version of an agent, use this Skill to verify that all documented container image tags, environment variables, and accessible skills match the live environment, and automatically generate a PR to update any outdated documentation.

Quick Start

Use the Workspace Improvement skill to cross-reference workspace documentation against the live deployment and create pull requests for any identified discrepancies.

Frequently Asked Questions about Workspace Improvement

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

FAQPage Schema
How do I sync workspace documentation with live Kubernetes deployments?

You can sync workspace documentation with live Kubernetes deployments by cross-referencing container names, volume mounts, and model providers against the actual deployed state, then generating validated pull requests to fix discrepancies.

How do I detect outdated image tags in my Kubernetes documentation?

Detect outdated image tags by cross-referencing your workspace documentation against the live Kubernetes deployment state, identifying staleness in image tags, configuration values, and version numbers automatically.

Can I automatically create pull requests to update kubernetes-manifests documentation?

Yes, you can automatically create validated pull requests to the kubernetes-manifests repository after detecting discrepancies between your workspace documentation and the live deployment state.

Do I need kubectl and jq installed to validate workspace documentation against deployments?

Yes, you need kubectl and jq installed, along with gh, git, and yq, as these tools are required to query the live deployment state and execute the documentation synchronization process.

What Kubernetes deployment details get cross-referenced during workspace documentation validation?

The validation cross-references container names, volume mounts, model providers, agent lists, and skill directories to ensure your workspace documentation accurately reflects the live Kubernetes deployment configuration.

Why does my workspace documentation show stale configuration values after a deployment?

Workspace documentation shows stale configuration values when it is not synchronized with the live Kubernetes deployment, meaning image tags, environment variables, and accessible skills have drifted from the actual deployed state.