Agent skill

Cime Unit Test

by ESMCI in ESMCI/cime

A skill your agent uses when writing/modifying CIME unit tests.

Custom licenceAuto-check passedTesting & QA

Install Cime Unit Test

skills CLI
$ npx skills add ESMCI/cime --skill cime-unit-test -a claude-code

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

GitHub CLI
$ gh skill install ESMCI/cime cime-unit-test --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/ESMCI/cime.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cime-unit-testing .claude/skills/cime-unit-test && 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
cime-unit-test
GitHub stars
174
Token cost
~543 tokens
SKILL.md length
243 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
Custom licence

At a glance

A skill your agent uses when writing/modifying CIME unit tests.

  • Works in 5 steps: Identify target unit for testing. → Analyze function implementation. → Write test checking for all combinations… → …
  • Writing/modifying CIME unit tests
  • SKILL.md covers Overview, When to use, Required frameworks and style and Test structure, plus 6 more sections
  • Calls pytest

What it does

Cime Unit Test is an agent skill from ESMCI/cime. Use when writing/modifying CIME unit tests.

Its SKILL.md is about 540 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Unit testing. The repository describes itself as: Common Infrastructure for Modeling the Earth.

When your agent uses it

  • Writing/modifying CIME unit tests
  • Tasks that involve Unit testing

Example prompts

  • “/cime-unit-test”

Requirements

  • Python 3

Workflow steps

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

  1. Identify target unit for testing.
  2. Analyze function implementation.
  3. Write test checking for all combinations of input/output, errors, and edge cases.
  4. Run tests and check for adaquate coverage.
  5. If failing go back to step 2, continue until tests pass.

What it can do on your machine

Read from SKILL.md and the folder at commit 56bc592. 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

    Shell commands in SKILL.md call:

    • pytest

    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.

Context cost

Cime Unit Test loads about 543 tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 243 words of instructions outside code blocks.

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

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 243 words (~543 tokens).

“Use this skill when writing/modifying python unit tests under CIME/tests that are prefixed with test_unit.”

— opening of SKILL.md by ESMCI, Custom licence
name
cime-unit-test

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/cime-unit-testing of ESMCI/cime.

Open the folder on GitHubat commit 56bc592

Compare with similar skills

Cime Unit Test 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.

Cime Unit Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cime Unit Test this skillESMCI/cime174—~543Automated safety check: PassCustom licence
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
Testing OpenLogi UIAprilNEA/OpenLogi23k—~1.1kAutomated safety check: PassApache-2.0
Go Testingcxuu/golang-skills1701 repos~1.3kAutomated safety check: PassApache-2.0
Contractssamchon/nestia2.2k—~1.3kAutomated safety check: PassMIT
Cohesion Over TestabilityEpicenterHQ/epicenter4.8k—~2kAutomated safety check: PassCustom licence

Similar skills

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed
  • Testing OpenLogi UI

    AprilNEA/OpenLogi

    Verifies OpenLogi's native GPUI interface with focused tests, the component gallery and a mock agent, choosing the evidence that fits each change.

    23k GitHub stars~1.1k tokensUpdated 5 days ago
    Testing & QAAuto-check passed
  • Go Testing

    cxuu/golang-skills

    A skill your agent uses when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff.

    170 GitHub starsUsed in 1 repo~1.3k tokens
    Testing & QAAuto-check passed
  • Contracts

    samchon/nestia

    Defines self-acknowledgments for production declarations and tests.

    2.2k GitHub stars~1.3k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Cohesion Over Testability

    EpicenterHQ/epicenter

    Collapse test-shaped production boundaries while preserving behavior and coverage.

    4.8k GitHub stars~2k tokensUpdated today
    Testing & QAAuto-check passed
  • JS-in-HTML Testing

    liaohch3/claude-tap

    Tests JavaScript embedded in an HTML file in two layers: pytest checks of the logic ported to Python, and Playwright runs in a real browser for the DOM.

    3.3k GitHub stars~924 tokensUpdated 16 days ago
    Testing & QAAuto-check passed

More from ESMCI/cime

  • A skill your agent uses when writing or modifying CIME sys (end-to-end) tests.

    174 GitHub stars~475 tokensUpdated yesterday
    Auto-check passed
  • Use when writing CIME documentation

    174 GitHub stars~459 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Cime Unit Test

What does Cime Unit Test do?

A skill your agent uses when writing/modifying CIME unit tests. Cime Unit Test is an agent skill from ESMCI/cime. Use when writing/modifying CIME unit tests.

When should I use Cime Unit Test?

Cime Unit Test fits situations like: writing/modifying CIME unit tests; tasks that involve Unit testing.

How do I install Cime Unit Test in Claude Code?

Run `npx skills add ESMCI/cime --skill cime-unit-test -a claude-code`. Or copy the skill folder (.agents/skills/cime-unit-testing in ESMCI/cime) into .claude/skills/cime-unit-test in your project. Claude Code loads it when a task matches its description.

How do I install Cime Unit Test in Codex?

Run `npx skills add ESMCI/cime --skill cime-unit-test -a codex`. Or copy the skill folder (.agents/skills/cime-unit-testing in ESMCI/cime) into .agents/skills/cime-unit-test in your project. Codex loads it when a task matches its description.

Can I use Cime Unit Test 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 ESMCI/cime --skill cime-unit-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cime-unit-test, .gemini/skills/cime-unit-test, .github/skills/cime-unit-test and .opencode/skills/cime-unit-test in your project.

What does Cime Unit Test need to run?

Going by SKILL.md and its folder, Cime Unit Test needs the command-line tools its instructions call (pytest). Our summary lists: Python 3.

Does Cime Unit Test 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 Cime Unit Test 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 Cime Unit Test use?

Cime Unit Test has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Cime Unit Test use?

About 543 tokens (SKILL.md is roughly 2.2k 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 Cime Unit Test?

Skills that share tags, products or a category with Cime Unit Test: TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), Testing OpenLogi UI (AprilNEA/OpenLogi, 23k stars), Go Testing (cxuu/golang-skills, 170 stars) and Contracts (samchon/nestia, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cime Unit Test?

ESMCI (a GitHub organization) maintains it in ESMCI/cime, which has 174 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

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