Gkarch/sync main 449a3992

.agents/README.md

@@ -1,46 +1,44 @@
-# `.agents/` — agent-agnostic source of truth
+# `.agents/` — agent compatibility and shared config
 
-This directory is the canonical location for assets shared by AI coding agents
-working in this repository (Claude Code, Codex, Cursor, …).
+This directory exposes the ModelOpt plugin skills to repository-local agents
+and holds shared configuration.
 
 ## Layout
 
 ```text
 .agents/
-├── skills/                 # SKILL.md files (canonical)
-│   └── <skill-name>/SKILL.md
+├── skills → ../plugins/modelopt/skills
+├── plugins/
+│   └── marketplace.json   # Codex marketplace
 ├── scripts/                # shared helper scripts (sync-upstream-skills.sh, …)
 └── clusters.yaml.example   # remote-cluster config template
-```
-
-## Why this exists
 
-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.
+plugins/modelopt/
+├── .claude-plugin/
+├── .codex-plugin/
+└── skills/                 # canonical SKILL.md files
+    ├── common/             # shared skill support files
+    └── <skill-name>/SKILL.md
+```
 
 ## How each agent finds these
 
 Each agent points at `.agents/` through whatever mechanism it supports — never
 a copy:
 
 - **Claude Code** only auto-discovers skills under `.claude/skills/`, so
-  `.claude/` holds relative in-repo symlinks back into `.agents/`:
-  `.claude/skills → ../.agents/skills`, `.claude/scripts → ../.agents/scripts`,
-  and `.claude/clusters.yaml.example → ../.agents/clusters.yaml.example`. These
-  follow the same committed-symlink pattern already used elsewhere in this repo
-  (e.g. `CLAUDE.md`, `tools/launcher/modules/Model-Optimizer`).
-- **Future agents** (Codex, Cursor, …) add their own symlink or config pointing
-  at `.agents/`.
+  `.claude/skills/` holds relative symlinks into `.agents/skills/`.
+- **Repository agents** use `.agents/skills`, a relative symlink into the
+  plugin.
+- **Claude Code and Codex plugins** load `plugins/modelopt/skills` directly.
 
 ## Editing rules
 
-- **Always edit files under `.agents/`**.
+- **Always edit skills under `plugins/modelopt/skills/`**.
 - 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
-  conventions of existing skills (e.g. `.agents/skills/monitor/SKILL.md`).
+- New skills go in `plugins/modelopt/skills/<skill-name>/SKILL.md`.
+- Shared support files go in `plugins/modelopt/skills/common/`.
 
 ## Project-level cluster config
 

.agents/TOOLING.md

@@ -8,6 +8,11 @@ of the always-loaded agent instructions.
 Update `AGENTS.md` for repository-wide agent instructions. `CLAUDE.md` is
 symlinked to `AGENTS.md`, so changes there apply to both Codex and Claude Code.
 
+## Installable Skills
+
+The `modelopt` plugin packages the repository skills for use from any
+workspace. Installation commands are in the [README](../README.md#ai-agents).
+
 ## Local Overrides
 
 For private local instructions, use the tool-specific override file:

.agents/plugins/marketplace.json

@@ -0,0 +1,20 @@
+{
+  "name": "modelopt",
+  "interface": {
+    "displayName": "NVIDIA Model Optimizer"
+  },
+  "plugins": [
+    {
+      "name": "modelopt",
+      "source": {
+        "source": "local",
+        "path": "./plugins/modelopt"
+      },
+      "policy": {
+        "installation": "AVAILABLE",
+        "authentication": "ON_INSTALL"
+      },
+      "category": "Productivity"
+    }
+  ]
+}

.agents/review-guidelines/technical-blog.md

@@ -0,0 +1,42 @@
+# Technical blog review guideline
+
+Use this rubric when a pull-request comment requests a **technical blog** or
+**technical announcement** review. It applies to public-facing documentation
+such as `docs/source/announcements/` and complements the repository's normal
+code-review guidance.
+
+## Review scope
+
+Review the changed announcement and its landing-page card together. Do not
+review unrelated source files unless they provide evidence for a claim in the
+post.
+
+## Checks
+
+1. **Factual support** — Every technical claim, performance number, and
+   comparison must be supported by a cited public source, a clearly identified
+   reproducible measurement, or a qualified statement. Flag claims that
+   overstate what the cited source establishes.
+2. **Citation integrity** — Check that cited papers, repositories, checkpoints,
+   and issue or PR links exist and match the surrounding claim. Publication
+   dates must not precede the cited source's availability.
+3. **Technical precision** — Preserve meaningful distinctions: measured versus
+   inferred results, training versus serving behavior, throughput versus
+   latency, architecture versus implementation detail, and public facts versus
+   internal context.
+4. **Figure provenance** — Images need an accurate alt text and a source or
+   provenance that makes their public use appropriate. Captions and nearby
+   text must not imply a result the figure does not show.
+5. **Public-release suitability** — Do not expose private infrastructure,
+   unreleased products, confidential benchmark data, credentials, internal
+   URLs, or claims that cannot be independently supported by public material.
+6. **Reader clarity** — Verify the title, date, author, summary, tags, and
+   announcement-card metadata agree. Prefer precise terminology over marketing
+   shorthand when the two could be confused.
+
+## Findings
+
+Raise only material findings. Each finding should identify the exact claim,
+explain the public-facing risk, and propose a concrete correction. Do not
+duplicate routine style, spelling, or formatting feedback already handled by
+CodeRabbit.

.agents/scripts/sync-upstream-skills.sh

@@ -26,13 +26,14 @@
 #
 # Requires: gh, base64, awk. Run from the repo root.
 #
-# The script overwrites .agents/skills/<skill>/ with upstream contents and
+# The script overwrites plugins/modelopt/skills/<skill>/ through the
+# .agents/skills compatibility symlink and
 # re-applies our provenance lines into each SKILL.md frontmatter. If you have
 # local changes to a vendored skill, they will be lost — that is expected,
 # since vendored-verbatim skills should not be modified locally.
 #
 # Note: .claude/skills/ (and other agent-specific skill dirs) are symlinks to
-# .agents/skills/ — see .agents/README.md.
+# plugins/modelopt/skills/ — see .agents/README.md.
 
 set -euo pipefail
 

.agents/skills

@@ -0,0 +1 @@
+../plugins/modelopt/skills