[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73ASZHY0KX0E83CSPBPSS98":3,"skill-same:01M73ASZHY0KX0E83CSPBPSS98":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":39,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M73ASZHY0KX0E83CSPBPSS98","rag-perf",null,"NVIDIA RAG Blueprint performance-tuning guidance for profiling retrieval stacks, comparing bottlenecks, and validating latency or throughput improvements.","bg-szy\u002FTOP-SKILLS","bg-szy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F106576190?v=4","01M73A4E8KPV67SFXRY8XZGNBX","ShuZhiyong","01M73A4E96MQ294MHM74TZBVQD",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fagent-skills\u002Frag-perf\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: rag-perf\nversion: \"2.0\"\nlast_updated: 2026-09-08\ntags: [nvidia, rag, performance, latency, throughput, profiling]\ndescription: \"NVIDIA RAG Blueprint performance-tuning guidance for profiling retrieval stacks, comparing bottlenecks, and validating latency or throughput improvements.\"\nlicense: \"Apache-2.0\"\ncompatibility: \"Guidance imported from the NVIDIA RAG Blueprint performance skill for current benchmark and profiling workflows.\"\n---\n# RAG-Perf — config-driven perf benchmark CLI\n\n## Purpose\n\nDrive a deployed NVIDIA RAG Blueprint server with a YAML config, run a server-side **profiling pass** (per-stage timing, citation quality, bottleneck inference) and an optional **aiperf load test** (TTFT \u002F E2E \u002F token & request throughput \u002F error rate), and write a unified report. The CLI is intentionally minimal: `rag-perf -c \u003Cconfig>` plus `--help` \u002F `--version`. Behaviour is *fully* config-driven; field variations belong in YAML.\n\n## Scope\n\n- **Accuracy \u002F RAGAS** scoring of answer quality → use the **rag-eval** skill.\n- **Deploying, repairing, or configuring services** (compose, helm, NIM env vars) → use the **rag-blueprint** skill.\n- **Production monitoring \u002F alerting** — rag-perf is a one-shot benchmark tool.\n- **Runtime requirement:** a deployed RAG server reachable on the network.\n\n## Prerequisites\n\n- Repo cloned; **run commands from the repo root** (config paths in the presets are repo-root-relative).\n- Python **3.11+** and **uv** on PATH.\n- Install rag-perf into its own uv-managed venv: `uv sync --project scripts\u002Frag-perf`.\n- For unit tests: install dev extras as well — `uv sync --project scripts\u002Frag-perf --extra dev` (otherwise `pytest-asyncio` is missing and async tests error out at collection time).\n- A reachable RAG server (default `http:\u002F\u002Flocalhost:8081`). For the aiperf phase, the bundled `nvidia_rag` endpoint plugin must be installed — `pip install -e .\u002Fscripts\u002Frag-perf` registers it via the `aiperf.plugins` entry point.\n- For **synthetic** queries: an OpenAI-compatible chat-completions endpoint reachable at `synthetic.llm_url` (default `http:\u002F\u002Flocalhost:8999\u002Fv1\u002Fchat\u002Fcompletions`).\n- rag-perf itself runs without `NVIDIA_API_KEY` (unlike rag-eval). The synthetic LLM endpoint may require its own auth — that's the deployment's concern.\n\n## Instructions\n\n1. **Pick a preset.** The three under [`scripts\u002Frag-perf\u002Fconfigs\u002F`](..\u002F..\u002Fscripts\u002Frag-perf\u002Fconfigs) are:\n   - `quick_profile.yaml` — profile-only, ~30 s. Skips load test. For fast iteration on retrieval \u002F reranker tuning.\n   - `single_run.yaml` — one concurrency level, profiling + aiperf, ~2 min. Regression checks.\n   - `sweep.yaml` — multi-axis sweep. `load.concurrency`, `rag.vdb_top_k`, `rag.reranker_top_k` are all `int | list[int]`; any of them as a list becomes a sweep axis (Cartesian product).\n\n2. **Edit the preset.** **Required:** replace `rag.collection_names: [\"\u003Ccollection_name>\"]` with a real collection on the deployed ingestor server. Verify the collection exists via `GET \u002Fv1\u002Fcollections` on the ingestor. The placeholder `\u003Ccollection_name>` validates fine but every request will fail at retrieval. Use a copied YAML preset for variants; the CLI surface is intentionally config-only.\n\n3. **Run.** From repo root:\n   ```bash\n   uv run --project scripts\u002Frag-perf rag-perf -c scripts\u002Frag-perf\u002Fconfigs\u002Fsingle_run.yaml\n   ```\n   Same form for the other presets. The CLI accepts only `-c \u002F --config` (required), `--help`, `--version`.\n\n4. **Read stdout.** Every invocation prints, in order: a startup banner, a one-line summary, the **fully resolved config as YAML** (so the run is reproducible from terminal output), per-grid-point progress with the **shlex-joined aiperf command** in copy-pastable form, a **rich per-point summary table** (stage breakdown with bars, citation quality, bottleneck, load-test block), and finally a **side-by-side comparison table** auto-labelled by whichever axis varied. See [`references\u002Foutput-and-analysis.md`](references\u002Foutput-and-analysis.md).\n\n5. **Inspect artifacts.** Layout depends on run shape — flat for single-point + `iterations=1`, nested under `iter_\u003Ci>\u002F\u003Cpoint>\u002F...` otherwise. See [`references\u002Foutput-and-analysis.md`](references\u002Foutput-and-analysis.md) for the full directory tree, file purposes, and how to parse `results.json` \u002F `results.csv` \u002F `report.md`.\n\n6. **Summarise for the user.** When reporting back, follow the playbook in [`references\u002Foutput-and-analysis.md#summarising-results-to-the-user`](references\u002Foutput-and-analysis.md#summarising-results-to-the-user): pick the canonical result file for the run shape, build a headline table (concurrency × top-k axes × TTFT × throughput × bottleneck × citation quality), compute scaling efficiency on sweeps, **always flag** zero citations \u002F non-zero error rate \u002F suspect `llm_ttft_ms` \u002F small-sample p99, and propose a concrete next-experiment YAML.\n\n7. **Tune.** Schema is fully documented in [`docs\u002Fperformance-benchmarking.md`](..\u002F..\u002Fdocs\u002Fperformance-benchmarking.md) and the deeper-dive references below. Common knobs: turn `aiperf.enabled: false` for profile-only mode, increase `load.iterations` for variance estimation, set `load.sleep_between_points_s: 60` for overnight Cartesian sweeps.\n\n## Examples\n\n**Profile-only (quickest signal on retrieval \u002F reranker tuning):**\n\n```bash\nuv run --project scripts\u002Frag-perf rag-perf -c scripts\u002Frag-perf\u002Fconfigs\u002Fquick_profile.yaml\n```\n\nOutput: `rag-perf-results\u002Fquick_profile\u002Frun_\u003Cts>\u002F{profile_report.md, profile_results.json, profiling\u002F}`. The `aiperf_rag_on\u002F` directory is omitted. Filenames are `profile_*` because `aiperf.enabled: false`.\n\n**Single benchmark point with full report:**\n\n```bash\nuv run --project scripts\u002Frag-perf rag-perf -c scripts\u002Frag-perf\u002Fconfigs\u002Fsingle_run.yaml\n```\n\nOutput: flat `run_\u003Cts>\u002F{report.md, results.json, results.csv, profiling\u002F, aiperf_rag_on\u002F}`.\n\n**Concurrency sweep:**\n\n```bash\nuv run --project scripts\u002Frag-perf rag-perf -c scripts\u002Frag-perf\u002Fconfigs\u002Fsweep.yaml\n```\n\nOutput: nested `run_\u003Cts>\u002Fiter_1\u002F\u003CCR:_VDB-K:_RERANKER-K:_…>\u002F{profiling,aiperf_rag_on}\u002F` per point, plus aggregate `report.md` \u002F `results.json` \u002F `results.csv` at the run root.\n\n**Run unit tests:**\n\n```bash\nuv sync --project scripts\u002Frag-perf --extra dev   # one-time, installs pytest-asyncio\nuv run --project scripts\u002Frag-perf python -m pytest tests\u002Funit\u002Ftest_rag_perf\u002F\n```\n\n## Limitations\n\n- The CLI is **config-only**: author or copy YAML to vary a parameter.\n- `load.concurrency` \u002F `rag.vdb_top_k` \u002F `rag.reranker_top_k` accept `int | list[int]`; the validator requires unique list values because each value names a unique point dir.\n- `input.file` and `input.synthetic` follow an XOR rule — both set fails validation. When neither is set, `synthetic` auto-fills with defaults so a bare config still validates.\n- File-based input format is **inferred from extension only** (`.jsonl` or `.csv`); other extensions are rejected.\n- Synthetic generation streams each query to disk as it completes (failure-resilient) but **fails fast on the first LLM error** — partial JSONL is preserved. Re-run after fixing the endpoint.\n- Reasoning models (Nemotron Omni, Qwen-Reasoning) require `synthetic.disable_thinking: true` (the default). Without it the model exhausts the token budget on chain-of-thought and `content` returns empty — the generator now raises with a clear message instead of substituting `reasoning_content` for the answer.\n- aiperf-specific knobs outside the YAML surface (request rate distribution, GPU telemetry config, etc.) require editing `AiperfRunner._base_aiperf_cmd` in `scripts\u002Frag-perf\u002Frag_perf\u002Frunner.py`.\n- Procedural detail lives under **`references\u002F`** to keep this file concise.\n\n## Troubleshooting\n\n| Error \u002F signal | Likely cause | What to do |\n|---|---|---|\n| `Configuration errors in \u003Cyaml>:  •  input  —  ... XOR rule` | Both `input.file` and `input.synthetic` set | Pick one. The XOR validator runs at YAML load time. |\n| `input.file must end in .jsonl or .csv` | Extension other than `.jsonl` \u002F `.csv` | Rename or convert. |\n| `load.concurrency has duplicate values` | e.g. `[2, 2, 4]` | Each concurrency maps to a unique point dir; dedupe. |\n| `warmup_requests must be >= 1` | YAML had `warmup_requests: 0` | aiperf rejects warmup=0; minimum is 1. |\n| `LLM returned empty content (reasoning_content was populated — model exhausted its budget on chain-of-thought; raise min_query_tokens or set synthetic.disable_thinking=true).` | Reasoning model used CoT and ran out of tokens | Set `synthetic.disable_thinking: true` (the default) or raise `min_query_tokens`. |\n| `✗ All N profiling requests failed across M point(s).` + exit 1 | Bad URL, server down, wrong collection | Verify `target.url`, `rag.collection_names` (the `\u003Ccollection_name>` placeholder will hit this). |\n| Per-iteration `⚠ N profiling requests failed` warning, run continues | Some requests timed out \u002F errored mid-run | Check rag-server logs, raise `target.timeout_s`, drop concurrency. |\n| `RuntimeError: Random synthetic query generation failed at query N: ...` | LLM endpoint rejected a request mid-generation | Partial JSONL is at `synthetic.jsonl_output_path`; fix endpoint and re-run with reduced `num_queries`, or point `input.file` at the partial file. |\n| `Citation count (mean): 0` and `Citation relevance score: N\u002FA` for a non-empty deployment | Collection mismatch between `rag.collection_names` and what's actually ingested | Run `curl -s http:\u002F\u002F\u003Cingestor>:8082\u002Fv1\u002Fcollections` to list real collections. |\n| Tests error with `ModuleNotFoundError: No module named 'pytest_asyncio'` | Dev extras missing | `uv sync --project scripts\u002Frag-perf --extra dev`. |\n| CI: `ModuleNotFoundError: No module named 'ruamel'` from `tests\u002Funit\u002Ftest_rag_perf\u002F` | rag-perf package missing from CI venv | Add `uv pip install -e .\u002Fscripts\u002Frag-perf` after the top-level install in the unit-tests job. |\n\n## Gotchas\n\n- **Run from repo root.** Preset configs reference `scripts\u002Frag-perf\u002Fexamples\u002Fqueries.jsonl` and `scripts\u002Frag-perf\u002Fprompts\u002Fdefault_prompts.yaml` with repo-root-relative paths. Running from inside `scripts\u002Frag-perf\u002F` will fail those file lookups.\n- **CLI is config-only.** Edit the YAML or copy a preset for URL, concurrency, collection, and similar fields.\n- **Always edit `rag.collection_names` before the first run.** The presets ship with `[\"\u003Ccollection_name>\"]` as a deliberate placeholder. Validation passes, retrieval fails silently for every request — manifests as `Citation count (mean): 0` everywhere.\n- **`load.concurrency_list`, `rag.vdb_top_k_list`, `rag.reranker_top_k_list`** are read-only properties that normalise scalar-or-list to a list. Use them when reasoning about the grid; the underlying YAML field is whatever the user wrote.\n- **`aiperf.enabled: false` changes filenames.** The top-level outputs become `profile_report.md` \u002F `profile_results.json` \u002F `profile_results.csv`. The aggregate sweep table also suppresses load-test rows and the \"Optimal throughput\" footer.\n- **Resolved-config dump is verbose** (50+ lines) — expected. It's what makes terminal output a self-contained reproducer; don't filter it out in scripts.\n- **The aiperf shell command is logged before each subprocess.** Look for `\\n  $ python -m aiperf profile -m ... --endpoint-type nvidia_rag ...` in stdout — copy-paste runnable for reproducing a single point outside rag-perf.\n- **`--endpoint-type nvidia_rag`** comes from the bundled plugin at `scripts\u002Frag-perf\u002Frag_perf\u002Fplugin\u002Fnvidia_rag.py`. It teaches aiperf about the RAG `\u002Fv1\u002Fgenerate` request shape and parses citations + per-stage `metrics` out of the SSE stream. If aiperf can't resolve `nvidia_rag`, rag-perf needs editable installation in the venv — re-run `uv sync --project scripts\u002Frag-perf` (or `uv pip install -e .\u002Fscripts\u002Frag-perf`).\n- **Sweep-mode point-name collision.** When two points differ only in concurrency (e.g. `[1, 4]` × single `vdb_top_k`), the dir name encodes everything: `CR:1_ISL:50_OSL:512_VDB-K:20_RERANKER-K:4_Model:...`. Cluster \u002F GPU \u002F experiment_name (`output.cluster`, `output.gpu`, `output.experiment_name`) are appended too — useful for diff-friendly artifact paths across machines.\n- **`load.iterations > 1` repeats the entire grid**. Each repetition writes to its own `iter_\u003Ci>\u002F`. Aggregate CSV row count = `n_points × iterations`.\n\n## Source of truth\n\n| Piece | Location |\n|---|---|\n| Driver | [`scripts\u002Frag-perf\u002Frag_perf\u002Fcli.py`](..\u002F..\u002Fscripts\u002Frag-perf\u002Frag_perf\u002Fcli.py) (`main` is the single Click command) |\n| Schema | [`scripts\u002Frag-perf\u002Frag_perf\u002Fconfig.py`](..\u002F..\u002Fscripts\u002Frag-perf\u002Frag_perf\u002Fconfig.py) (`RunConfig` and sub-models) |\n| Orchestrator | [`scripts\u002Frag-perf\u002Frag_perf\u002Frunner.py`](..\u002F..\u002Fscripts\u002Frag-perf\u002Frag_perf\u002Frunner.py) (`BenchmarkRunner.run`, `RagProfiler`, `AiperfRunner`) |\n| aiperf plugin | [`scripts\u002Frag-perf\u002Frag_perf\u002Fplugin\u002Fnvidia_rag.py`](..\u002F..\u002Fscripts\u002Frag-perf\u002Frag_perf\u002Fplugin\u002Fnvidia_rag.py) |\n| User-facing doc | [`docs\u002Fperformance-benchmarking.md`](..\u002F..\u002Fdocs\u002Fperformance-benchmarking.md) |\n| Presets | [`scripts\u002Frag-perf\u002Fconfigs\u002F{quick_profile,single_run,sweep}.yaml`](..\u002F..\u002Fscripts\u002Frag-perf\u002Fconfigs\u002F) |\n| Sample queries | [`scripts\u002Frag-perf\u002Fexamples\u002Fqueries.jsonl`](..\u002F..\u002Fscripts\u002Frag-perf\u002Fexamples\u002Fqueries.jsonl) |\n| Synthetic prompts | [`scripts\u002Frag-perf\u002Fprompts\u002Fdefault_prompts.yaml`](..\u002F..\u002Fscripts\u002Frag-perf\u002Fprompts\u002Fdefault_prompts.yaml) |\n| Config schema details | [`references\u002Fconfig-schema.md`](references\u002Fconfig-schema.md) |\n| Synthetic-query generation | [`references\u002Fsynthetic-generation.md`](references\u002Fsynthetic-generation.md) |\n| Output layout & metric semantics | [`references\u002Foutput-and-analysis.md`](references\u002Foutput-and-analysis.md) |\n\n## Agent playbook\n\n1. **Sync deps:** `uv sync --project scripts\u002Frag-perf` (one-time per checkout).\n2. **Pick & customise a preset:** copy `scripts\u002Frag-perf\u002Fconfigs\u002F\u003Cpreset>.yaml` if you want a variant; always set `rag.collection_names` to a real collection.\n3. **Run:** `uv run --project scripts\u002Frag-perf rag-perf -c \u003Cconfig>` from repo root.\n4. **Read the per-point + aggregate tables on stdout.** Bottleneck inference is in the per-point profiling section; comparison across points is the final aggregate table.\n5. **Parse artifacts** under `output.dir\u002Frun_\u003Cts>\u002F` — see [`references\u002Foutput-and-analysis.md`](references\u002Foutput-and-analysis.md). For multi-point runs, `results.csv` has one row per (point × iteration).\n6. **Summarise for the user** using the playbook in [`references\u002Foutput-and-analysis.md#summarising-results-to-the-user`](references\u002Foutput-and-analysis.md#summarising-results-to-the-user) — headline table, scaling-efficiency math for sweeps, mandatory flags for zero citations \u002F non-zero errors \u002F suspect `llm_ttft_ms` \u002F low sample size, and a concrete next-experiment YAML.\n7. **Tune retrieval \u002F reranker:** flip to `quick_profile.yaml` or `aiperf.enabled: false` for fast iteration, then return to `single_run.yaml` \u002F `sweep.yaml` when characterising under load.\n8. **Triage failures:** see Troubleshooting above and [`references\u002Foutput-and-analysis.md`](references\u002Foutput-and-analysis.md) for empty-citation \u002F bottleneck=N\u002FA patterns.\n\n\u003C!-- MCP:START -->\n\n\u003C!-- PORTABILITY:START -->\n## Cross-Client Portability\n\nThis skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.\n\n- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the\n  workflow in project instructions when folder discovery is unavailable.\n- Claude Code: keep the folder in a local skills directory or a compatible plugin source.\n- Codex: install or sync the folder into\n  `$CODEX_HOME\u002Fskills\u002Frag-perf` and restart Codex after major changes.\n\n\u003C!-- PORTABILITY:END -->\n\n## MCP Availability And Fallback\n\nPreferred MCP Server: None required\n\n- Fallback prompt: \"Use the RAG-Perf — config-driven perf benchmark CLI skill without MCP. Rely on its local instructions, bundled resources, standard shell or editor tools, and direct verification. Show the evidence used before concluding.\"\n- Do not claim an MCP operation was used when the active host does not expose it.\n- Treat local files, tests, rendered outputs, logs, or screenshots as the fallback evidence path.\n\n\u003C!-- MCP:END -->\n\n## Anti-Patterns\n\n- Optimizing before recording a baseline: Without a starting point, there is no trustworthy performance story.\n- Using toy traffic to justify production tuning: Tiny prompts or empty corpora hide the real bottleneck.\n- Accepting lower answer quality as an untracked side effect of a latency win.\n\n## Verification Protocol\n\nBefore claiming \"skill applied successfully\":\n\n1. Pass\u002Ffail: The performance investigation starts from a named baseline and a concrete bottleneck hypothesis.\n2. Pass\u002Ffail: The workload shape, corpus size, and concurrency assumptions match the path being optimized.\n3. Pass\u002Ffail: Any latency or throughput claim is paired with a correctness or quality guardrail.\n4. Pressure-test scenario: Re-run the workflow on a retrieval stack that speeds up only because caching masked a stale index.\n5. Success metric: The user gets a reproducible benchmark path and a tuning change that improves the intended metric without hidden regressions.\n\n## Related Skills\n\n- [devops-tooling](..\u002Fdevops-tooling\u002FSKILL.md): Use it when the performance work also needs container, CI, or infrastructure diagnostics.\n- [cloud-design-patterns](..\u002Fcloud-design-patterns\u002FSKILL.md): Use it when bottlenecks reveal larger scaling or architecture tradeoffs.\n- [documentation-verification](..\u002Fdocumentation-verification\u002FSKILL.md): Use it when benchmark claims must be published or preserved in repo docs.\n","# RAG-Perf — config-driven perf benchmark CLI\n\n## Purpose\n\nDrive a deployed NVIDIA RAG Blueprint server with a YAML config, run a server-side **profiling pass** (per-stage timing, citation quality, bottleneck inference) and an optional **aiperf load test** (TTFT \u002F E2E \u002F token & request throughput \u002F error rate), and write a unified report. The CLI is intentionally minimal: `rag-perf -c \u003Cconfig>` plus `--help` \u002F `--version`. Behaviour is *fully* config-driven; field variations belong in YAML.\n\n## Scope\n\n- **Accuracy \u002F RAGAS** scoring of answer quality → use the **rag-eval** skill.\n- **Deploying, repairing, or configuring services** (compose, helm, NIM env vars) → use the **rag-blueprint** skill.\n- **Production monitoring \u002F alerting** — rag-perf is a one-shot benchmark tool.\n- **Runtime requirement:** a deployed RAG server reachable on the network.\n\n## Prerequisites\n\n- Repo cloned; **run commands from the repo root** (config paths in the presets are repo-root-relative).\n- Python **3.11+** and **uv** on PATH.\n- Install rag-perf into its own uv-managed venv: `uv sync --project scripts\u002Frag-perf`.\n- For unit tests: install dev extras as well — `uv sync --project scripts\u002Frag-perf --extra dev` (otherwise `pytest-asyncio` is missing and async tests error out at collection time).\n- A reachable RAG server (default `http:\u002F\u002Flocalhost:8081`). For the aiperf phase, the bundled `nvidia_rag` endpoint plugin must be installed — `pip install -e .\u002Fscripts\u002Frag-perf` registers it via the `aiperf.plugins` entry point.\n- For **synthetic** queries: an OpenAI-compatible chat-completions endpoint reachable at `synthetic.llm_url` (default `http:\u002F\u002Flocalhost:8999\u002Fv1\u002Fchat\u002Fcompletions`).\n- rag-perf itself runs without `NVIDIA_API_KEY` (unlike rag-eval). The synthetic LLM endpoint may require its own auth — that's the deployment's concern.\n\n## Instructions\n\n1. **Pick a preset.** The three under [`scripts\u002Frag-perf\u002Fconfigs\u002F`](..\u002F..\u002Fscripts\u002Frag-perf\u002Fconfigs) are:\n   - `quick_profile.yaml` — profile-only, ~30 s. Skips load test. For fast iteration on retrieval \u002F reranker tuning.\n   - `single_run.yaml` — one concurrency level, profiling + aiperf, ~2 min. Regression checks.\n   - `sweep.yaml` — multi-axis sweep. `load.concurrency`, `rag.vdb_top_k`, `rag.reranker_top_k` are all `int | list[int]`; any of them as a list becomes a sweep axis (Cartesian product).\n\n2. **Edit the preset.** **Required:** replace `rag.collection_names: [\"\u003Ccollection_name>\"]` with a real collection on the deployed ingestor server. Verify the collection exists via `GET \u002Fv1\u002Fcollections` on the ingestor. The placeholder `\u003Ccollection_name>` validates fine but every request will fail at retrieval. Use a copied YAML preset for variants; the CLI surface is intentionally config-only.\n\n3. **Run.** From repo root:\n   ```bash\n   uv run --project scripts\u002Frag-perf rag-perf -c scripts\u002Frag-perf\u002Fconfigs\u002Fsingle_run.yaml\n   ```\n   Same form for the other presets. The CLI accepts only `-c \u002F --config` (required), `--help`, `--version`.\n\n4. **Read stdout.** Every invocation prints, in order: a startup banner, a one-line summary, the **fully resolved config as YAML** (so the run is reproducible from terminal output), per-grid-point progress with the **shlex-joined aiperf command** in copy-pastable form, a **rich per-point summary table** (stage breakdown with bars, citation quality, bottleneck, load-test block), and finally a **side-by-side comparison table** auto-labelled by whichever axis varied. See [`references\u002Foutput-and-analysis.md`](references\u002Foutput-and-analysis.md).\n\n5. **Inspect artifacts.** Layout depends on run shape — flat for single-point + `iterations=1`, nested under `iter_\u003Ci>\u002F\u003Cpoint>\u002F...` otherwise. See [`references\u002Foutput-and-analysis.md`](references\u002Foutput-and-analysis.md) for the full directory tree, file purposes, and how to parse `results.json` \u002F `results.csv` \u002F `report.md`.\n\n6. **Summarise for the user.** When reporting back, follow the playbook in [`references\u002Foutput-and-analysis.md#summarising-results-to-the-user`](references\u002Foutput-and-analysis.md#summarising-results-to-the-user): pick the canonical result file for the run shape, build a headline table (concurrency × top-k axes × TTFT × throughput × bottleneck × citation quality), compute scaling efficiency on sweeps, **always flag** zero citations \u002F non-zero error rate \u002F suspect `llm_ttft_ms` \u002F small-sample p99, and propose a concrete next-experiment YAML.\n\n7. **Tune.** Schema is fully documented in [`docs\u002Fperformance-benchmarking.md`](..\u002F..\u002Fdocs\u002Fperformance-benchmarking.md) and the deeper-dive references below. Common knobs: turn `aiperf.enabled: false` for profile-only mode, increase `load.iterations` for variance estimation, set `load.sleep_between_points_s: 60` for overnight Cartesian sweeps.\n\n## Examples\n\n**Profile-only (quickest signal on retrieval \u002F reranker tuning):**\n\n```bash\nuv run --project scripts\u002Frag-perf rag-perf -c scripts\u002Frag-perf\u002Fconfigs\u002Fquick_profile.yaml\n```\n\nOutput: `rag-perf-results\u002Fquick_profile\u002Frun_\u003Cts>\u002F{profile_report.md, profile_results.json, profiling\u002F}`. The `aiperf_rag_on\u002F` directory is omitted. Filenames are `profile_*` because `aiperf.enabled: false`.\n\n**Single benchmark point with full report:**\n\n```bash\nuv run --project scripts\u002Frag-perf rag-perf -c scripts\u002Frag-perf\u002Fconfigs\u002Fsingle_run.yaml\n```\n\nOutput: flat `run_\u003Cts>\u002F{report.md, results.json, results.csv, profiling\u002F, aiperf_rag_on\u002F}`.\n\n**Concurrency sweep:**\n\n```bash\nuv run --project scripts\u002Frag-perf rag-perf -c scripts\u002Frag-perf\u002Fconfigs\u002Fsweep.yaml\n```\n\nOutput: nested `run_\u003Cts>\u002Fiter_1\u002F\u003CCR:_VDB-K:_RERANKER-K:_…>\u002F{profiling,aiperf_rag_on}\u002F` per point, plus aggregate `report.md` \u002F `results.json` \u002F `results.csv` at the run root.\n\n**Run unit tests:**\n\n```bash\nuv sync --project scripts\u002Frag-perf --extra dev   # one-time, installs pytest-asyncio\nuv run --project scripts\u002Frag-perf python -m pytest tests\u002Funit\u002Ftest_rag_perf\u002F\n```\n\n## Limitations\n\n- The CLI is **config-only**: author or copy YAML to vary a parameter.\n- `load.concurrency` \u002F `rag.vdb_top_k` \u002F `rag.reranker_top_k` accept `int | list[int]`; the validator requires unique list values because each value names a unique point dir.\n- `input.file` and `input.synthetic` follow an XOR rule — both set fails validation. When neither is set, `synthetic` auto-fills with defaults so a bare config still validates.\n- File-based input format is **inferred from extension only** (`.jsonl` or `.csv`); other extensions are rejected.\n- Synthetic generation streams each query to disk as it completes (failure-resilient) but **fails fast on the first LLM error** — partial JSONL is preserved. Re-run after fixing the endpoint.\n- Reasoning models (Nemotron Omni, Qwen-Reasoning) require `synthetic.disable_thinking: true` (the default). Without it the model exhausts the token budget on chain-of-thought and `content` returns empty — the generator now raises with a clear message instead of substituting `reasoning_content` for the answer.\n- aiperf-specific knobs outside the YAML surface (request rate distribution, GPU telemetry config, etc.) require editing `AiperfRunner._base_aiperf_cmd` in `scripts\u002Frag-perf\u002Frag_perf\u002Frunner.py`.\n- Procedural detail lives under **`references\u002F`** to keep this file concise.\n\n## Troubleshooting\n\n| Error \u002F signal | Likely cause | What to do |\n|---|---|---|\n| `Configuration errors in \u003Cyaml>:  •  input  —  ... XOR rule` | Both `input.file` and `input.synthetic` set | Pick one. The XOR validator runs at YAML load time. |\n| `input.file must end in .jsonl or .csv` | Extension other than `.jsonl` \u002F `.csv` | Rename or convert. |\n| `load.concurrency has duplicate values` | e.g. `[2, 2, 4]` | Each concurrency maps to a unique point dir; dedupe. |\n| `warmup_requests must be >= 1` | YAML had `warmup_requests: 0` | aiperf rejects warmup=0; minimum is 1. |\n| `LLM returned empty content (reasoning_content was populated — model exhausted its budget on chain-of-thought; raise min_query_tokens or set synthetic.disable_thinking=true).` | Reasoning model used CoT and ran out of tokens | Set `synthetic.disable_thinking: true` (the default) or raise `min_query_tokens`. |\n| `✗ All N profiling requests failed across M point(s).` + exit 1 | Bad URL, server down, wrong collection | Verify `target.url`, `rag.collection_names` (the `\u003Ccollection_name>` placeholder will hit this). |\n| Per-iteration `⚠ N profiling requests failed` warning, run continues | Some requests timed out \u002F errored mid-run | Check rag-server logs, raise `target.timeout_s`, drop concurrency. |\n| `RuntimeError: Random synthetic query generation failed at query N: ...` | LLM endpoint rejected a request mid-generation | Partial JSONL is at `synthetic.jsonl_output_path`; fix endpoint and re-run with reduced `num_queries`, or point `input.file` at the partial file. |\n| `Citation count (mean): 0` and `Citation relevance score: N\u002FA` for a non-empty deployment | Collection mismatch between `rag.collection_names` and what's actually ingested | Run `curl -s http:\u002F\u002F\u003Cingestor>:8082\u002Fv1\u002Fcollections` to list real collections. |\n| Tests error with `ModuleNotFoundError: No module named 'pytest_asyncio'` | Dev extras missing | `uv sync --project scripts\u002Frag-perf --extra dev`. |\n| CI: `ModuleNotFoundError: No module named 'ruamel'` from `tests\u002Funit\u002Ftest_rag_perf\u002F` | rag-perf package missing from CI venv | Add `uv pip install -e .\u002Fscripts\u002Frag-perf` after the top-level install in the unit-tests job. |\n\n## Gotchas\n\n- **Run from repo root.** Preset configs reference `scripts\u002Frag-perf\u002Fexamples\u002Fqueries.jsonl` and `scripts\u002Frag-perf\u002Fprompts\u002Fdefault_prompts.yaml` with repo-root-relative paths. Running from inside `scripts\u002Frag-perf\u002F` will fail those file lookups.\n- **CLI is config-only.** Edit the YAML or copy a preset for URL, concurrency, collection, and similar fields.\n- **Always edit `rag.collection_names` before the first run.** The presets ship with `[\"\u003Ccollection_name>\"]` as a deliberate placeholder. Validation passes, retrieval fails silently for every request — manifests as `Citation count (mean): 0` everywhere.\n- **`load.concurrency_list`, `rag.vdb_top_k_list`, `rag.reranker_top_k_list`** are read-only properties that normalise scalar-or-list to a list. Use them when reasoning about the grid; the underlying YAML field is whatever the user wrote.\n- **`aiperf.enabled: false` changes filenames.** The top-level outputs become `profile_report.md` \u002F `profile_results.json` \u002F `profile_results.csv`. The aggregate sweep table also suppresses load-test rows and the \"Optimal throughput\" footer.\n- **Resolved-config dump is verbose** (50+ lines) — expected. It's what makes terminal output a self-contained reproducer; don't filter it out in scripts.\n- **The aiperf shell command is logged before each subprocess.** Look for `\\n  $ python -m aiperf profile -m ... --endpoint-type nvidia_rag ...` in stdout — copy-paste runnable for reproducing a single point outside rag-perf.\n- **`--endpoint-type nvidia_rag`** comes from the bundled plugin at `scripts\u002Frag-perf\u002Frag_perf\u002Fplugin\u002Fnvidia_rag.py`. It teaches aiperf about the RAG `\u002Fv1\u002Fgenerate` request shape and parses citations + per-stage `metrics` out of the SSE stream. If aiperf can't resolve `nvidia_rag`, rag-perf needs editable installation in the venv — re-run `uv sync --project scripts\u002Frag-perf` (or `uv pip install -e .\u002Fscripts\u002Frag-perf`).\n- **Sweep-mode point-name collision.** When two points differ only in concurrency (e.g. `[1, 4]` × single `vdb_top_k`), the dir name encodes everything: `CR:1_ISL:50_OSL:512_VDB-K:20_RERANKER-K:4_Model:...`. Cluster \u002F GPU \u002F experiment_name (`output.cluster`, `output.gpu`, `output.experiment_name`) are appended too — useful for diff-friendly artifact paths across machines.\n- **`load.iterations > 1` repeats the entire grid**. Each repetition writes to its own `iter_\u003Ci>\u002F`. Aggregate CSV row count = `n_points × iterations`.\n\n## Source of truth\n\n| Piece | Location |\n|---|---|\n| Driver | [`scripts\u002Frag-perf\u002Frag_perf\u002Fcli.py`](..\u002F..\u002Fscripts\u002Frag-perf\u002Frag_perf\u002Fcli.py) (`main` is the single Click command) |\n| Schema | [`scripts\u002Frag-perf\u002Frag_perf\u002Fconfig.py`](..\u002F..\u002Fscripts\u002Frag-perf\u002Frag_perf\u002Fconfig.py) (`RunConfig` and sub-models) |\n| Orchestrator | [`scripts\u002Frag-perf\u002Frag_perf\u002Frunner.py`](..\u002F..\u002Fscripts\u002Frag-perf\u002Frag_perf\u002Frunner.py) (`BenchmarkRunner.run`, `RagProfiler`, `AiperfRunner`) |\n| aiperf plugin | [`scripts\u002Frag-perf\u002Frag_perf\u002Fplugin\u002Fnvidia_rag.py`](..\u002F..\u002Fscripts\u002Frag-perf\u002Frag_perf\u002Fplugin\u002Fnvidia_rag.py) |\n| User-facing doc | [`docs\u002Fperformance-benchmarking.md`](..\u002F..\u002Fdocs\u002Fperformance-benchmarking.md) |\n| Presets | [`scripts\u002Frag-perf\u002Fconfigs\u002F{quick_profile,single_run,sweep}.yaml`](..\u002F..\u002Fscripts\u002Frag-perf\u002Fconfigs\u002F) |\n| Sample queries | [`scripts\u002Frag-perf\u002Fexamples\u002Fqueries.jsonl`](..\u002F..\u002Fscripts\u002Frag-perf\u002Fexamples\u002Fqueries.jsonl) |\n| Synthetic prompts | [`scripts\u002Frag-perf\u002Fprompts\u002Fdefault_prompts.yaml`](..\u002F..\u002Fscripts\u002Frag-perf\u002Fprompts\u002Fdefault_prompts.yaml) |\n| Config schema details | [`references\u002Fconfig-schema.md`](references\u002Fconfig-schema.md) |\n| Synthetic-query generation | [`references\u002Fsynthetic-generation.md`](references\u002Fsynthetic-generation.md) |\n| Output layout & metric semantics | [`references\u002Foutput-and-analysis.md`](references\u002Foutput-and-analysis.md) |\n\n## Agent playbook\n\n1. **Sync deps:** `uv sync --project scripts\u002Frag-perf` (one-time per checkout).\n2. **Pick & customise a preset:** copy `scripts\u002Frag-perf\u002Fconfigs\u002F\u003Cpreset>.yaml` if you want a variant; always set `rag.collection_names` to a real collection.\n3. **Run:** `uv run --project scripts\u002Frag-perf rag-perf -c \u003Cconfig>` from repo root.\n4. **Read the per-point + aggregate tables on stdout.** Bottleneck inference is in the per-point profiling section; comparison across points is the final aggregate table.\n5. **Parse artifacts** under `output.dir\u002Frun_\u003Cts>\u002F` — see [`references\u002Foutput-and-analysis.md`](references\u002Foutput-and-analysis.md). For multi-point runs, `results.csv` has one row per (point × iteration).\n6. **Summarise for the user** using the playbook in [`references\u002Foutput-and-analysis.md#summarising-results-to-the-user`](references\u002Foutput-and-analysis.md#summarising-results-to-the-user) — headline table, scaling-efficiency math for sweeps, mandatory flags for zero citations \u002F non-zero errors \u002F suspect `llm_ttft_ms` \u002F low sample size, and a concrete next-experiment YAML.\n7. **Tune retrieval \u002F reranker:** flip to `quick_profile.yaml` or `aiperf.enabled: false` for fast iteration, then return to `single_run.yaml` \u002F `sweep.yaml` when characterising under load.\n8. **Triage failures:** see Troubleshooting above and [`references\u002Foutput-and-analysis.md`](references\u002Foutput-and-analysis.md) for empty-citation \u002F bottleneck=N\u002FA patterns.\n\n\u003C!-- MCP:START -->\n\n\u003C!-- PORTABILITY:START -->\n## Cross-Client Portability\n\nThis skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.\n\n- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the\n  workflow in project instructions when folder discovery is unavailable.\n- Claude Code: keep the folder in a local skills directory or a compatible plugin source.\n- Codex: install or sync the folder into\n  `$CODEX_HOME\u002Fskills\u002Frag-perf` and restart Codex after major changes.\n\n\u003C!-- PORTABILITY:END -->\n\n## MCP Availability And Fallback\n\nPreferred MCP Server: None required\n\n- Fallback prompt: \"Use the RAG-Perf — config-driven perf benchmark CLI skill without MCP. Rely on its local instructions, bundled resources, standard shell or editor tools, and direct verification. Show the evidence used before concluding.\"\n- Do not claim an MCP operation was used when the active host does not expose it.\n- Treat local files, tests, rendered outputs, logs, or screenshots as the fallback evidence path.\n\n\u003C!-- MCP:END -->\n\n## Anti-Patterns\n\n- Optimizing before recording a baseline: Without a starting point, there is no trustworthy performance story.\n- Using toy traffic to justify production tuning: Tiny prompts or empty corpora hide the real bottleneck.\n- Accepting lower answer quality as an untracked side effect of a latency win.\n\n## Verification Protocol\n\nBefore claiming \"skill applied successfully\":\n\n1. Pass\u002Ffail: The performance investigation starts from a named baseline and a concrete bottleneck hypothesis.\n2. Pass\u002Ffail: The workload shape, corpus size, and concurrency assumptions match the path being optimized.\n3. Pass\u002Ffail: Any latency or throughput claim is paired with a correctness or quality guardrail.\n4. Pressure-test scenario: Re-run the workflow on a retrieval stack that speeds up only because caching masked a stale index.\n5. Success metric: The user gets a reproducible benchmark path and a tuning change that improves the intended metric without hidden regressions.\n\n## Related Skills\n\n- [devops-tooling](..\u002Fdevops-tooling\u002FSKILL.md): Use it when the performance work also needs container, CI, or infrastructure diagnostics.\n- [cloud-design-patterns](..\u002Fcloud-design-patterns\u002FSKILL.md): Use it when bottlenecks reveal larger scaling or architecture tradeoffs.\n- [documentation-verification](..\u002Fdocumentation-verification\u002FSKILL.md): Use it when benchmark claims must be published or preserved in repo docs.\n",{"name":5,"tags":24,"license":15,"version":31,"description":7,"last_updated":32,"compatibility":33},[25,26,27,28,29,30],"nvidia","rag","performance","latency","throughput","profiling","2.0",1788825600000,"Guidance imported from the NVIDIA RAG Blueprint performance skill for current benchmark and profiling workflows.","master","fd76f882a04e445e899d5cfb2732f2105ea054ee","skills\u002Fagent-skills\u002Frag-perf",0,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS","https:\u002F\u002Fbg-szy.github.io\u002FTOP-SKILLS\u002F","https:\u002F\u002Fgithub.com\u002Fbg-szy","https:\u002F\u002Fwww.ecust.edu.cn\u002F","a student of East China University of Science and Technology","2026-11-15 03:38:02",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill rag-perf",{"tool":50,"command":51},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill rag-perf",{"tool":53,"command":54},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill rag-perf","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fagent-skills\u002Frag-perf\u002FSKILL.md",true,[58,64,68,72],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"BENCHMARK.md","REFERENCE","参考文档",2672,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fagent-skills\u002Frag-perf\u002FBENCHMARK.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"CHANGELOG.md",5039,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fagent-skills\u002Frag-perf\u002FCHANGELOG.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"skill-card.md",2750,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fagent-skills\u002Frag-perf\u002Fskill-card.md",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"skill.oms.sig","OTHER","其他",5549,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fagent-skills\u002Frag-perf\u002Fskill.oms.sig",[79,88,95,102,109,116],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":87},"01M7DXW9N826PKXK174PVW3038","serpmaven","Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.","MIT","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fserpmaven\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":87},"01M7DXVHSTWDV65475QEQ915M7","revnu-landing-page-audit","Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: \"audit my landing page\", \"why isn't this page converting\", \"review my homepage\", \"my ads get clicks but no signups\", \"people bounce from the pricing page\", \"CRO review\", \"improve conversion rate\", \"is my hero section clear\", \"roast my landing page\", \"rewrite my headline\", \"what's wrong with this page\", \"landing page feedback\", \"make the signup page convert better\". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-landing-page-audit\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":87},"01M7DXV8X2D7B3VTD4HHYYHTGR","revnu-growth-context","Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents\u002Frevnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says \"set up our marketing context\", \"who is our ideal customer\", \"write our ICP\", \"describe the product for marketing\", \"positioning doc\", \"what's our brand voice\", \"remember this about our customers\", \"log what we tried\", \"what have we learned from marketing\", \"we changed pricing, update the context\", \"update our growth notes\", \"summarize the business for the agent\", \"import my product-marketing.md\", \"start a growth doc\", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-growth-context\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":87},"01M7DXV0DGJ1G0A60PAHC6J3C5","revnu-get-listed","Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: \"best X\" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says \"get us listed\", \"which directories should we submit to\", \"how do we get into best-of lists\", \"why does ChatGPT recommend competitors and not us\", \"get mentioned in AI answers\", \"submit to awesome lists\", \"get on G2\", \"where are our competitors listed\", \"pitch listicle authors\", \"find backlink opportunities\", \"launch directories\", \"get into roundups\", \"Product Hunt alternatives\", \"where should we be listed\", \"get cited by Perplexity\". Never submits, pays or posts without a yes. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-get-listed\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":87},"01M7DXTSPMGT9D6DSS0HP9BSTA","revnu-ai-readiness-audit","Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks \"is my site ready for AI search\", \"audit my site for AI answers\", \"AEO audit\", \"GEO audit\", \"why doesn't ChatGPT quote our pricing\", \"make our pages citable by AI\", \"do I need llms.txt\", \"does schema help with ChatGPT\", \"check our structured data\", \"is our content visible without JavaScript\", \"AI SEO audit\", \"optimize our homepage for AI answers\", \"LLM SEO check\", \"why does AI get our product wrong\", \"fix our site for AI Overviews\". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-ai-readiness-audit\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":87},"01M7DXSZHCVTRS620GC3S97JZV","proxy-troubleshooting","Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fproxy-troubleshooting\u002FSKILL.md",[],[]]