new-skill
Skill1 starsChanged 14 days agoMITView on GitHub
Scaffold a new java-skills skill from the template, with good and bad examples, then validate it. Use when adding a skill to this repository.
We split this skill into the rules it gives an agent
6 rules. 0 are common, 0 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Create the skill $ARGUMENTS in this repository.
- Very specific: line 12
Stop if skills/$ARGUMENTS/ already exists, or if the name is not lowercase kebab-case.
- Very specific: line 13
Read CLAUDE.md and templates/SKILL.template.md.
- Very specific: line 15
Create skills/$ARGUMENTS/examples/good/ and skills/$ARGUMENTS/examples/bad/, each either a Main.java that uses only the JDK, or a minimal …
- Very specific: line 17
Add the skill to the index in both README.md and README.pt-BR.md.
- Very specific: line 18
Run bash scripts/validate.sh and ONLY=skills/$ARGUMENTS bash scripts/test-examples.sh and fix everything they report.
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
New skill
Create the skill $ARGUMENTS in this repository.
- Stop if
skills/$ARGUMENTS/already exists, or if the name is not lowercase kebab-case. - Read
CLAUDE.mdandtemplates/SKILL.template.md. Check that the skill is in the catalog inCLAUDE.md; if not, say so and stop. - Copy the template to
skills/$ARGUMENTS/SKILL.mdand setname: $ARGUMENTS. - Create
skills/$ARGUMENTS/examples/good/andskills/$ARGUMENTS/examples/bad/, each either aMain.javathat uses only the JDK, or a minimal Maven project with<maven.compiler.release>25</maven.compiler.release>. - Write the skill following every rule in
CLAUDE.md: one decision, a position, a reason for every rule, real mistakes in the bad example with// MISTAKE:comments, and exceptions in "When not to apply". Check every fact against openjdk.org, docs.oracle.com, docs.spring.io or the library's own docs. - Add the skill to the index in both
README.mdandREADME.pt-BR.md. - Run
bash scripts/validate.shandONLY=skills/$ARGUMENTS bash scripts/test-examples.shand fix everything they report.
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- pedrohcgs/claude-code-my-workflow★ 1.6ksame name
- hyhmrright/brooks-lint★ 1.6ksame name
- remorses/kimaki★ 1.4ksame name
- ivklgn/ai-kit★ 12same name
- ivklgn/bag-of-skills★ 12same name
- MusserLab/lab-claude-skills★ 4same name
- qunyou-agent/finance-skills★ 4same name
- press-pass/journalism-skills★ 2same name
- 0xkangl/skills★ 1same name
- Andersonnn7788/claude-code-101★ 1same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use commit and handoff.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 4 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
In this repository26 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- review-skillSkill
- background-jobs-outboxSkill
- ci-guardrailsSkill
- container-runtime-tuningSkill
- db-migrationsSkill
- exceptionsSkill
- fast-startup-aot-cacheSkill
- http-serverSkill
- java-version-policySkill
- json-jackson3Skill
- logging-structuredSkill
- mcp-server-javaSkill
- null-safety-jspecifySkill
- observability-otelSkill
- outbound-http-clientSkill
- overload-protectionSkill
- postgres-hikari-poolSkill
- profiling-jfrSkill
- project-layoutSkill
- scoped-valuesSkill
- secure-defaultsSkill
- sql-and-transactionsSkill
- testingSkill
- timeouts-and-deadlinesSkill
- virtual-threadsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

