Agent skill

Score Style

Score migrated code against style guidelines and best practices.

MITAuto-check passedDevelopment

Install Score Style

skills CLI

$ npx skills add OpenHands/extensions --skill score-style -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install OpenHands/extensions score-style --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/migration-scoring/skills/score-style .claude/skills/score-style && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "score-style" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/migration-scoring/skills/score-style into .claude/skills/score-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "score-style", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/OpenHands/extensions/tree/main/plugins/migration-scoring/skills/score-style

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add OpenHands/extensions --skill score-style -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install OpenHands/extensions score-style --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/migration-scoring/skills/score-style .agents/skills/score-style && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "score-style" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/migration-scoring/skills/score-style into .agents/skills/score-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "score-style", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add OpenHands/extensions --skill score-style -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install OpenHands/extensions score-style --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/migration-scoring/skills/score-style .cursor/skills/score-style && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "score-style" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/migration-scoring/skills/score-style into .cursor/skills/score-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "score-style", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/OpenHands/extensions.git --path plugins/migration-scoring/skills/score-style

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add OpenHands/extensions --skill score-style -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install OpenHands/extensions score-style --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/migration-scoring/skills/score-style .gemini/skills/score-style && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "score-style" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/migration-scoring/skills/score-style into .gemini/skills/score-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "score-style", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install OpenHands/extensions score-style

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add OpenHands/extensions --skill score-style -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/migration-scoring/skills/score-style .github/skills/score-style && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "score-style" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/migration-scoring/skills/score-style into .github/skills/score-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "score-style", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add OpenHands/extensions --skill score-style -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install OpenHands/extensions score-style --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/migration-scoring/skills/score-style .opencode/skills/score-style && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "score-style" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/migration-scoring/skills/score-style into .opencode/skills/score-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "score-style", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: score-style
GitHub stars: 157
Token cost: ~721 tokens
SKILL.md length: 289 words
Files: 1
Skills in repo: 78
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Score migrated code against style guidelines and best practices.

Tasks that involve Code quality
SKILL.md covers Default Scoring Criteria, Output Format, Custom Rubric and Evaluation Guidelines, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Score Style is an agent skill from OpenHands/extensions. Score migrated code against style guidelines and best practices. Evaluates code quality independent of functional correctness.

Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires target code to evaluate

It sits in Development, covering Code quality. It works with Java. The repository describes itself as: Public registry for OpenHands extensions. The licence is MIT.

When your agent uses it

Tasks that involve Code quality

Example prompts

“/score-style”

Requirements

Compatibility (from SKILL.md): Requires target code to evaluate

What it can do on your machine

Read from SKILL.md and the folder at commit d008b81. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires target code to evaluate
From compatibility in the SKILL.md frontmatter.

Context cost

Score Style loads about 721 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 289 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~35
When it runs · the whole SKILL.md, loaded when a task matches: ~721

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from OpenHands/extensions at commit d008b81, republished under its MIT licence (© OpenHands). 289 words, ~721 tokens.

