java-coding-skill

Use this skill whenever editing `*.java` files in the `java/` directore of the SDK in order to write idiomatic, well-structured Java code for the Copilot SDK

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/java-coding-skill/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a comprehensive, highly actionable Java SDK reference with executable examples throughout, but it is a long monolithic document that repeats boilerplate and does not split detailed API reference into separate bundle files. Organization is good; token efficiency and progressive disclosure are the weakest areas.

Suggestions

Split the detailed API reference (e.g. full SessionConfig/CopilotClientOptions option tables and event-type catalog) into a separate reference file and keep SKILL.md as a concise overview with one-level-deep links, lifting progressive_disclosure.

Reduce repeated createSession + setOnPermissionRequest(APPROVE_ALL) boilerplate by introducing one canonical setup snippet and referencing it, improving conciseness.

Add an explicit validate→fix→retry loop for the build/commit flow (e.g. run `mvn spotless:check`, fix, re-check, only then commit) to strengthen workflow_clarity.

Dimension	Reasoning	Score
Conciseness	Each section is lean and SDK-specific (classes, setters, events Claude would not already know), but the ~750-line body repeats the createSession + permission-handler boilerplate across many examples and could be tightened; not a verbose 1, not a fully lean 3.	2 / 3
Actionability	Throughout the body are complete, copy-paste-ready Java snippets (client setup, sessions, tools, streaming, BYOK, hooks) with specific class and method names rather than pseudocode.	3 / 3
Workflow Clarity	Sequencing exists (Tool Execution Flow, session lifecycle, the Spotless "run mvn spotless:apply before committing" checkpoint), but as a reference-style skill it lacks explicit validate→fix→retry feedback loops for most operations, so it sits below a 3.	2 / 3
Progressive Disclosure	The body is a monolithic single file (~750 lines) with API reference, examples, and best practices all inline and no references/scripts/assets bundles; it is well-sectioned with headers but content that could be split into separate files is not, matching the level-2 anchor.	2 / 3
	Total	9 / 12 Passed

Description

75%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description uses the recommended explicit "Use this skill whenever..." trigger form and clearly states both what and when, with a distinct, low-conflict niche. It is held back by a typo ("directore") and a lack of varied/comprehensive trigger terms and concrete action verbs.

Suggestions

Fix the typo "directore" → "directory" so the trigger phrase reads cleanly.

Broaden trigger-term coverage with natural variants users might say (e.g. "Copilot SDK", "SDK for Java", "Java bindings", "copilot-sdk-java").

Name a few more concrete actions (e.g. "initialize the client, create sessions, define custom tools, handle events") to lift specificity to a 3.

Dimension	Reasoning	Score
Specificity	Names the domain ("editing *.java files in the java/ directory") and actions ("write idiomatic, well-structured Java code"), but does not list multiple distinct concrete actions, so it stops short of a comprehensive 3.	2 / 3
Completeness	Explicitly answers both what ("write idiomatic, well-structured Java code for the Copilot SDK") and when ("Use this skill whenever editing *.java files in the java/ directory").	3 / 3
Trigger Term Quality	Includes some natural terms a user might say ("editing", "*.java files", "Java", "Copilot SDK"), but lacks common variations and the typo "directore" slightly muddies the trigger phrase.	2 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (Copilot SDK Java code under java/), with file-pattern and product-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (759 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: github/copilot-sdk
Path: .github/skills/java-coding-skill/SKILL.md
Commit: 2ab2aa5

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.