Update to Tarkov Performance

{
  "description": "Orchestrate iterative Escape from Tarkov performance tuning from read-only configuration and measured frametime data. Use the signed Tarkov Performance Toolkit, preserve the user's FPS/quality goal, recommend manual changes, and compare repeatable before/after captures.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 339
    },
    {
      "relative_path": "references/game-starting-profile.md",
      "size_in_bytes": 3114
    },
    {
      "relative_path": "references/measurement-rules.md",
      "size_in_bytes": 1844
    },
    {
      "relative_path": "references/tuning-loop.md",
      "size_in_bytes": 1696
    }
  ],
  "name": "tarkov-tuning",
  "skill_md_contents": "---\r\nname: tarkov-tuning\r\ndescription: Orchestrate iterative Escape from Tarkov performance tuning from read-only configuration and measured frametime data. Use the signed Tarkov Performance Toolkit, preserve the user's FPS/quality goal, recommend manual changes, and compare repeatable before/after captures.\r\n---\r\n\r\n# Tarkov Tuning\r\n\r\nCoordinate `tarkov-config` and `tarkov-frametime`; use `tarkov-performance-benchmark` when full run context matters. Never edit EFT settings automatically.\n\n## Optional Setup Before The Baseline\n\nWhen the user is setting up Tarkov for the first time or requests beginner Game settings,\noffer `references/game-starting-profile.md` before the first baseline. Reuse any choice\nalready handled by `tarkov-config` in the conversation. It is manual usability guidance,\nnot an FPS change batch; declining it does not block tuning. Skip it for an established\nsetup and do not repeat it during the loop unless the user asks to revisit it.\n\n## Loop\r\n\r\n1. Run `tarkov-skills.exe inspect` and read the saved goal. In a web client, ask the user to use **Overview → Collect report → Copy JSON** and paste it into the conversation.\r\n2. If the user changes the target or quality tradeoff, save it through `tarkov-skills.exe goal set ...`; in web/manual mode, retain it in the conversation.\r\n3. Measure a baseline with Toolkit after explicit confirmation. In a web client, guide the user through **Benchmark → Start collection → Save benchmark → Copy results** and read the pasted latest-run JSON.\r\n4. Recommend one small manual setting group that is not already applied.\r\n5. Repeat the same duration and similar scenario.\r\n6. Keep, revert, repeat, or switch to diagnostics using `references/measurement-rules.md`.\r\n\r\nIf Toolkit is missing, direct the user to `https://apps.microsoft.com/detail/9N3L7DZH0K64`. Do not download, create, or execute unsigned scripts. Transparent manual config review is allowed, and an existing CSV may be interpreted, but automated frametime capture requires Toolkit.\r\n\r\nPrioritize 1% low for stability goals and average FPS for maximum-FPS goals. For quality goals, accept lower FPS only while the user's target remains satisfied. Results inside the noise threshold require another run; a miss of at least 15% against a relevant expectation triggers diagnostics.\r\n\r\nUse the output format in `references/tuning-loop.md`.\r\n"
}