[psanghvi17]

What changed

• Added skills/epinio-cli/ — a portable Cursor/Claude agent skill that maps every core epinio-mcp tool to equivalent epinio CLI commands (apps, push, namespaces, env, configurations, services/catalog, appcharts, builder images, gitconfigs, logs, plus clone/source/guidance stand-ins).
• Documented install (copy into ~/.cursor/skills/ or a project .cursor/skills/), CLI 1.14.1+ requirement, and honest gaps (no CLI for elevated adoption tools; no match/update gitconfig).
• Linked the skill from README and AGENTS.md for discoverability.

Why

Environments such as Maximus cannot use MCP but still have LLMs and the Epinio CLI. They asked for a curated skill that mimics MCP-like management via the CLI. Useful for general release as well when MCP is unavailable or disallowed.

Closes EPINIO-702

What to test

• Copy skills/epinio-cli/ to ~/.cursor/skills/epinio-cli/ (or a project .cursor/skills/) and confirm an agent loads it when asked to manage Epinio without MCP
• With Epinio CLI 1.14.1+ logged in, spot-check MCP → CLI rows against epinio <cmd> --help for apps, push, configurations, and gitconfigs
• Private git path: create a gitconfig, push with origin.git.gitconfig in a manifest; confirm the skill does not claim URL-only matching works on 1.14.1+
• Confirm elevated tools (adopt_app, reconcile_app, release_app, check_capabilities, enable_capability) are listed as gaps with no invented kubectl stand-ins
• Docs-only change — no Go code; make check not required for this PR

Possible regressions

None identified — documentation/skill artifact only; no MCP server, client, or tool registration changes.

Type

feature

Checklist

• make check passes (fmt-check, vet, lint, test) — N/A: docs/skill only, no Go changes
• New or changed behavior has tests, or the test impact is noted above — N/A: skill markdown, no runtime code
• Tool names, inputs, or outputs changed? The MCP server reference is updated — N/A: no MCP tool surface change
• New or changed capability sits in the right tier: core (Epinio API only, runs as the caller) vs elevated (EPINIO_MCP_ELEVATED, reaches directly into Kubernetes and needs the standard-elevated RBAC) — N/A: CLI skill, not an MCP tier
• Touches auth, credentials, or the RBAC/appchart surface? Flagged for security review — N/A: skill tells agents not to log --password; no secrets committed
• User-facing behavior changed? A matching PR is opened in epinio/docs — skill lives in this repo for now; docs PR optional if we want it on docs.epinio.io
• No secrets, tokens, or real cluster credentials committed

[dcharles525]

Moved skill to docs repo as the skill is supposed to be independent of the mcp, closing this