Kepler

Plugin kepler in systemsbyzane/Kepler. Commands read from the repo's manifest — 1 month ago.

Skills (18)

• kepler-artifacts

  Route DOCX, PDF, and XLSX creation or editing through installed system artifact capabilities with mandatory visual quality gates. Use for Word documents, PDFs, spreadsheets, control workbooks, or artifact package validation in a Kepler.

• kepler-automations

  Design, inspect, or operate safe Kepler recurring jobs. Use for daily Doctor, recurring repository or CI monitoring, vulnerability triage, research refresh, compliance evidence review, governance drift, automation deltas, or questions about whether Hub YAML specifications create real Codex automatio

• kepler-charts

  Coordinate Helm, Kubernetes manifest, deployment YAML, and rendered configuration changes through a Kepler. Use for chart values, templates, RBAC, networking, secrets, images, storage, probes, scheduling, rendered manifests, or rollout review. CI/CD pipeline files belong to the focused Kepler CI/CD

• kepler-ci

  Coordinate trustworthy CI/CD and software-delivery work through Kepler. Use when a user asks about failing or slow checks, pipeline diagnosis, build and test workflows, release automation, artifact provenance, caching, matrices, runners, permissions, secrets, environments, approvals, promotion, roll

• kepler-compliance

  Coordinate evidence-backed compliance program workspaces and professional artifacts. Use for control assessments, evidence indexes, RMF or ATO support, eMASS-style workbooks, OSCAL, policies, POA&M candidates, structured-record validation, or package quality review.

• kepler-db

  Coordinate safe, reliable database work through Kepler. Use whenever a request discusses databases, DBs, data stores, SQL, relational or non-relational persistence, schema or table design, queries or indexes, transactions or locking, ORMs, connection pools, migrations or backfills, replication or fa

• kepler-development

  Coordinate secure application and multi-repository implementation through a Kepler. Use when a user wants to build or change features, fix bugs, implement backend or frontend behavior, modify APIs or data, coordinate cross-repository contracts, or hand off runtime validation. Planning-only and revie

• kepler-doctor

  Run and interpret read-only Kepler Doctor and structured status checks. Use for control-project integrity, ArchitectureMap and Plan validity, exact project/path drift, dispatch prerequisites, bridge integrity, repository state, automation policy, or compliance sidecar parity.

• kepler-patching

  Coordinate vulnerability, dependency, base-image, and container-image patching while preserving downstream runtime contracts. Use for CVEs, SBOMs, scans, image ownership, rebuilds, tags or digests, or patch review queues.

• kepler-plan

  Create right-sized, evidence-led plans for work coordinated through Kepler. Use when a user asks to plan, scope, design, sequence, break down, or choose an approach for implementation, migration, release, CI/CD, platform, security, compliance, or cross-repository work before changes begin. Natural p

• kepler-platform

  Coordinate platform engineering and environment work through Kepler. Use when a user asks about infrastructure as code, Terraform or OpenTofu, Pulumi, cloud resources, Kubernetes clusters, SSH or remote-host operations, kind, kubectl, live deployments, platform services, identity, networking, DNS, c

• kepler-repo-bridge

  Inspect, change, migrate, or repair optional repository instruction bridges and exact-path saved-project identities for an existing Kepler control project. Use for reference, materialized, or repo-native mode changes, bridge drift, unsafe overrides, or advanced bulk bridge work. Initial project-firs

• kepler-research

  Run durable, evidence-led technical research through a Kepler. Use for architecture traces, deployment or ownership questions, current external facts, declared-versus-live comparisons, decision briefs, or source freshness reviews.

• kepler-review

  Review changes and readiness through Kepler with findings-first, evidence-backed output. Use when a user asks to review a pull request, diff, branch, commit, working tree, architecture or implementation plan, release readiness, or a cross-repository change for correctness, security, regressions, com

• kepler-setup

  Generate and validate a Kepler control project, select existing saved Codex projects by opaque ID and exact path, propose ArchitectureMap domains and relationships, and persist them after confirmation. Use for /kepler setup, onboarding, or control-project validation.

• kepler-stig

  Evaluate, review, and plan remediation for STIG compliance while deterministically parsing or generating CKL files in a portable Kepler. Use for natural STIG intent, pasted rules, evidence or applicability questions, inherited controls, Kubernetes or chart checks, evidence-gap reviews, CKL import or

• kepler-upgrade

  Plan, explain, apply, and verify a supported Kepler plugin upgrade without regenerating a Hub or changing attached repositories. Use when a user asks to upgrade or update Kepler, reinstall a newer Kepler plugin build, check whether an update is available, preserve existing Kepler state during an upd

• kepler

  Coordinate context-aware engineering work across existing Codex projects with ArchitectureMaps, revisioned Plans, focused ContextPacks, exact dispatch, WorkerResults, and scoped memory. Use for explicit /kepler commands, multi-project planning and status, exact worker dispatch, or Kepler control-pro

MCP servers (1)

• kepler_dispatch

  runs: ./scripts/launch_kepler_dispatch_mcp

Similar plugins