← ClaudeAtlas

robotframeworklisted

Use this skill for general Robot Framework work: authoring `.robot` suites, tasks, keywords, variables, resource files, execution, dry runs, tags, Rebot/Libdoc usage, and Python test-library patterns. Trigger when the user mentions Robot Framework, `.robot` files, keywords, libraries, resource files, tasks, listeners, Libdoc, Rebot, or Robot Framework syntax and execution.
bayeslearner/bayeslearner-skills · ★ 0 · AI & Automation · score 65
Install: claude install-skill bayeslearner/bayeslearner-skills
# Robot Framework Use this skill for general Robot Framework authoring, refactoring, execution, and Python library work. This is the broad Robot Framework skill. It is not `wise-rpa-bdd`, which is for browser-extraction-oriented BDD/RPA suites with a fixed generic-keyword contract. ## Start Here Classify the task first: 1. **Suite work**: write or refactor `.robot` suites 2. **Keyword design**: extract or reshape user keywords and resources 3. **Execution**: run `robot`, `--dryrun`, tags, Rebot, pabot 4. **Library work**: create or edit Python libraries 5. **Framework extension**: listeners, remote libraries, dynamic APIs Pick the narrowest layer that solves the problem. ## Strong Defaults - Prefer `.robot` suites plus resource files before Python libraries. - Prefer high-level user keywords over repeated low-level calls. - Prefer `*** Test Cases ***` unless the work is genuinely task/RPA shaped. - Prefer `Test Template` when many rows share one interaction shape. - Prefer `robot --dryrun` as the first validation step. - Prefer Python libraries when suite logic starts hiding business intent. ## Core Model Choose the right layer: - **suite file**: scenario intent and visible assertions - **resource file**: shared domain flows, imports, and reusable keywords - **Python library**: external-system mechanics, parsing, retries, heavy logic If the suite starts reading like general-purpose program code, move logic down into Python. ## What Good Looks Like Good Robot Fra