mcpbeat Sign in

Dup Classes Agent Skill

Verify whether generated Java classes duplicate openai-java models by comparing fields/types (names may differ). Use when checking for duplicate model coverage.

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
2566
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Azure/azure-sdk-for-java --skill dup-classes

What it tells the agent to use

found in the instruction text
WebSearch reads your files

The instruction itself

11 sections, as written by the author

Duplicate Class Verification (Generated vs openai-java)

Use this skill to compare generated Java models against the openai-java dependency. The goal is field-by-field comparison of model shapes, even when class or field names differ.

Inputs to confirm

  • Generated source root (e.g., src/main/java/...)
  • The relevant pom.xml (module) to resolve the openai-java dependency version
  • Optional: package or class name hints to narrow the search

Steps

  • Locate the pom.xml in the current directory tree (find . -name pom.xml). If multiple, ask which module to use.
  • Resolve openai-java:
  • Search the chosen pom for openai-java (or an explicit group/artifact provided by the user).
  • Resolve the version (including properties) and locate the JAR in ~/.m2/repository.
  • The model classes live in openai-java-core, not the top-level openai-java artifact.
  • List candidate classes:
  • Generated classes: scan the source root for class and record declarations.
  • openai-java classes: jar tf <jar> | grep '\.class$' (filter by package hints if provided).
  • Extract field signatures (names may differ; compare shape):
  • Generated source:
  • For record, use the component list in the record declaration.
  • For class, extract non-static field declarations (type + count) and note any @JsonProperty names.
  • Check toJson/fromJson methods for the actual JSON keys used in serialization.
  • openai-java JAR:
  • Use javap -classpath <jar> -p <FQCN> to list fields (ignore static, validated, hashCode$delegate, additionalProperties).
  • Extract @JsonProperty keys from the sources JAR (*-sources.jar) for JSON key comparison.
  • Compare shapes:
  • Compare field count and field types (order-independent).
  • Compare JSON keys from @JsonProperty (openai-java) vs toJson/fromJson string literals (generated).
  • Compare enum/union values when field types are enums or string unions.
  • Follow type hierarchy: BinaryDataJsonValue (both represent untyped JSON), Map<String,BinaryData>Map<String,JsonValue>, Java enum ↔ Kotlin string enum.
  • Categorize results (do NOT treat all matches the same):

Actionable duplicates — standalone models not in any type hierarchy. These can potentially be suppressed and replaced with the openai-java equivalent. Examples: ComparisonFilter, Reasoning.

Structural equivalents — classes that produce identical JSON but participate in a discriminator hierarchy (e.g., extends Tool, extends TextResponseFormatConfiguration). The SDK's polymorphic serialization (Tool.fromJson() dispatches to FunctionTool.fromJson(), etc.) requires these to exist. They are NOT actionable duplicates. Examples: FunctionTool, FileSearchTool, ComputerUsePreviewTool.

Partial matches — classes with most fields matching but extra Azure-specific fields. Note the extra fields. Examples: CodeInterpreterTool (extra container), WebSearchTool (extra custom_search_configuration).

  • Report:
  • Provide a table with: generated class → openai-java class, field count, matching fields, category.
  • Clearly separate actionable duplicates from structural equivalents.
  • For actionable duplicates, note whether @@alternateType or @@access(internal) would be the right suppression mechanism (see dedup-openai skill).

Useful commands

List generated class names

rg -n "^(public\s+)?(final\s+)?(class|record)\s+" <generated_root>

Extract field lines from source (classes)

grep -E '^\s+private\s+' <file> | grep -v 'static\s'

Extract JSON keys from generated toJson/fromJson

grep -E 'jsonWriter\.write|"[a-z_]+"' <file> | grep -v '//'

Inspect fields in a JAR class

javap -classpath <jar> -p <fully.qualified.ClassName>

Extract @JsonProperty from openai-java sources JAR

jar xf <sources-jar> main/com/openai/models/<Class>.kt
grep '@JsonProperty' main/com/openai/models/<Class>.kt

Check if a class participates in a hierarchy

grep 'extends\s' <file>  # If it extends Tool, TextResponseFormatConfiguration, etc. → structural

Notes

  • Use search-m2 if you need help locating the dependency version or JAR path.
  • If the user provides only a vague class hint, narrow candidates by package or field count first.
  • The openai-java classes are Kotlin and use Jackson; generated classes use azure-json (JsonSerializable). Compare at the JSON wire level, not at the Java API level.

Other skills for the same job

different authors, same section of the catalogue
Receiving Code Review
by ZhanlinCui
×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens
Requesting Code Review
by ZhanlinCui
×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

2k tokens
Git Commit
by github
vendor ×3

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

799 tokens
Github Code Review
by ComeOnOliver
×3

Comprehensive GitHub code review with AI-powered swarm coordination

13k tokens
Karpathy Guidelines
by hyyhf
×3

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

629 tokens
Code Reviewer
by google-gemini
vendor ×2

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

795 tokens
Agent MD Refactor
by softaworks
×2

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

4k tokens
Commit Work
by softaworks
×2

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take azure/dup-classes from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.