🤖 Kelos User Agent @gjkim42
Problem
The CLI reference in `docs/reference.md` lists `kelos create workspace` and `kelos create agentconfig` in the command table, but neither command has a dedicated flags section. A new user can see these commands exist but has no way to discover their flags without running `--help`.
This is inconsistent with `kelos install` and `kelos run`, which both have detailed flag sections immediately following the table.
Missing documentation
`kelos create workspace` flags
| Flag |
Description |
| `--repo` |
Git repository URL (required) |
| `--ref` |
Git reference (branch, tag, or commit SHA) |
| `--token` |
GitHub token — auto-creates a credentials secret |
| `--secret` |
Pre-existing secret name containing `GITHUB_TOKEN` |
| `--dry-run` |
Print the resource without creating it |
| `--yes, -y` |
Skip confirmation prompts |
`kelos create agentconfig` flags
| Flag |
Description |
| `--agents-md` |
Agent instructions (inline content or `@file` path) |
| `--skill` |
Skill definition as `name=content` or `name=@file` (repeatable) |
| `--agent` |
Agent definition as `name=content` or `name=@file` (repeatable) |
| `--mcp` |
MCP server as `name=JSON` or `name=@file` (repeatable) |
| `--skills-sh` |
skills.sh package as `source` or `source:skill` (repeatable) |
| `--dry-run` |
Print the resource without creating it |
Impact
The `--agents-md`, `--skill`, `--agent`, `--mcp`, and `--skills-sh` flags on `kelos create agentconfig` are especially useful and not obvious — users will miss the ability to create AgentConfigs from the CLI without reading source code. The `@file` convention (e.g. `--agents-md @./CLAUDE.md`) is also undocumented.
Fix
Add a `### `kelos create workspace` Flags` and a `### `kelos create agentconfig` Flags` section to `docs/reference.md`, following the pattern of the existing `kelos install` and `kelos run` flag sections.
🤖 Kelos User Agent @gjkim42
Problem
The CLI reference in `docs/reference.md` lists `kelos create workspace` and `kelos create agentconfig` in the command table, but neither command has a dedicated flags section. A new user can see these commands exist but has no way to discover their flags without running `--help`.
This is inconsistent with `kelos install` and `kelos run`, which both have detailed flag sections immediately following the table.
Missing documentation
`kelos create workspace` flags
`kelos create agentconfig` flags
Impact
The `--agents-md`, `--skill`, `--agent`, `--mcp`, and `--skills-sh` flags on `kelos create agentconfig` are especially useful and not obvious — users will miss the ability to create AgentConfigs from the CLI without reading source code. The `@file` convention (e.g. `--agents-md @./CLAUDE.md`) is also undocumented.
Fix
Add a `### `kelos create workspace` Flags` and a `### `kelos create agentconfig` Flags` section to `docs/reference.md`, following the pattern of the existing `kelos install` and `kelos run` flag sections.