{
  "skill_name": "browser-testing-with-devtools",
  "evals": [
    {
      "id": 1,
      "name": "basic-invocation",
      "prompt": "Apply the browser-testing-with-devtools skill to the following task: implement a user authentication feature with JWT tokens in a Node.js Express app.",
      "expected_output": "Output that follows the browser-testing-with-devtools skill's guidance, including its key sections and recommendations.",
      "assertions": [
        "The output references or follows browser-testing-with-devtools guidance",
        "The output follows a structured process or workflow",
        "The output is specific, not generic"
      ]
    },
    {
      "id": 2,
      "name": "ambiguous-input",
      "prompt": "The codebase is messy and needs cleanup. Apply the browser-testing-with-devtools skill.",
      "expected_output": "The skill handles vague input by either asking clarifying questions or providing bounded guidance.",
      "assertions": [
        "The output does not hallucinate specific technologies not mentioned",
        "The output is scoped to the skill's intended use case",
        "The output is actionable rather than purely descriptive"
      ]
    },
    {
      "id": 3,
      "name": "complex-scenario",
      "prompt": "A large enterprise team needs to adopt the practices from the browser-testing-with-devtools skill across 5 microservices with different tech stacks. How should they apply it?",
      "expected_output": "The skill scales its guidance to a multi-team, multi-service context without losing specificity.",
      "assertions": [
        "The output addresses complexity without being vague",
        "The output provides concrete next steps",
        "The output acknowledges tradeoffs"
      ]
    }
  ]
}