removing symlinks

Signed-off-by: Seonghee Lee <seongheel@nvidia.com>

Author: shljessie

.agents/README.md

@@ -15,37 +15,14 @@ working in this repository (Claude Code, Codex, Cursor, …).
 
 ## Why this exists
 
-Different agents look for skills/config in vendor-specific directories:
-
-| Agent       | Default location              |
-|-------------|-------------------------------|
-| Claude Code | `.claude/skills/`             |
-| Codex       | `.codex/skills/`              |
-| Cursor      | `.cursor/skills/`             |
-
-Maintaining N copies of the same skill is a non-starter. Instead, **`.agents/`
-is the single source of truth**, and each vendor directory is a symlink:
-
-```text
-.claude/skills              -> ../.agents/skills
-.claude/scripts             -> ../.agents/scripts
-.claude/clusters.yaml.example -> ../.agents/clusters.yaml.example
-```
-
-To add support for a new agent, create a directory with the symlinks that
-agent expects, e.g.:
-
-```bash
-mkdir -p .codex
-ln -s ../.agents/skills .codex/skills
-git add .codex/skills
-```
+Different agents look for skills/config in vendor-specific directories. Rather
+than maintaining N copies that drift out of sync, **`.agents/` is the single
+source of truth** — each agent's guidance or install mechanism points here
+directly.
 
 ## Editing rules
 
-- **Always edit files under `.agents/`**, never under the vendor symlink paths.
-  Edits via the symlink work, but the diff will look like changes to
-  `.agents/...` either way; editing the canonical path makes that explicit.
+- **Always edit files under `.agents/`**.
 - Vendored-verbatim skills (`launching-evals`, `accessing-mlflow`) are managed
   by `.agents/scripts/sync-upstream-skills.sh` — do not modify by hand.
 - New skills go in `.agents/skills/<skill-name>/SKILL.md` following the
@@ -60,11 +37,3 @@ The remote-execution skills look for a `clusters.yaml` at, in order:
 3. `<repo-root>/.claude/clusters.yaml` (project-level, back-compat)
 
 See `clusters.yaml.example` for the schema.
-
-## A note on Windows
-
-Git stores symlinks portably, but Windows requires either Developer Mode or
-`git config --global core.symlinks true` plus admin rights for them to
-materialise correctly. If you're on Windows and skills aren't being picked
-up under `.claude/skills/`, that's the most likely cause — `.agents/skills/`
-will still work directly.