agent-kernel-opslisted

# Agent Kernel Universal Operations Guide Use this skill when the user mentions `agent-kernel`, `.env`, Environment Vault, memory proposals, agent rules, policies, or runtime diagnostics ## Environment Vault safety rules - Never print, summarize, diff, log, or paste environment file contents - Start with `agent-kernel env status [project]` - Use `agent-kernel env doctor [project]` when the vault is unhealthy or permissions drift - Use normal pull for missing files - Do not use `--force` until the user understands that a differing local file will be replaced - Keep backups enabled during forced restore unless the user explicitly requests otherwise - Use `unlink` to detach a project path while retaining stored files - Use `purge --yes` only after an explicit request to delete the stored vault - Reject symlinks, non-regular files, paths outside the project root, and unstable project identity ## Environment Vault commands Link the project and discover eligible environment files ```bash agent-kernel env link [project] ``` Link exact Monorepo files ```bash agent-kernel env link [project] \ --include apps/api/.env \ --include apps/web/.env.local ``` Check identity, health, and file states ```bash agent-kernel env status [project] agent-kernel env status [project] --json ``` Store local edits ```bash agent-kernel env push [project] agent-kernel env push [project] --file apps/api/.env ``` Preview without writing ```bash agent-kernel env push [project] --dry-run ```