Agent skill · operations · aiskillstore
casely
Intelligent QA assistant that automates writing test cases from project documentation. Use when the user wants to generate test cases from requirements, runs /init, /parse, /style, /plan, /generate, /export, or works with PDF/DOCX/XLSX requirement documents and TestRail-ready Excel export.
Why this skill is useful
Adds executable scripts for parsing and generating test cases from various document formats, which the AI cannot generate on its own.
What it needs
Requires docling, openpyxl, uv installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Casely — QA Test Case Generator Casely automates the most time-consuming part of a QA engineer's job: writing test cases. It reads requirement documents and learns from your team's existing test case examples to produce structured, style-consistent test suites ready for import into any Test Management System. Why this matters Manual test case writing accounts for ~40% of a QA engineer's time. Requirements come in fragmented formats (PDF, DOCX, XLSX). Every team has its own column structure, naming conventions, and writing style. Casely solves this by: Converting any document format to clean Markdown via docling. Extracting formal style rules from your team's example test cases. Generating test cases that match your team's exact structure and tone. Exporting to Excel with correct column mapping for TMS import. --- Commands /init [ProjectName] Creates a new isolated project workspace and verifies the environment. /parse Runs the CaselyParser to convert all raw assets (requirements and examples) to Markdown. /style Analyzes example test cases and generates a persistent teststyleguide.md. /plan Scans parsed requirements and suggests a testing plan with modules and test types. /generate [type] Generates atomic test cases of the specified type (functional, negative, integration, boundary, etc.). /export Converts generated Markdown test cases into a formatted .xlsx file. --- Full Workflow Phase 1: Project Initialization & Environment Setup (/init) When the user runs /init [ProjectName] (or asks to start a new testing project): 1. Create Directories: Create the project directory structure under projects/ in the repository root: input/requirements/ input/examples/ processed/requirements/ processed/examples/ results/ exports/ 2. Environment Setup via uv: Location: Dependencies are defined in pyproject.toml at the repository root (not inside the skill folder). Scripts expect uv sync to have been run from that root. Check if pyproject.toml exists at the repo root. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/casely