New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Score Quality

by OpenHands in OpenHands/extensions

Score code migration quality based on coverage and correctness.

MITAuto-check passedDevelopment

Install Score Quality

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

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

GitHub CLI
$ gh skill install OpenHands/extensions score-quality --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-quality .claude/skills/score-quality && 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/

Facts

Skill name
score-quality
GitHub stars
158
Token cost
~378 tokens
SKILL.md length
124 words
Files
2 (incl. references)
Skills in repo
78
Repo updated
First seen
Licence
MIT

At a glance

Score code migration quality based on coverage and correctness.

  • Works in 4 steps: Identify key functionality in the source → Check coverage in the target → Verify correctness → …
  • Tasks that involve Code migrations
  • SKILL.md covers Output Format, Evaluation Process and Incremental Scoring
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Score Quality is an agent skill from OpenHands/extensions. Score code migration quality based on coverage and correctness. Evaluates how well target code represents source functionality.

Its SKILL.md is about 380 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/scoring-criteria.md`). Compatibility notes: Requires completed migration with source and target code

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

When your agent uses it

  • Tasks that involve Code migrations

Example prompts

  • “/score-quality”

Requirements

  • Compatibility (from SKILL.md): Requires completed migration with source and target code

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Identify key functionality in the source
  2. Check coverage in the target
  3. Verify correctness
  4. Document justification

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 completed migration with source and target code

    From compatibility in the SKILL.md frontmatter.

Context cost

Score Quality loads about 378 tokens when it runs, and up to ~625 if it reads all its reference files. Until then it costs about 35 tokens; SKILL.md has 124 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
~378
With references · SKILL.md plus every file in references/, read only if the agent opens them
~625

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). 124 words, ~378 tokens.

Download SKILL.mdSave it as .claude/skills/score-quality/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
score-quality
description
Score code migration quality based on coverage and correctness. Evaluates how well target code represents source functionality.
compatibility
Requires completed migration with source and target code
license
MIT
triggers
migration quality, migration score, coverage score, correctness score

Evaluate migration quality by scoring coverage and correctness for each source-target file pair.

Prerequisite: A migration mapping file must exist (see migration-mapping skill).

See references/scoring-criteria.md for the 1-5 scoring scales.

Output Format

Save scores as a JSON file:

json
{
  "source_file_1.cbl": {
    "coverage": 4,
    "correctness": 5,
    "justification": "All calculation logic migrated. Tax rounding matches COBOL behavior."
  }
}

Evaluation Process

For each source file and its mapped target files:

  1. Identify key functionality in the source

    • Business logic, data operations, control flow, error handling

  2. Check coverage in the target

    • Is each function/paragraph represented?
    • Are all data fields and code paths covered?

  3. Verify correctness

    • Do calculations produce the same results?
    • Are edge cases handled the same way?

  4. Document justification

    • Specific functionality present/missing
    • Known discrepancies

Incremental Scoring

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

© OpenHands, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/migration-scoring/skills/score-quality of OpenHands/extensions.

  • SKILL.md
  • references/scoring-criteria.md

Open the folder on GitHubat commit d008b81

Compare with similar skills

Score Quality 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 Quality compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Score Quality this skillOpenHands/extensions158—~378Automated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman42k—~2.6kAutomated safety check: PassGPL-3.0
Migrate Internal Package into GhostTryGhost/Ghost55k—~3.8kAutomated safety check: PassMIT
Next Cache Components Adoptionvercel/next.js143k6 repos~8.3kAutomated safety check: PassMIT
Deprecate R Functions and Argumentstidyverse/dplyr5.1k1 repos~1.2kAutomated safety check: PassCustom licence
Rust Path Typesopeninterpreter/openinterpreter69k2 repos~605Automated safety check: PassApache-2.0

Similar skills

  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    42k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Migrate Internal Package into Ghost

    TryGhost/Ghost

    Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    55k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Next Cache Components Adoption

    vercel/next.js

    Official

    Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces.

    143k GitHub starsUsed in 6 repos~8.3k tokens
    DevelopmentAuto-check passed

  • Deprecate R Functions and Arguments

    tidyverse/dplyr

    Walks through deprecating an R function or argument in a package: lifecycle warning, silenced tests, a new snapshot test, documentation badge and NEWS entry.

    5.1k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed

  • Rust Path Types

    openinterpreter/openinterpreter

    Rules for choosing Rust types for filesystem paths in new Codex code, covering protocol types, internal use and model tool arguments.

    69k GitHub starsUsed in 2 repos~605 tokens
    DevelopmentAuto-check passed

  • ast-grep Structural Search

    code-yeongyu/oh-my-openagent

    Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.

    70k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed

More from OpenHands/extensions

All 78 skills in this repo

  • GitHub

    OpenHands/extensions

    Interact with GitHub repositories, pull requests, issues, and workflows using the GITHUBTOKEN environment variable and GitHub CLI.

    158 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

  • Agent Readiness Report

    OpenHands/extensions

    Evaluate how well a codebase supports autonomous AI-assisted development.

    158 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Discord

    OpenHands/extensions

    Build and automate Discord integrations (bots, webhooks, slash commands, and REST API workflows).

    158 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • GitHub Issue To PR

    OpenHands/extensions

    Create an automation that implements GitHub issues when a configurable trigger label is applied.

    158 GitHub stars~4.4k tokensUpdated today
    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"…

    158 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • GitLab Issue To Mr

    OpenHands/extensions

    Create an automation that implements GitLab issues when a configurable trigger label is applied.

    158 GitHub stars~4.9k tokensUpdated today
    Auto-check passed

Categories

Questions about Score Quality

What does Score Quality do?

Score code migration quality based on coverage and correctness. Score Quality is an agent skill from OpenHands/extensions. Score code migration quality based on coverage and correctness.

When should I use Score Quality?

Score Quality fits situations like: tasks that involve Code migrations.

How do I install Score Quality in Claude Code?

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

How do I install Score Quality in Codex?

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

Can I use Score Quality 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-quality -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-quality, .gemini/skills/score-quality, .github/skills/score-quality and .opencode/skills/score-quality in your project.

What does Score Quality need to run?

SKILL.md names no scripts, command-line tools or credentials: Score Quality is instructions for the agent only. Compatibility (from SKILL.md): Requires completed migration with source and target code.

Does Score Quality 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 Quality 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 Quality use?

Score Quality 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 Quality use?

About 378 tokens (SKILL.md is roughly 1.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 247 tokens, read only when the agent opens those files.

What are the alternatives to Score Quality?

Skills that share tags, products or a category with Score Quality: Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Migrate Internal Package into Ghost (TryGhost/Ghost, 55k stars), Next Cache Components Adoption (vercel/next.js, 143k stars) and Deprecate R Functions and Arguments (tidyverse/dplyr, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Score Quality?

OpenHands (a GitHub organization) maintains it in OpenHands/extensions, which has 158 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 7, 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.