Agent skill

Optest

Raise a PyLops operator's test coverage above a threshold (default 90%) by adding or modifying tests.

LGPL-3.0Auto-check passedTesting & QA

Install Optest

skills CLI

$ npx skills add PyLops/pylops --skill optest -a claude-code

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

GitHub CLI

$ gh skill install PyLops/pylops optest --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/PyLops/pylops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/optest .claude/skills/optest && 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 "optest" agent skill from https://github.com/PyLops/pylops/tree/dev/.claude/skills/optest into .claude/skills/optest/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "optest", 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/PyLops/pylops/tree/dev/.claude/skills/optest

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 PyLops/pylops --skill optest -a codex

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

GitHub CLI

$ gh skill install PyLops/pylops optest --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/PyLops/pylops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/optest .agents/skills/optest && 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 "optest" agent skill from https://github.com/PyLops/pylops/tree/dev/.claude/skills/optest into .agents/skills/optest/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "optest", 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 PyLops/pylops --skill optest -a cursor

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

GitHub CLI

$ gh skill install PyLops/pylops optest --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/PyLops/pylops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/optest .cursor/skills/optest && 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 "optest" agent skill from https://github.com/PyLops/pylops/tree/dev/.claude/skills/optest into .cursor/skills/optest/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "optest", 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/PyLops/pylops.git --path .claude/skills/optest

--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 PyLops/pylops --skill optest -a gemini-cli

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

GitHub CLI

$ gh skill install PyLops/pylops optest --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/PyLops/pylops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/optest .gemini/skills/optest && 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 "optest" agent skill from https://github.com/PyLops/pylops/tree/dev/.claude/skills/optest into .gemini/skills/optest/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "optest", 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 PyLops/pylops optest

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 PyLops/pylops --skill optest -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/PyLops/pylops.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/optest .github/skills/optest && 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 "optest" agent skill from https://github.com/PyLops/pylops/tree/dev/.claude/skills/optest into .github/skills/optest/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "optest", 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 PyLops/pylops --skill optest -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 PyLops/pylops optest --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/PyLops/pylops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/optest .opencode/skills/optest && 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 "optest" agent skill from https://github.com/PyLops/pylops/tree/dev/.claude/skills/optest into .opencode/skills/optest/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "optest", 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: optest
GitHub stars: 539
Token cost: ~729 tokens
SKILL.md length: 341 words
Files: 1
Skills in repo: 2
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: LGPL-3.0

At a glance

Raise a PyLops operator's test coverage above a threshold (default 90%) by adding or modifying tests.

