testcase-builder

A tool for turning structured requirements or user scenarios into Robot Framework test cases. Robot Framework is a readable testing system that describes actions as reusable keywords.

In plain words
What is it for?
Use it to generate keyword-based or template-based tests for workflows such as account creation or login, including browser setup and multiple data rows.
Why use it?
It creates consistent test files from requirements and handles common details such as tags, setup, cleanup, and repeated test data. This avoids formatting each test manually.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/manykarim/robotframework-agentskills/testcase-builder
Any agent
npx skills add manykarim/robotframework-agentskills --skill testcase-builder
Clone the repo
git clone --depth 1 https://github.com/manykarim/robotframework-agentskills

Made for: Claude Code, Codex.

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 618 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.00618
Opus 5 $0.00018 $0.00309
Sonnet 5 $0.00007 $0.00124
Haiku 4.5 $0.00004 $0.00062

Measured 2d ago against content hash 1b0bd5baf0cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

testcase-builder scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/rf-agentskills/skills/testcase-builder/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Robot Framework Test Case Builder

Create test cases in Robot Framework syntax from structured input. Output JSON only.

Input (JSON)

Provide input via --input or stdin. Example:

{
  "style": "keyword-driven",
  "tests": [
    {
      "name": "User can create account",
      "documentation": "Happy path account creation.",
      "tags": ["smoke"],
      "setup": {"keyword": "Open Browser", "args": ["${URL}", "chromium"]},
      "teardown": {"keyword": "Close Browser"},
      "steps": [
        {"keyword": "Go To Sign Up"},
        {"keyword": "Create User", "args": ["${username}", "${role}"]},
        {"keyword": "User Should Be Logged In"}
      ]
    }
  ]
}

Template-driven test:

{
  "style": "template",
  "tests": [
    {
      "name": "Login works",
      "template": "Login Should Succeed",
      "data_rows": [
        ["alice", "pass"],
        ["bob", "pass"]
      ]
    }
  ]
}

Command

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/testcase_builder.py" --input tests.json

Flags

  • --allow-control -- Suppress warnings when control structures (FOR, IF, WHILE, TRY, etc.) appear in test steps. Without this flag the builder emits a warning for each control keyword found, encouraging you to move control logic into user keywords.
  • --input FILE -- Path to the JSON input file (alternative to stdin).
  • --full-suite -- Wrap the output in a *** Test Cases *** section so the artifact is a directly saveable, runnable .robot file. Without it (the default) the artifact is a section fragment — the test case block(s) only, no header — meant to be embedded into an existing suite (e.g. one that already has *** Settings ***/*** Keywords ***).

Timeout support

Add "timeout" to a test object to render a [Timeout] setting:

{
  "name": "Slow Operation",
  "timeout": "30s",
  "steps": [{"keyword": "Long Running Task"}]
}

Output (JSON)

  • artifact: test case block(s). A *** Test Cases *** section fragment by default; a full saveable suite when --full-suite is passed.
  • full_suite: whether the artifact includes the section header.
  • warnings and suggestions

Read the full file on GitHub · 88 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 88 lines · 37 tokens per session scan A 1b0bd5baf0cc

Subscribe to this mod's changes

testcase-builder is a skill published in the GitHub repository manykarim/robotframework-agentskills (30 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 618 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens