Docker Jfr Benchmark Loop
eclipse-rdf4j/rdf4j
Run a repeatable RDF4J performance loop against one JMH benchmark in Docker with Linux Java 26 and JFR CPU-time profiling.
Run or debug the coastline rendering test (CoastlineRenderingTester / utilities.sh test-coastline-rendering) that compares locally rendered tiles against tile.osmand.net and reports water mask…
Install Coastline Rendering Test
$ npx skills add osmandapp/OsmAnd-tools --skill coastline-rendering-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install osmandapp/OsmAnd-tools coastline-rendering-test --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/osmandapp/OsmAnd-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/coastline-rendering-test .claude/skills/coastline-rendering-test && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "coastline-rendering-test" agent skill from https://github.com/osmandapp/OsmAnd-tools/tree/master/.claude/skills/coastline-rendering-test into .claude/skills/coastline-rendering-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coastline-rendering-test", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/osmandapp/OsmAnd-tools/tree/master/.claude/skills/coastline-rendering-testType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add osmandapp/OsmAnd-tools --skill coastline-rendering-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install osmandapp/OsmAnd-tools coastline-rendering-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/osmandapp/OsmAnd-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/coastline-rendering-test .agents/skills/coastline-rendering-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "coastline-rendering-test" agent skill from https://github.com/osmandapp/OsmAnd-tools/tree/master/.claude/skills/coastline-rendering-test into .agents/skills/coastline-rendering-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coastline-rendering-test", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add osmandapp/OsmAnd-tools --skill coastline-rendering-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install osmandapp/OsmAnd-tools coastline-rendering-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/osmandapp/OsmAnd-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/coastline-rendering-test .cursor/skills/coastline-rendering-test && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "coastline-rendering-test" agent skill from https://github.com/osmandapp/OsmAnd-tools/tree/master/.claude/skills/coastline-rendering-test into .cursor/skills/coastline-rendering-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coastline-rendering-test", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/osmandapp/OsmAnd-tools.git --path .claude/skills/coastline-rendering-test--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add osmandapp/OsmAnd-tools --skill coastline-rendering-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install osmandapp/OsmAnd-tools coastline-rendering-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/osmandapp/OsmAnd-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/coastline-rendering-test .gemini/skills/coastline-rendering-test && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "coastline-rendering-test" agent skill from https://github.com/osmandapp/OsmAnd-tools/tree/master/.claude/skills/coastline-rendering-test into .gemini/skills/coastline-rendering-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coastline-rendering-test", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install osmandapp/OsmAnd-tools coastline-rendering-testInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add osmandapp/OsmAnd-tools --skill coastline-rendering-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/osmandapp/OsmAnd-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/coastline-rendering-test .github/skills/coastline-rendering-test && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "coastline-rendering-test" agent skill from https://github.com/osmandapp/OsmAnd-tools/tree/master/.claude/skills/coastline-rendering-test into .github/skills/coastline-rendering-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coastline-rendering-test", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add osmandapp/OsmAnd-tools --skill coastline-rendering-test -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install osmandapp/OsmAnd-tools coastline-rendering-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/osmandapp/OsmAnd-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/coastline-rendering-test .opencode/skills/coastline-rendering-test && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "coastline-rendering-test" agent skill from https://github.com/osmandapp/OsmAnd-tools/tree/master/.claude/skills/coastline-rendering-test into .opencode/skills/coastline-rendering-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coastline-rendering-test", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
coastline-rendering-test- GitHub stars
- 116
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,299 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Run or debug the coastline rendering test (CoastlineRenderingTester / utilities.sh test-coastline-rendering) that compares locally rendered tiles against tile.osmand.net and reports water mask…
- Working on coastline issues
- SKILL.md covers Running it, Running it locally, The OpenGL (v2) engine and The one number that explains a…, plus 2 more sections
- Reaches tile.osmand.net and builder.osmand.net
- On the WebOceanTilesTest Jenkins job
What it does
Coastline Rendering Test is an agent skill from osmandapp/OsmAnd-tools. Run or debug the coastline rendering test (CoastlineRenderingTester / utilities.sh test-coastline-rendering) that compares locally rendered tiles against tile.osmand.net and reports water mask differences, with either the legacy (v1) renderer or the OpenGL core one (v2, -renderer=opengl). Use when working on coastline issues, on the WebOceanTilesTest Jenkins job, on coastline-tests.json, when comparing the two rendering engines, or when the test is slow, crashes on a map, or reports unexpected failures.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud. It works with Jenkins and Java. The repository describes itself as: OsmAnd tools to generate new maps & to test OsmAnd files on PC.
When your agent uses it
- Working on coastline issues
- On the WebOceanTilesTest Jenkins job
- On coastline-tests.json
- Comparing the two rendering engines
Example prompts
- “/coastline-rendering-test”
What it can do on your machine
Read from SKILL.md and the folder at commit 8ad0df7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
tile.osmand.netbuilder.osmand.net
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Coastline Rendering Test loads about 2.5k tokens when it runs. Until then it costs about 135 tokens; SKILL.md has 1,299 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,299 words (~2,455 tokens).
“Renders tiles with the legacy native renderer (v1) or with OsmAndCore (v2, -renderer=opengl) and compares the water mask against the reference https://tile.osmand.net/hd/{z}/{x}/{y}.png. Exit code 0 = no failed tile above -failAbove (default 0.05, i.e. 5% of the tile), 2 =…”
- name
- coastline-rendering-test
Files
Just SKILL.md in .claude/skills/coastline-rendering-test of osmandapp/OsmAnd-tools.
Open the folder on GitHubat commit 8ad0df7
Compare with similar skills
Coastline Rendering Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Coastline Rendering Test this skillosmandapp/OsmAnd-tools | 116 | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| Docker Jfr Benchmark Loopeclipse-rdf4j/rdf4j | 420 | — | ~945 | Automated safety check: Pass | BSD-3-Clause | |
| Opik Local Dev Environmentcomet-ml/opik | 22k | — | ~734 | Automated safety check: Pass | Apache-2.0 | |
| Migrate To TeamcityJetBrains/teamcity-cli | 125 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Pi K8s Deployrodrigorodrigues/microservices-design-patterns | 187 | — | ~1.6k | Automated safety check: Pass | None | |
| Tirith PoliciesStackGuardian/tirith | 170 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Opik Local Dev Environment
comet-ml/opik
Starts, rebuilds, and troubleshoots the Opik local dev stack, including an optional Comet Platform integration mode for the Opik team.
- Official
Migrate To Teamcity
JetBrains/teamcity-cli
Migrating CI/CD pipelines to TeamCity. An agent skill from JetBrains/teamcity-cli.
Pi K8s Deploy
rodrigorodrigues/microservices-design-patterns
Check Docker Hub for a new :latest image on a managed service and roll it out to the home Pi k8s cluster, the same way authentication-service was deployed on 2026-08-29 (SSH + kubectl rollout…
Tirith Policies
StackGuardian/tirith
Write, validate, run and debug Tirith IaC governance policies, install Tirith, and add it to a CI pipeline (GitHub Actions, GitLab CI, Bitbucket Pipelines, Jenkins, Azure DevOps, CircleCI or any…
Release A2a
a2aproject/a2a-java
Guide maintainers through the multi-step release process — version bump, CI verification, tagging, Maven Central deployment, SNAPSHOT bump, and versioned documentation.
Related
Categories
Questions about Coastline Rendering Test
What does Coastline Rendering Test do?
Run or debug the coastline rendering test (CoastlineRenderingTester / utilities.sh test-coastline-rendering) that compares locally rendered tiles against tile.osmand.net and reports water mask…. Coastline Rendering Test is an agent skill from osmandapp/OsmAnd-tools.net and reports water mask differences, with either the legacy (v1) renderer or the OpenGL core one (v2, -renderer=opengl).
When should I use Coastline Rendering Test?
Coastline Rendering Test fits situations like: working on coastline issues; on the WebOceanTilesTest Jenkins job; on coastline-tests.json; comparing the two rendering engines.
How do I install Coastline Rendering Test in Claude Code?
Run `npx skills add osmandapp/OsmAnd-tools --skill coastline-rendering-test -a claude-code`. Or copy the skill folder (.claude/skills/coastline-rendering-test in osmandapp/OsmAnd-tools) into .claude/skills/coastline-rendering-test in your project. Claude Code loads it when a task matches its description.
How do I install Coastline Rendering Test in Codex?
Run `npx skills add osmandapp/OsmAnd-tools --skill coastline-rendering-test -a codex`. Or copy the skill folder (.claude/skills/coastline-rendering-test in osmandapp/OsmAnd-tools) into .agents/skills/coastline-rendering-test in your project. Codex loads it when a task matches its description.
Can I use Coastline Rendering Test in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add osmandapp/OsmAnd-tools --skill coastline-rendering-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/coastline-rendering-test, .gemini/skills/coastline-rendering-test, .github/skills/coastline-rendering-test and .opencode/skills/coastline-rendering-test in your project.
What does Coastline Rendering Test need to run?
SKILL.md names no scripts, command-line tools or credentials: Coastline Rendering Test is instructions for the agent only.
Does Coastline Rendering Test access the network?
SKILL.md names 2 domains. In commands or code: tile.osmand.net and builder.osmand.net; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Coastline Rendering Test safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Coastline Rendering Test use?
Coastline Rendering Test has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Coastline Rendering Test use?
About 2.5k tokens (SKILL.md is roughly 9.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Coastline Rendering Test?
Skills that share tags, products or a category with Coastline Rendering Test: Docker Jfr Benchmark Loop (eclipse-rdf4j/rdf4j, 420 stars), Opik Local Dev Environment (comet-ml/opik, 22k stars), Migrate To Teamcity (JetBrains/teamcity-cli, 125 stars) and Pi K8s Deploy (rodrigorodrigues/microservices-design-patterns, 187 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Coastline Rendering Test?
osmandapp (a GitHub organization) maintains it in osmandapp/OsmAnd-tools, which has 116 GitHub stars. The repository was last updated on October 7, 2026.
Source: osmandapp/OsmAnd-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.