Works in 7 steps: Locate the operator. Find the source… → Measure baseline coverage for this… → Inspect the uncovered lines in the… → …
The user asks to improve/raise/check test coverage for a specific PyLops operator class (e.g
Calls make and python3
Tasks that involve Test coverage

What it does

Optest is an agent skill from PyLops/pylops. Raise a PyLops operator's test coverage above a threshold (default 90%) by adding or modifying tests. Use when the user asks to improve/raise/check test coverage for a specific PyLops operator class (e.g. "get FirstDerivative to 95% coverage", "improve test coverage for FFT").

Its SKILL.md is about 730 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 Test coverage. It works with Python. The repository describes itself as: PyLops – A Linear-Operator Library for Python. The licence is LGPL-3.0.

When your agent uses it

The user asks to improve/raise/check test coverage for a specific PyLops operator class (e.g
Tasks that involve Test coverage

Example prompts

“get FirstDerivative to 95% coverage”
“improve test coverage for FFT”
“/optest”

Requirements

Python 3

Workflow steps

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

Locate the operator. Find the source module that defines class
Measure baseline coverage for this operator only
Inspect the uncovered lines in the source module. For each missing line,
Add or modify tests in the existing pytests/test_*.py file for this
Re-run .pi/tools/operator_coverage.sh and iterate steps 3–4
Validate the new tests actually pass and lint cleanly
Report a short summary: starting %, final %, which test functions were

What it can do on your machine

Read from SKILL.md and the folder at commit 2f06397. 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:
- make
- python3
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

Optest loads about 729 tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 341 words of instructions outside code blocks.

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

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 PyLops/pylops at commit 2f06397, republished under its LGPL-3.0 licence (© PyLops). 341 words, ~729 tokens.

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

name: optest
description: Raise a PyLops operator's test coverage above a threshold (default 90%) by adding or modifying tests. Use when the user asks to improve/raise/check test coverage for a specific PyLops operator class (e.g. "get FirstDerivative to 95% coverage", "improve test coverage for FFT").

Goal: bring test coverage for a given PyLops operator class to at least a target percentage (default 90%).

Expect the invocation to include an operator class name (e.g. FirstDerivative, FFT) and optionally a target percentage. If the operator name is missing, ask for it before proceeding.

Follow this workflow precisely:

Locate the operator. Find the source module that defines class <Operator> (e.g. grep -rln "^class <Operator>\b" pylops/) and the test file(s) that already exercise it (grep -rln "<Operator>" pytests/).
Measure baseline coverage for this operator only:
bash
```
.pi/tools/operator_coverage.sh <Operator>
```
Read the reported percentage and the list of missing line numbers.
Inspect the uncovered lines in the source module. For each missing line, identify what behaviour is untested: alternate dtypes, branches (e.g. kind/edge/order options), error paths (raise/NotImplementedError), adjoint vs forward, ND vs 1D, backend dispatch, etc.
Add or modify tests in the existing pytests/test_*.py file for this operator. Match the repo's conventions:
- Parametrize with @pytest.mark.parametrize over par dicts and dtype.
- Always include a dottest(...) adjoint check for new configurations.
- Use assert_array_almost_equal for forward/inverse comparisons.
- Keep the CuPy/backend guard pattern used at the top of the test file. Do NOT weaken assertions or add trivial no-op tests just to hit lines.
Re-run .pi/tools/operator_coverage.sh <Operator> and iterate steps 3–4 until COVERAGE_PCT >= <target>. If some lines are genuinely untestable on the current backend (e.g. CUDA-only paths), say so explicitly and exclude them from the target with justification rather than faking coverage.
Validate the new tests actually pass and lint cleanly:
bash
```
make lint
```
(run the relevant pytest file directly if a full make tests is too slow).
Report a short summary: starting %, final %, which test functions were added/changed, and any lines deliberately left uncovered with the reason.

The coverage-measurement tool lives at .pi/tools/operator_coverage.sh (repo root, two levels up from the script's own location) — it locates the operator's source module, runs pytest scoped to it, and prints coverage % plus missing line numbers. Usage: .pi/tools/operator_coverage.sh <OperatorName> [extra pytest args...]. Runner selection: $RUNNER env var, else uv run if uv is on PATH, else python3 -m coverage.

Files

Just SKILL.md in .claude/skills/optest of PyLops/pylops.

Open the folder on GitHubat commit 2f06397

Compare with similar skills

Optest 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.

Optest compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Optest this skillPyLops/pylops	539	—	~729	Automated safety check: Pass	LGPL-3.0	today
Find Untested Sourcesdotnet/skills	5.6k	1 repos	~3.3k	Automated safety check: Pass	MIT	today
Test Coverage Reviewareed1192/finance-news-aggregator	149	—	~2.6k	Automated safety check: Pass	MIT	5 mo ago
Supercovsupercorp-ai/supercov	150	1 repos	~415	Automated safety check: Pass	MIT	today
Review OpCVCUDA/CV-CUDA	2.7k	—	~481	Automated safety check: Pass	Custom licence	21 days ago
Supercov Securitysupercorp-ai/supercov	150	1 repos	~236	Automated safety check: Pass	MIT	today

Similar skills

Find Untested Sources
dotnet/skills
Official
Statically pairs source files with test files to list code that no test references, using Roslyn for C# or tree-sitter for many languages, with no build.
5.6k GitHub starsUsed in 1 repo~3.3k tokens
Testing & QAAuto-check passed
Test Coverage Review
areed1192/finance-news-aggregator
Audit, plan, write, and verify unit tests for Python projects using pytest.
149 GitHub stars~2.6k tokensUpdated 5 mo ago
Testing & QAAuto-check passed
Supercov
supercorp-ai/supercov
Measures test coverage and code quality in a repository with the supercov CLI, and turns what it finds into small, focused tests or fixes.
150 GitHub starsUsed in 1 repo~415 tokens
Testing & QAAuto-check passed
Review Op
CVCUDA/CV-CUDA
Review a CV-CUDA operator end-to-end (support / test / bench / docs coverage).
2.7k GitHub stars~481 tokensUpdated 21 days ago
Testing & QAAuto-check passed
Supercov Security
supercorp-ai/supercov
Scans a repository's source for security vulnerabilities with the supercov CLI, pointing to the line of each finding and mapping it to CWE classes.
150 GitHub starsUsed in 1 repo~236 tokens
Testing & QAAuto-check passed
Test Coverage Improver
openai/openai-agents-python
Official
Measure Python SDK coverage or address measured coverage gaps.
30k GitHub stars~687 tokensUpdated today
Testing & QAAuto-check passed

Questions about Optest

What does Optest do?

Raise a PyLops operator's test coverage above a threshold (default 90%) by adding or modifying tests. Optest is an agent skill from PyLops/pylops. Raise a PyLops operator's test coverage above a threshold (default 90%) by adding or modifying tests.

When should I use Optest?

Optest fits situations like: the user asks to improve/raise/check test coverage for a specific PyLops operator class (e.g; tasks that involve Test coverage.

How do I install Optest in Claude Code?

Run `npx skills add PyLops/pylops --skill optest -a claude-code`. Or copy the skill folder (.claude/skills/optest in PyLops/pylops) into .claude/skills/optest in your project. Claude Code loads it when a task matches its description.

How do I install Optest in Codex?

Run `npx skills add PyLops/pylops --skill optest -a codex`. Or copy the skill folder (.claude/skills/optest in PyLops/pylops) into .agents/skills/optest in your project. Codex loads it when a task matches its description.

Can I use Optest 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 PyLops/pylops --skill optest -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/optest, .gemini/skills/optest, .github/skills/optest and .opencode/skills/optest in your project.

What does Optest need to run?

Going by SKILL.md and its folder, Optest needs the command-line tools its instructions call (make and python3). Our summary lists: Python 3.

Does Optest 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 Optest 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 Optest use?

Optest is published under the LGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Optest use?

About 729 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 Optest?

Skills that share tags, products or a category with Optest: Find Untested Sources (dotnet/skills, 5.6k stars), Test Coverage Review (areed1192/finance-news-aggregator, 149 stars), Supercov (supercorp-ai/supercov, 150 stars) and Review Op (CVCUDA/CV-CUDA, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Optest?

PyLops (a GitHub organization) maintains it in PyLops/pylops, which has 539 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.

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

Optest

Install Optest

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

Find Untested Sources

Test Coverage Review

Supercov

Review Op

Supercov Security

Test Coverage Improver

More from PyLops/pylops

Newop

Questions about Optest

Install Optest

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

Find Untested Sources

Test Coverage Review

Supercov

Review Op

Supercov Security

Test Coverage Improver

More from PyLops/pylops

Newop

Related

Questions about Optest