Update to Kilotest

{
  "description": "Kilotest uses an ensemble of 12 rule engines to test web pages for front-end quality, including accessibility, usability, and web standards such as HTML, CSS, ARIA, and WCAG. Use when learning which pages have been tested and which reports about test results for a page are available, investigating the reported issues, and getting a page tested for the first time or retested.",
  "included_files": [],
  "name": "kilotest-overview",
  "skill_md_contents": "---\nname: kilotest-overview\ndescription: Kilotest uses an ensemble of 12 rule engines to test web pages for front-end quality, including accessibility, usability, and web standards such as HTML, CSS, ARIA, and WCAG. Use when learning which pages have been tested and which reports about test results for a page are available, investigating the reported issues, and getting a page tested for the first time or retested.\n---\n\n# Kilotest overview and workflow\n\nKilotest tests web pages for front-end quality: accessibility, usability, and web standards, including HTML, CSS, ARIA, and WCAG.\n\nKilotest integrates an ensemble of 12 independent rule engines to test a web page and stores the results as a structured report, from which it exposes results at selectable granularities.\n\n## Report hierarchy\n\nResults are organized as a hierarchy:\n\n- Tested pages.\n- For each tested page, reports from the tests of the page.\n- For each report, issues reported.\n- For each issue, violators of rules belonging to the issue (a violator is an element or the whole page).\n- For each violator, diagnoses by rule engines of its violations.\n\n## Typical workflow\n\n1. Call `listPages` to determine whether the page has been tested.\n2. If it has been tested:\n   - Use `listIssues` to identify reports about the page and summarize the issues reported by one report.\n   - Use `listViolators` to inspect elements violating rules belonging to an issue.\n   - Use `listDiagnoses` to inspect diagnoses by rule engines of violations of applicable rules by an element.\n   - Use `getReport` to retrieve an entire JSON report.\n   - Use `requestRetest` or `orderRetest` if the latest report is obsolete and you want the page retested.\n3. If the page has not been tested:\n   - Use `requestNewTest` or `orderNewTest` if you want the page tested.\n\n## Test request and order processing\n\nA test or retest **request** is reviewed by a manager. If approved, the testing is typically performed within a day.\n\nA test or retest **order** is reviewed automatically and immediately. If it is approved, you get a report identifier. You can then use `awaitTest`, with the identifier, to await test completion, which typically takes 2 to 4 minutes, or you can later use `listIssues` with the identifier to check the status.\n\n## Reporting to users\n\nWhen reporting test results to users:\n\n- Do not assume a requested or ordered test or retest has produced a report until Kilotest confirms this.\n- You may quote the Kilotest classification of issues into priorities, but identify any additional prioritization recommendations as your own.\n- You may quote recommendations for remediation made by rule engines in diagnoses, but identify any additional remediation recommendations as your own.\n\n## Further documentation\n\n- https://kilotest.com/llms.txt\n- https://kilotest.com/llms-full.txt\n"
}