Fetches kotlin-testing from affaan-m/everything-claude-code and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/kotlin-testing
Restart Cursor to activate kotlin-testing. Access via /kotlin-testing in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
RED -> Write a failing test first
GREEN -> Write minimal code to pass the test
REFACTOR -> Improve code while keeping tests green
REPEAT -> Continue with next requirement
Step-by-Step TDD in Kotlin
// Step 1: Define the interface/signature// EmailValidator.ktpackage com.example.validator
funvalidateEmail(email: String): Result<String>{TODO("not implemented")}// Step 2: Write failing test (RED)// EmailValidatorTest.ktpackage com.example.validator
import io.kotest.core.spec.style.StringSpec
import io.kotest.matchers.result.shouldBeFailure
import io.kotest.matchers.result.shouldBeSuccess
class EmailValidatorTest :StringSpec({"valid email returns success"{validateEmail("[email protected]").shouldBeSuccess("[email protected]")}"empty email returns failure"{validateEmail("").shouldBeFailure()}"email without @ returns failure"{validateEmail("userexample.com").shouldBeFailure()}})// Step 3: Run tests - verify FAIL// $ ./gradlew test// EmailValidatorTest > valid email returns success FAILED// kotlin.NotImplementedError: An operation is not implemented// Step 4: Implement minimal code (GREEN)funvalidateEmail(email: String): Result<String>{if(email.isBlank())return Result.failure(IllegalArgumentException("Email cannot be blank"))if('@'!in email)return Result.failure(IllegalArgumentException("Email must contain @"))val regex =Regex("^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\\.[A-Za-z]{2,}$")if(!regex.matches(email))return Result.failure(IllegalArgumentException("Invalid email format"))return Result.success(email)}// Step 5: Run tests - verify PASS// $ ./gradlew test// EmailValidatorTest > valid email returns success PASSED// EmailValidatorTest > empty email returns failure PASSED// EmailValidatorTest > email without @ returns failure PASSED// Step 6: Refactor if needed, verify tests still pass
Kotest Spec Styles
StringSpec (Simplest)
class CalculatorTest :StringSpec({"add two positive numbers"{ Calculator.add(2,3) shouldBe 5}"add negative numbers"{ Calculator.add(-1,-2) shouldBe -3}"add zero"{ Calculator.add(0,5) shouldBe 5}})
FunSpec (JUnit-like)
class UserServiceTest :FunSpec({val repository = mockk<UserRepository>()val service =UserService(repository)test("getUser returns user when found"){val expected =User(id ="1", name ="Alice") coEvery { repository.findById("1")} returns expected
val result = service.getUser("1") result shouldBe expected
}test("getUser throws when not found"){ coEvery { repository.findById("999")} returns null shouldThrow<UserNotFoundException>{ service.getUser("999")}}})
BehaviorSpec (BDD Style)
class OrderServiceTest :BehaviorSpec({val repository = mockk<OrderRepository>()val paymentService = mockk<PaymentService>()val service =OrderService(repository, paymentService)Given("a valid order request"){val request =CreateOrderRequest( userId ="user-1", items =listOf(OrderItem("product-1", quantity =2)),)When("the order is placed"){ coEvery { paymentService.charge(any())} returns PaymentResult.Success
coEvery { repository.save(any())} answers {firstArg()}
Implementation Guide
Prerequisites
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
