kt
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- DevOps
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Manual integration
- External API key
- Not required
- Operating systems
- Docker
- Runtime requirements
- Docker
- Permissions
-
- Read-only
- Shell exec
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: kt
description: Build, test, analyze, or start Docker for a Kotlin project Use when this capability is needed. R…
category: devops
runtime: Docker
---
# kt output preview
## PART A: Task fit
- Use case: Build, test, analyze, or start Docker for a Kotlin project Use when this capability is needed. Resolve project paths from ~/.claude/project-repos.json. A Kotlin project runs entirely locally; runs on Docker. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Kotlin build / test / analyze / docker / Project paths & JDK / Actions” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Build, test, analyze, or start Docker for a Kotlin project Use when this capability is needed. Resolve project paths from ~/.claude/project-repos.json. A Kotlin project runs entirely locally; runs on Docker. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Kotlin build / test / analyze / docker / Project paths & JDK / Actions” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, run shell commands, write/modify files.
Start with a small task and check whether the result follows “Kotlin build / test / analyze / docker / Project paths & JDK / Actions”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: kt
description: Build, test, analyze, or start Docker for a Kotlin project Use when this capability is needed. R…
category: devops
source: tomevault-io/skills-registry
---
# kt
## When to use
- Build, test, analyze, or start Docker for a Kotlin project Use when this capability is needed. Resolve project paths f…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Kotlin build / test / analyze / docker / Project paths & JDK / Actions” and keep inference separate from source facts.
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "kt" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Kotlin build / test / analyze / docker / Project paths & JDK / Actions
rules -> SKILL.md triggers / order / output contract
runtime -> Docker | read files, run shell commands, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Kotlin build / test / analyze / docker
Arguments: $ARGUMENTS
Project paths & JDK
Resolve project paths from ~/.claude/project-repos.json. A Kotlin project
is any registry entry whose root contains build.gradle or build.gradle.kts.
JDK version is per-project and should be declared in the project's
projects/{shortname}.md. Set it before invoking Gradle:
export JAVA_HOME=$(/usr/libexec/java_home -v {version})Actions
build
cd {repo-path} && ./gradlew build -x test
# Multi-module projects:
cd {repo-path} && ./gradlew :{module}:build -x testOn failure, suggest ./gradlew --refresh-dependencies for dependency
errors. For compilation errors, quote the file/line and the offending type.
test
# All tests:
cd {repo-path} && ./gradlew test
# A specific module:
cd {repo-path} && ./gradlew :{module}:test
# A filter (uses JUnit's `--tests`):
cd {repo-path} && ./gradlew test --tests "{filter}"
# Module + filter:
cd {repo-path} && ./gradlew :{module}:test --tests "{filter}"If the project uses TestContainers, ensure Docker is running first.
Report: total / passed / failed / skipped. For failures, show class, method, assertion error, and the first few lines of stack trace.
analyze
Detekt (common):
cd {repo-path} && ./gradlew detekt
cd {repo-path} && ./gradlew :{module}:detekt
cd {repo-path} && ./gradlew detekt --auto-correctktlint (alternative):
cd {repo-path} && ./gradlew ktlintCheck
cd {repo-path} && ./gradlew ktlintFormatReport issues with: rule name, file:line, message, severity.
docker
Starts the project's docker-compose.yml services (Postgres, Redis, any
stub/mock servers):
# All services:
cd {repo-path} && docker compose up -d
# Specific service:
cd {repo-path} && docker compose up -d {service}After start, wait ~5s and check health:
docker compose -f {repo-path}/docker-compose.yml psIf any container is unhealthy:
docker compose logs --tail=20 {service}Common fixes:
- Port conflict:
docker psto find the claimant - Stale volumes:
docker compose down -v && docker compose up -d
Process
- Parse arguments: action, shortname, optional module/filter/flags
- Set JDK (skip for
docker) cdto the resolved project path- Run the command
- Report result
Source: ajvelo/claude-toolkit — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review