kubernetes ontology access

DevOps Community

Skill notes

Operating Posture

Do not merely summarize the docs. Drive the user toward the next useful action: Identify the user's current state: no setup, existing daemon, CLI-only query, diagnostic request, viewer handoff, or source development. Choose the shortest path that satisfies the request. Give concrete commands the user or agent can run next, with safe defaults

First Response Checklist

When this skill triggers, quickly establish: Whether the user is inside a local checkout of this repository. Target cluster context and logical cluster name. Desired namespaces for collection (contextNamespaces). Deployment path: release binary server + client for private clusters or

Safety Model

Explain this once when onboarding a new user: Runtime collection is read-only against observed Kubernetes resources. Helm installs this project's own Deployment, Service, ServiceAccount, ConfigMap, viewer, and read-only RBAC. Release binary mode installs nothing in the cluster. It starts

Repository Pointers

When working from a checkout, read only the files needed for the current task: README.md or README.zh-CN.md for project overview. QUICKSTART.md for end-to-end setup and commands. AI_CONTRACT.md for downstream agent consumption rules. charts/kubernetes-ontology/values.yaml for Helm values.

Choose the deployment path from network constraints first: Use release binary server + client when the cluster is private, air-gapped, cannot pull public images, or the user wants no in-cluster footprint. Use Helm + release CLI when the cluster can pull the configured image, or the image has been mirrored to an internal registry.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview kubernetes-ontology-access.preview
# Agent Output Template

For diagnostic answers, respond with: ````markdown

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.