casely
Generate QA Test Cases from Requirements
QA teams spend significant time converting requirements into consistent test cases. Casely parses project documents, learns example formats, and exports structured cases.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "casely" from https://skillstore.io/skills/johnwayneeee-casely.md and its manifest at https://skillstore.io/api/skills/johnwayneeee-casely/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "casely". A QA engineer starts a BillingPortal project with requirement PDFs and example Excel cases.
Expected outcome:
- Project folders are created.
- The assistant tells the user where to place files.
- The next step suggests parsing documents.
Using "casely". A team asks for negative test cases for password reset requirements.
Expected outcome:
Casely creates separate Markdown cases, each with one table row that matches the style guide.
Using "casely". A test manager exports generated login cases.
Expected outcome:
The export folder receives one Excel file per test case with the original columns preserved.
Security Audit
Medium RiskMost static findings are false positives caused by Markdown backticks around slash commands, file names, and paths. The real concerns are package-manager execution, unpinned dependency installation, and bundled script execution for parsing and export workflows.
Confirmed security concerns (1)
Capability review items (7)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
โ๏ธ External commands (50)
๐ Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/johnwayneeee-casely/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/johnwayneeee-casely?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/johnwayneeee-casely?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/johnwayneeee-casely/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/johnwayneeee-casely.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
JohnWayneeee. (2026). casely security audit report (audit version 6) [Author version 1.5.0]. Skillstore. https://skillstore.io/skills/johnwayneeee-casely/audits/6BibTeX citation
@techreport{johnwayneeee-johnwayneeee-casely-2026,
author = {JohnWayneeee},
title = {casely security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/johnwayneeee-casely/audits/6},
note = {Author version 1.5.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "casely security audit report (audit version 6)"
version: "1.5.0"
type: report
authors:
- name: "JohnWayneeee"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/johnwayneeee-casely/audits/6"
identifiers:
- type: other
value: "skillstore:johnwayneeee-casely:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Standardize Release Test Cases
Derive columns and writing style from approved examples before generating cases for a release.
Draft Cases from Requirements
Turn product requirements into functional, negative, boundary, and integration cases with less repetitive writing.
Prepare TMS Import Files
Create Excel-ready case files while preserving one scenario per source file.
Try These Prompts
Initialize a new Casely project named BillingPortal and tell me where to place requirements and examples.
Parse the latest project documents and summarize which files were converted, skipped, or failed.
Analyze my example cases, create the style guide, then plan critical coverage for the checkout module.
Generate negative and integration cases for the payment retry flow, then export the results to Excel.
Best Practices
- Review the generated style guide before generating cases.
- Use representative example cases with the exact columns your team needs.
- Generate critical cases first, then expand to negative, boundary, and integration coverage.
Avoid
- Do not generate cases before parsing requirements and approving the style guide.
- Do not mix unrelated modules in one generation request.
- Do not import exported files into a TMS without a QA review.
Frequently Asked Questions
What does Casely generate?
Can it read PDF, DOCX, and XLSX files?
Does it create one large test suite file?
Can it match our test format?
Does it run commands on my machine?
Is generated content ready to import?
Developer Details
Author
JohnWayneeeeLicense
MIT
Author version
v1.5.0
Skillstore revision
r1
Ref
0519034dad657fb1f7706e0550e962beeda73fdf
Maintenance freshness
7/18/2026
Usage
73 downloads ยท 183 views
File structure
๐ evals/
๐ evals.json
๐ references/
๐ export_guide.md
๐ parser_usage.md
๐ style_analysis_prompts.md
๐ scripts/
๐ casely_parser.py
๐ export_to_xlsx.py
๐ SKILL.md