Agent skill for openQA: write os-autoinst tests and review job results
概览
Agent skills for working with openQA: writing tests and reviewing results. The skills are plain Markdown plus small Python helper scripts, so they work with any coding agent that can read files and run shell commands. Harnesses that implement the Agent Skills format pick up the SKILL.md frontmatter directly. One skill covers both jobs on purpose: they share the openQA model, the failure-triage method, the cloning recipes and most scripts, and they hand over to each other (a review finds a test issue, a verification run needs triage). Tests and evals live outside the skill directory because installers copy the skill directory verbatim. A skill never references files outside its own directory. Requirements: Python 3.9 or newer (standard library only; PyYAML is used when present). Writing to an openQA instance additionally needs openqa-cli / openqa-clone-job and an API key; the bundled scripts only ever read from openQA.
README
以下为原文 README 节选，完整内容请查看原文。
openQA-skill
Agent skills for working with openQA: writing tests and reviewing results.
The skills are plain Markdown plus small Python helper scripts, so they work with any coding agent that can
read files and run shell commands. Harnesses that implement the Agent Skills
format pick up the SKILL.md frontmatter directly.
Skills
| Skill | Use it when | What it does |
|---|---|---|
openqa |
writing, scheduling, running or fixing an openQA test; asking why a job failed; reviewing a job group or build, or someone else’s test PR | Create: test modules for os-autoinst-distri-opensuse or a custom test distribution, needles, YAML schedules, verification runs, pull requests that pass review. Review: triage a failed or incomplete job from its artifacts, sweep a group or build, classify product bug / test issue / infrastructure / sporadic, draft bug reports and comments that openQA parses as references; review someone else’s test PR at the right size. |
One skill covers both jobs on purpose: they share the openQA model, the failure-triage method, the cloning recipes and most scripts, and they hand over to each other (a review finds a test issue, a verification run needs triage).
Layout
skills/openqa/
SKILL.md entry point: shared rules, block routing, core directives
references/ depth, read one section at a time (scripts/refsection.py)
scripts/ helpers that print compact digests and never write to openQA; catalogue in scripts/README.md
agents/ delegation playbooks: role prompts for sub-agents, also usable as standalone session prompts
(their frontmatter is metadata for harnesses that register agents from files)
tests/openqa/ script tests with offline fixtures
tests/repo/ repository gate: frontmatter, size caps (SKILL.md body and lines, file, section, pointer), pointers that resolve and reach, a contents line in long references, content checks, valid evals.json and triggers.json, cited flags
evals/openqa/ evaluation prompts, trigger queries
Tests and evals live outside the skill directory because installers copy the skill directory verbatim. A skill never references files outside its own directory.
Install
Requirements: Python 3.9 or newer (standard library only; PyYAML is used when present). Writing to an openQA
instance additionally needs openqa-cli / openqa-clone-job and an API key; the bundled scripts only ever
read from openQA.
Any harness, with an installer:
npx skills add os-autoinst/openQA-skill --skill openqa -g
gh skill install os-autoinst/openQA-skill openqa --scope user
Without -g / --scope user both install into the current project (./.agents/skills/), for example into a
test-repository checkout.
Manual, tracking the git checkout:
git clone https://github.com/os-autoinst/openQA-skill.git
mkdir -p ~/.agents/skills ~/.claude/skills推荐工具
换一个关键词，或者移除筛选条件。
安装
npx skillfish add os-autoinst/openqa-skill