Update to Testkube Skills

{
  "name": "test-discovery",
  "description": "Walk a cloned repository, identify test files by framework and language, and report what was found in either a machine-readable JSON manifest or a human-readable Markdown report. Use when a repository has been cloned locally and you need to know what tests exist, what framework runs them, and what command executes them. The JSON output is consumed by programs (the testworkflow-author skill, cloud-api ingestion, CI); the Markdown output is meant for a person to read and opens cleanly in any plain-text editor. This skill does NOT execute tests, install dependencies, or write any TestWorkflow YAML — it observes and reports.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 218
    },
    {
      "relative_path": "assets/manifest-schema.json",
      "size_in_bytes": 5915
    }
  ],
  "skill_md_contents": "---\nname: test-discovery\ndescription: \"Walk a cloned repository, identify test files by framework and language, and report what was found in either a machine-readable JSON manifest or a human-readable Markdown report. Use when a repository has been cloned locally and you need to know what tests exist, what framework runs them, and what command executes them. The JSON output is consumed by programs (the testworkflow-author skill, cloud-api ingestion, CI); the Markdown output is meant for a person to read and opens cleanly in any plain-text editor. This skill does NOT execute tests, install dependencies, or write any TestWorkflow YAML — it observes and reports.\"\n---\n\n# test-discovery\n\nWalk a cloned repository at the given path, identify the tests inside, and emit a structured JSON manifest describing\nwhat was found. Output goes to stdout as a single JSON document. The consumer is typically the `testworkflow-author`\nskill or the Testkube cloud-api discovery ingestion.\n\nScope:\n- Read-only walk of the local filesystem\n- Detect language and framework from marker files (config, manifest, lock files) and content signals\n- Group findings into suites; a suite is one framework + one working directory\n- Attach evidence + confidence to every suite\n- Report ambiguity via `status: needs_input`; report failures via `status: error`\n\nOut of scope: running tests, installing dependencies, writing TestWorkflow YAML, cloning repos, calling network APIs.\n"
}