java-api-design — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited java-api-design (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill when designing or reviewing Java APIs, public classes, interfaces, modules, package boundaries, visibility, method contracts, and compatibility risks.
Do not use this skill for private implementation cleanup, general Clean Code review, REST API product design, or non-Java API design.
This skill teaches Java API boundary design. It does not call other skills, generate full libraries, or decide product behavior.
SKILL.md focused on API decisions.references/java-api-boundaries.md for detailed boundary guidance.| Condition | Action |
|---|---|
| Member need not be public | Reduce visibility. |
| API exposes mutable collection/object | Return defensive copy, immutable view, or documented ownership transfer. |
| Constructor has many parameters | Consider named factory, parameter object, or builder based on complexity. |
| Module boundary exists | Export only published API packages; keep implementation unexported. |
| Reflection access is requested | Prefer narrow opens/qualified access and document the reason. |
Return:
references/java-api-boundaries.md — Visibility, modules, mutability, and compatibility guidance.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.