by ShaftHQ
Java test automation framework for web, mobile, API, CLI, database, and desktop E2E testing with a fluent API and built-in reporting.
# Add to your Claude Code skills
git clone https://github.com/ShaftHQ/SHAFT_ENGINEGuides for using mcp servers skills like SHAFT_ENGINE.
Last scanned: 6/23/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-06-23T07:49:19.138Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}See how SHAFT_ENGINE compares with popular alternatives.
SHAFT_ENGINE is an open-source mcp servers skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by ShaftHQ. Java test automation framework for web, mobile, API, CLI, database, and desktop E2E testing with a fluent API and built-in reporting. It has 414 GitHub stars.
Yes. SHAFT_ENGINE passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/ShaftHQ/SHAFT_ENGINE" and add it to your Claude Code skills directory (see the Installation section above).
SHAFT_ENGINE is primarily written in Java. It is open-source under ShaftHQ on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other MCP Servers skills you can browse and compare side by side. Open the MCP Servers category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh SHAFT_ENGINE against similar tools.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
30 days in the Featured rail · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
Reliable Java test automation, from first intent to production-grade evidence.
SHAFT is a Java test-automation framework for teams who want one maintainable engine across web, mobile, API, CLI, database, and desktop. Configuration drives the run. The verdict comes back with logs, screenshots, and a report.
Generate your first project · Read the user guide · Watch the 100-second overview · Star SHAFT on GitHub
SHAFT is for Java teams who are about to rebuild drivers, waits, assertions,
configuration, test data, and Allure plumbing again. Generate a project from
the user guide, then run mvn test. The
100-second overview
and the feature video release
are the short tour; the badge above is the current version, and
releases hold history.
Humans: orient here, then CONTRIBUTING.md. Report vulnerabilities through SECURITY.md.
Agents: jump to For agents. This README is orientation, not agent policy.
Use coordinate io.github.shafthq:shaft-engine. Set the version from the Maven Central badge. The generated project is still the supported first run. Kotlin uses the same coordinate.
<dependency>
<groupId>io.github.shafthq</groupId>
<artifactId>shaft-engine</artifactId>
<version>${shaft.version}</version>
</dependency>
Each reactor module and shaft-intellij has a short README with a purpose line and a use-or-skip note.
SHAFT removes the repeated plumbing around drivers, waits, assertions, configuration, test data, screenshots, logs, and Allure evidence. The modular reactor keeps the core lean.
shaft-engine, then add visual, video, cloud, native, or agentic modules.Test intent and configuration enter SHAFT's orchestration layer, fan out across the required execution surfaces, and return through one unified evidence flow.
flowchart LR
accTitle: SHAFT execution and evidence workflow
accDescr: Test intent and configuration enter SHAFT orchestration, run across Web, Mobile, API, and Native execution surfaces, and produce unified evidence.
I[Test intent] --> S[SHAFT orchestration]
C[Configuration] --> S
S --> W[Web]
S --> M[Mobile]
S --> A[API]
S --> N[Native, CLI, and Database]
W --> E[Unified evidence]
M --> E
A --> E
N --> E
| Engineering need | What SHAFT provides |
|---|---|
| Stable UI automation | Managed Selenium and Appium drivers, synchronized actions, locator builders, screenshots, and accessibility evidence. |
| End-to-end coverage | REST, GraphQL, Database, CLI, and native desktop actions in the same test flow. |
| Trustworthy verdicts | Hard and soft assertions, structured logs, attachments, failure context, and Allure reports. |
| Scalable execution | Configuration-first local, Grid, BrowserStack, LambdaTest, TestNG, JUnit, and Cucumber runs. |
| Maintainable architecture | A focused engine, BOM-aligned optional modules, public extension points, and reusable test assets. |
| Assisted workflows | Capture, Doctor, deterministic Heal, MCP/CLI tools, provider adapters, and an IntelliJ IDEA plugin. |
| You want to | Open |
|---|---|
| Learn the product | User guide |
| Work inside IntelliJ | shaft-intellij |
| Call a tool from an agent | MCP tool names |
| Call a tool from the shell | CLI commands |
| Follow the working policy | AGENTS.md |
chaos-engine/skills/local-agency (dispatch.py --prefer freetoken or OpenAI-compat on :8080).http://127.0.0.1:8000 is READY; not the default on 6GB VRAM laptops.What is SHAFT? A Java framework for web, mobile, API, CLI, database, and desktop end-to-end testing, with one evidence trail.
How do I get a passing run today? Generate a project from the user guide, then run mvn test. Runners are TestNG, JUnit, and Cucumber, local or through Grid, BrowserStack, or LambdaTest.
Where does an agent start? AGENTS.md. Not this file. License: MIT (LICENSE).
This page is a map. It is not the working policy.
$shaft-developer; it routes the job to one specialist.shaft-mcp-tools.md and shaft-cli-commands.md.Open an issue, read CONTRIBUTING.md and the Code of Conduct, and report vulnerabilities privately through SECURITY.md. Star the repository if SHAFT helps your team.
BrowserStack, LambdaTest, Applitools, and JetBrains have provided tooling or open-source program support. This is support for the project, not a claim of financial sponsorship, customer status, or endorsement.
SHAFT is free and MIT licensed. Support maintenance through GitHub Sponsors.