Download SKILL.mdSave it as .claude/skills/score-style/SKILL.md (or your agent's skills folder).

name: score-style
description: Score migrated code against style guidelines and best practices. Evaluates code quality independent of functional correctness.
compatibility: Requires target code to evaluate
license: MIT
triggers: style score, code quality score, style evaluation

Evaluate migrated code against style guidelines and best practices.

This skill scores code quality aspects that are independent of functional correctness — focusing on readability, maintainability, and adherence to conventions.

Default Scoring Criteria

Unless a custom rubric is provided, score on these attributes (1-5 scale):

Naming Conventions (1-5)

1: Inconsistent or meaningless names
3: Mostly follows conventions, some issues
5: Clear, consistent, idiomatic names

Code Organization (1-5)

1: Monolithic, hard to navigate
3: Some structure, could be cleaner
5: Well-organized, logical structure

Error Handling (1-5)

1: Missing or swallowed exceptions
3: Basic error handling present
5: Comprehensive, appropriate error handling

Documentation (1-5)

1: No documentation
3: Some documentation, inconsistent
5: Thorough, helpful documentation

Idiomaticity (1-5)

1: Non-idiomatic, smells like translated code
3: Mostly idiomatic, some foreign patterns
5: Fully idiomatic, natural code

Output Format

Save scores as a JSON file:

json

{
  "target_file_a.java": {
    "naming_conventions": 4,
    "code_organization": 3,
    "error_handling": 5,
    "documentation": 4,
    "idiomaticity": 4,
    "justification": "Good naming and error handling. Some methods could be extracted for better organization."
  }
}

Custom Rubric

If a custom rubric is provided, use its attributes and scoring criteria instead of the defaults. The rubric should define:

Attribute names
Score meanings for each level (1-5)
Examples of good/bad code for each attribute

Evaluation Guidelines

What to Look For

Positive indicators:

Consistent naming (camelCase for Java, snake_case for Python)
Appropriate class/method sizes
Single responsibility principle followed
Meaningful comments (not obvious ones)
Standard library usage over custom implementations
Defensive programming practices

Negative indicators:

Literal translations (COBOL-style Java)
God classes or methods
Magic numbers
Excessive comments or no comments
Reinvented wheels
Swallowed exceptions
Hardcoded values

Language-Specific Considerations

Java:

Streams vs. for loops (both acceptable, but be consistent)
Optional vs. null checks
Record types for data classes
Builder pattern for complex objects

Python:

Type hints
List comprehensions
Context managers
Pythonic idioms

Incremental Scoring

If a score file already exists, update it with new scores rather than replacing it entirely.

Files

Just SKILL.md in plugins/migration-scoring/skills/score-style of OpenHands/extensions.

Open the folder on GitHubat commit d008b81

Compare with similar skills

Score Style next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Score Style compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Score Style this skillOpenHands/extensions	157	—	~721	Automated safety check: Pass	MIT	yesterday
Code Review Skillawesome-skills/code-review-skill	2.1k	—	~2.8k	Automated safety check: Notes	MIT	29 days ago
New Rule for sonar-javaSonarSource/sonar-java	1.2k	—	~833	Automated safety check: Pass	Custom licence	today
Cross-Language Coding Standardszereight/gitlab-mcp	2k	1 repos	~1.4k	Automated safety check: Pass	MIT	yesterday
Code Qualitypiomin/claude-ai-spring-boot	1.3k	—	~2.2k	Automated safety check: Pass	Apache-2.0	5 mo ago
Android Code Quality Checkerwordpress-mobile/WordPress-Android	3.2k	—	~587	Automated safety check: Pass	GPL-2.0	today

Similar skills

Code Review Skill
awesome-skills/code-review-skill
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…
2.1k GitHub stars~2.8k tokensUpdated 29 days ago
DevelopmentAuto-check: notes
New Rule for sonar-java
SonarSource/sonar-java
Official
Sets the sonar-java conventions for adding an analyzer rule: metadata from rule-api, test locations, MethodMatchers and what not to commit or change.
1.2k GitHub stars~833 tokensUpdated today
DevelopmentAuto-check passed
Cross-Language Coding Standards
zereight/gitlab-mcp
Shared reference for naming, function size, complexity and error handling rules that reviewer agents apply across TypeScript, Python, Go, Rust, Java, C# and Swift.
2k GitHub starsUsed in 1 repo~1.4k tokens
DevelopmentAuto-check passed
Code Quality
piomin/claude-ai-spring-boot
Comprehensive code review for Java - clean code principles, API contracts, null safety, exception handling, and performance.
1.3k GitHub stars~2.2k tokensUpdated 5 mo ago
DevelopmentAuto-check passed
Android Code Quality Checker
wordpress-mobile/WordPress-Android
Runs detekt, checkstyle, and Android lint together, reads their reports, and proposes approved fixes grouped by file.
3.2k GitHub stars~587 tokensUpdated today
DevelopmentAuto-check passed
Caffeine Performance Audit
ben-manes/caffeine
Audits the Caffeine cache source for hot-path costs such as allocations, contention and memory layout, reporting only findings tied to specific lines.
18k GitHub stars~559 tokensUpdated yesterday
DevelopmentAuto-check passed

More from OpenHands/extensions

All 78 skills in this repo

Agent Readiness Report
OpenHands/extensions
Evaluate how well a codebase supports autonomous AI-assisted development.
157 GitHub stars~1.1k tokensUpdated yesterday
Auto-check passed
Discord
OpenHands/extensions
Build and automate Discord integrations (bots, webhooks, slash commands, and REST API workflows).
157 GitHub stars~1.1k tokensUpdated yesterday
Auto-check passed
GitHub
OpenHands/extensions
Interact with GitHub repositories, pull requests, issues, and workflows using the GITHUBTOKEN environment variable and GitHub CLI.
157 GitHub stars~1.7k tokensUpdated yesterday
Auto-check passed
GitHub Issue To PR
OpenHands/extensions
Create an automation that implements GitHub issues when a configurable trigger label is applied.
157 GitHub stars~4.4k tokensUpdated yesterday
Auto-check passed
GitHub Repo Monitor
OpenHands/extensions
This skill should be used when the user asks to "monitor a GitHub repository", "watch GitHub for issues or PRs", "respond to @OpenHands mentions on GitHub", "set up an OpenHands GitHub integration"…
157 GitHub stars~3.1k tokensUpdated yesterday
Auto-check passed
GitLab Issue To Mr
OpenHands/extensions
Create an automation that implements GitLab issues when a configurable trigger label is applied.
157 GitHub stars~4.9k tokensUpdated yesterday
Auto-check passed

Works with

Java

Questions about Score Style

What does Score Style do?

Score migrated code against style guidelines and best practices. Score Style is an agent skill from OpenHands/extensions. Score migrated code against style guidelines and best practices.

When should I use Score Style?

Score Style fits situations like: tasks that involve Code quality.

How do I install Score Style in Claude Code?

Run `npx skills add OpenHands/extensions --skill score-style -a claude-code`. Or copy the skill folder (plugins/migration-scoring/skills/score-style in OpenHands/extensions) into .claude/skills/score-style in your project. Claude Code loads it when a task matches its description.

How do I install Score Style in Codex?

Run `npx skills add OpenHands/extensions --skill score-style -a codex`. Or copy the skill folder (plugins/migration-scoring/skills/score-style in OpenHands/extensions) into .agents/skills/score-style in your project. Codex loads it when a task matches its description.

Can I use Score Style in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OpenHands/extensions --skill score-style -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/score-style, .gemini/skills/score-style, .github/skills/score-style and .opencode/skills/score-style in your project.

What does Score Style need to run?

SKILL.md names no scripts, command-line tools or credentials: Score Style is instructions for the agent only. Compatibility (from SKILL.md): Requires target code to evaluate.

Does Score Style access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Score Style safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Score Style use?

Score Style is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Score Style use?

About 721 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Score Style?

Skills that share tags, products or a category with Score Style: Code Review Skill (awesome-skills/code-review-skill, 2.1k stars), New Rule for sonar-java (SonarSource/sonar-java, 1.2k stars), Cross-Language Coding Standards (zereight/gitlab-mcp, 2k stars) and Code Quality (piomin/claude-ai-spring-boot, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Score Style?

OpenHands (a GitHub organization) maintains it in OpenHands/extensions, which has 157 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 6, 2026.

Source: OpenHands/extensions on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Score Style

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

Default Scoring Criteria

Naming Conventions (1-5)

Code Organization (1-5)

Error Handling (1-5)

Documentation (1-5)

Idiomaticity (1-5)

Output Format

Custom Rubric

Evaluation Guidelines

What to Look For

Language-Specific Considerations

Incremental Scoring

Files

Compare with similar skills

Similar skills

More from OpenHands/extensions

Related

Questions about Score Style