Java SDK Development

VerifiedSafe

Use for Java package layout, Java 8 constraints, Lombok, and coding conventions in this repository.

Sby Skills Guide Bot
DevelopmentIntermediate
7/28/2026
Claude CodeCursorWindsurfCopilotCodex
#java#java-8#lombok#package-layout#coding-conventions

Recommended for

Automated summary

This skill guides adherence to the Contentstack Management Java SDK conventions: package layout, Java 8 constraint, Lombok usage, and nullability annotations.

Strengths

  • Precisely describes source organization (core/, stack/, oauth/, models/) and mirrored test packages.
  • Reinforces Java 8 source compatibility via maven.compiler.source/target.
  • Recommends matching Lombok and @NotNull usage to neighboring classes instead of mixing inconsistent boilerplate.
  • Encourages fixing new -Xlint warnings rather than suppressing them.

Limitations

  • References relative links to pom.xml and repository files that only exist in this specific project.
  • Does not cover detailed testing or SDK API usage, deferring to other SKILL.md files.
  • Assumes familiarity with Lombok and Maven project structure.
When to use it

Use it when adding types under com.contentstack.cms, reorganizing packages, or touching Lombok-based code in this repository.

When not to use it

Avoid it for Java projects outside this SDK or when the JVM target is no longer Java 8.

Security analysis

Safe
Quality score84/100

The skill only provides repository-specific Java coding conventions and package layout guidance. It declares no tools and contains no executable commands, network access, secret handling, or destructive instructions, so listing it introduces no meaningful execution risk.

No concerns found

How this analysis is made

Examples

Add a new stack feature type
Add a new class under com.contentstack.cms.stack for managing webhooks, following the existing package layout, Java 8 compatibility, and Lombok patterns in neighboring classes.
Review Lombok consistency
Check the new model class I wrote and make it consistent with the existing Lombok style (@Getter, @Builder) and @NotNull annotations used elsewhere in this SDK.
Keep Java 8 compliance
I refactored some HTTP helpers in core/ — verify I didn't use any language features newer than Java 8 and that no new -Xlint warnings are introduced.

name: java description: Use for Java package layout, Java 8 constraints, Lombok, and coding conventions in this repository.

Java – Contentstack Management Java SDK

When to use

  • You add new types under com.contentstack.cms or reorganize packages.
  • You need to stay compatible with Java 8 (maven.compiler.source / target = 1.8).
  • You use or configure Lombok and need to match existing patterns.

Instructions

Layout

  • Main code: src/main/java/com/contentstack/cms/ — core client in Contentstack, stack features under stack/, HTTP helpers in core/, OAuth under oauth/, models under models/.
  • Tests: mirror packages under src/test/java/com/contentstack/cms/; Surefire includes **/Test*.java, **/*Test.java, **/*Tests.java, and related patterns per pom.xml.

Language level

  • Do not use language or library features that require a JVM newer than 8 for source compatibility unless the project explicitly upgrades (check maven-compiler-plugin and <maven.compiler.source> in pom.xml).

Lombok and tooling

  • Lombok is on the annotation processor path; prefer the same style as neighboring classes (@Getter, @Builder, etc.) instead of mixing hand-written boilerplate inconsistently.
  • JetBrains @NotNull / nullable annotations appear in places like Contentstack; follow existing nullability hints for new APIs.

Compiler

  • The compiler enables broad -Xlint checks; fix new warnings rather than suppressing without cause.

References

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/java-sdk-development-ms47vphv/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/java-sdk-development-ms47vphv' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/java-sdk-development-ms47vphv/download' --output '.skill-downloads/java-sdk-development-ms47vphv/SKILL.md.part' && mv '.skill-downloads/java-sdk-development-ms47vphv/SKILL.md.part' '.skill-downloads/java-sdk-development-ms47vphv/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/java-sdk-development-ms47vphv/SKILL.md' && test -s '.skill-downloads/java-sdk-development-ms47vphv/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/java' && cp -R '.skill-downloads/java-sdk-development-ms47vphv' '.claude/skills/java'

Cursor
test -f '.skill-downloads/java-sdk-development-ms47vphv/SKILL.md' && test -s '.skill-downloads/java-sdk-development-ms47vphv/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/java' && cp -R '.skill-downloads/java-sdk-development-ms47vphv' '.cursor/skills/java'

Codex
test -f '.skill-downloads/java-sdk-development-ms47vphv/SKILL.md' && test -s '.skill-downloads/java-sdk-development-ms47vphv/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/java' && cp -R '.skill-downloads/java-sdk-development-ms47vphv' '.agents/skills/java'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/java-sdk-development-ms47vphv'

openskills read 'java-sdk-development-ms47vphv'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/java-sdk-development-ms47vphv/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills