Documentation
¶
Overview ¶
Package skills implements FR-MCP-04's agent skill bundles and the `vegaload init` command built on them: the actual Markdown content Claude Code and Cursor read to know when and how to call VegaLoad's MCP tools, embedded into the compiled binary at build time (via go:embed) so `vegaload init` can write them out without needing the vegaload source tree to be present on the machine it's installed on.
Index ¶
Constants ¶
This section is empty.
Variables ¶
var ClaudeCode string
ClaudeCode is the Claude Code skill bundle's SKILL.md content, written by Init to .claude/skills/vegaload/SKILL.md.
var ClaudeCodeSmoke string
ClaudeCodeSmoke is the Claude Code smoke-test skill's SKILL.md content, written to .claude/skills/vegaload-smoke/SKILL.md.
var Cursor string
Cursor is the Cursor rules bundle's content, written by Init to .cursor/rules/vegaload.mdc.
var CursorSmoke string
CursorSmoke is the Cursor smoke-test rules content, written to .cursor/rules/vegaload-smoke.mdc.
Functions ¶
func MergeMCPServerConfig ¶
func MergeMCPServerConfig(existing []byte, exePath string, force bool) (merged []byte, changed bool, err error)
MergeMCPServerConfig takes an existing MCP config file's raw JSON (nil or empty for "no existing file") and returns the JSON it should be replaced with, with a "vegaload" entry added or updated under "mcpServers" pointing at exePath — preserving every other key and every other configured server untouched. It returns ok=false without modifying anything when a "vegaload" entry already exists and force is false, so a second `vegaload init` doesn't clobber a hand-edited config by default.
func MergeMCPServerConfigEnv ¶ added in v0.9.1
func MergeMCPServerConfigEnv(existing []byte, exePath string, force bool, env map[string]string) (merged []byte, changed bool, err error)
MergeMCPServerConfigEnv is MergeMCPServerConfig plus environment variables for the server. Each key in env is set (or replaced) in the entry's "env" object; env keys already there and not named in env are kept, and with a nil or empty env an existing "env" is left as it is. The entry has no "env" key at all when nothing sets one, so the output without env is the same as MergeMCPServerConfig's always was.
When env is not empty the entry is brought up to date even if it exists and force is false: command and args are refreshed and the env keys set. Nothing is written (changed is false) when that produces the file already on disk.
Types ¶
This section is empty.