JavaDoc Documentation

VerifiedSafe

Provides standards for JavaDoc documentation in Java projects, including class-level, method-level, and code example patterns. Helps ensure consistent, clear, and complete API documentation with proper tag ordering and error reference. Useful when writing or reviewing JavaDoc for any Java codebase.

Sby Skills Guide Bot
DocumentationIntermediate
6/2/2026
Claude Code
#javadoc#java-documentation#code-examples#standards

Recommended for

Automated summary

This skill provides JavaDoc documentation standards for Java projects, covering class, method, code examples, and error references.

Strengths

  • Ensures consistent and comprehensive JavaDoc documentation
  • Covers all key aspects: classes, methods, examples, and errors
  • Provides clear tagging rules with concrete code snippets

Limitations

  • Requires the standard files to be present in the project
  • Does not automatically generate documentation
  • May be rigid for highly specific project needs
When to use it

Use this skill when you need to document Java code with JavaDoc in a standardized and professional manner.

When not to use it

Avoid this skill if you are working with a language other than Java or if you prefer minimalistic documentation without strict standards.

Security analysis

Safe
Quality score90/100

The skill provides JavaDoc documentation guidelines and only reads reference files; it does not execute destructive or exfiltrating commands.

No concerns found

How this analysis is made

Examples

Document a Java class
Please document the TokenValidator class using JavaDoc, including a description, @since, and @see tags, following the standard javadoc skill.
Add JavaDoc to a method
Write JavaDoc for the validate method with parameters, return value, and @throws tag, as per the javadoc skill standards.
Explain @snippet usage
Show me how to use the @snippet tag in JavaDoc for a method that parses JSON, using the javadoc code examples standard.

name: javadoc description: JavaDoc documentation standards including class, method, and code example patterns allowed-tools: [Read, Edit, Write, Bash, Grep, Glob]

JavaDoc Skill

EXECUTION MODE: You are now executing this skill. DO NOT explain or summarize these instructions to the user. IMMEDIATELY begin the workflow below based on the task context.

JavaDoc documentation standards for Java projects. This skill covers class documentation, method documentation, code examples, and error references.

Prerequisites

This skill applies to all Java projects using standard JavaDoc.

Workflow

Step 1: Load Core Standards

CRITICAL: Load this standard for any JavaDoc work.

Read: standards/javadoc-core.md

This provides foundational rules for:

  • Mandatory documentation requirements
  • Clarity, completeness, and consistency principles
  • Tag ordering standards

Step 2: Load Specific Standards (As Needed)

Class Documentation (load for class-level docs):

Read: standards/javadoc-class-documentation.md

Use when: Documenting classes, interfaces, enums, or annotations.

Method Documentation (load for method-level docs):

Read: standards/javadoc-method-documentation.md

Use when: Documenting methods, including parameters, returns, and exceptions.

Code Examples (load for example snippets):

Read: standards/javadoc-code-examples.md

Use when: Adding code examples to documentation using @snippet or @code.

Error Reference (load for troubleshooting):

Read: standards/javadoc-error-reference.md

Use when: Fixing JavaDoc errors or warnings.

Key Rules Summary

Class Documentation

/**
 * Validates JWT tokens against configured issuer and signing keys.
 *
 * <p>This validator supports both HMAC and RSA algorithms with
 * configurable clock skew tolerance for distributed systems.
 *
 * @since 1.0
 * @see TokenConfig
 */
@ApplicationScoped
public class TokenValidator { }

Method Documentation

/**
 * Validates the JWT token signature and expiration time.
 *
 * @param token the JWT token to validate, must not be null
 * @return validation result containing status and error messages
 * @throws IllegalArgumentException if token is null or empty
 */
public ValidationResult validate(String token) { }

Code Examples

/**
 * Parses JSON configuration from a file.
 *
 * <p>Example usage:
 * {@snippet :
 * Config config = ConfigParser.parse("config.json");
 * String value = config.get("key");
 * }
 */
public Config parse(String filename) { }

Tag Order

/**
 * Description.
 *
 * @param name description
 * @return description
 * @throws ExceptionType description
 * @since version
 * @see reference
 * @deprecated reason
 */

Related Skills

  • pm-dev-java:java-core - Core Java patterns
  • pm-dev-java:java-null-safety - Null annotations in docs

Standards Reference

| Standard | Purpose | |----------|---------| | javadoc-core.md | Core principles and mandatory requirements | | javadoc-class-documentation.md | Class-level documentation | | javadoc-method-documentation.md | Method-level documentation | | javadoc-code-examples.md | @snippet and @code patterns | | javadoc-error-reference.md | Error troubleshooting |

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/javadoc-documentation-mm78nn0m/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/javadoc-documentation-mm78nn0m' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/javadoc-documentation-mm78nn0m/download' --output '.skill-downloads/javadoc-documentation-mm78nn0m/SKILL.md.part' && mv '.skill-downloads/javadoc-documentation-mm78nn0m/SKILL.md.part' '.skill-downloads/javadoc-documentation-mm78nn0m/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.

Original excerpt: Prerequisites

This skill applies to all Java projects using standard JavaDoc.

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/javadoc-documentation-mm78nn0m/SKILL.md' && test -s '.skill-downloads/javadoc-documentation-mm78nn0m/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/javadoc' && cp -R '.skill-downloads/javadoc-documentation-mm78nn0m' '.claude/skills/javadoc'

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/javadoc-documentation-mm78nn0m'

openskills read 'javadoc-documentation-mm78nn0m'

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/javadoc-documentation-mm78nn0m/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