What is xlsx-to-qmetry?

A workflow for importing test cases from Excel workbooks into QMetry Test Management, a tool for organizing software tests.

Importing one or more .xlsx files, detecting their structure, organizing cases into QMetry folders, and setting selected statuses, components, and custom fields.

It removes the need to enter many spreadsheet-based test cases into QMetry one by one and supports repeatable imports.

How salehrifai42/qmetrymcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to salehrifai42/qmetrymcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/salehrifai42/qmetrymcp/main/.claude/skills/xlsx-to-qmetry/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/salehrifai42/qmetrymcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/salehrifai42/qmetrymcp/xlsx-to-qmetry/github.svg)](https://agentmods.dev/skills/salehrifai42/qmetrymcp/xlsx-to-qmetry)

Your own site

<a href="https://agentmods.dev/skills/salehrifai42/qmetrymcp/xlsx-to-qmetry"><img src="https://agentmods.dev/badge/skills/salehrifai42/qmetrymcp/xlsx-to-qmetry/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/salehrifai42/qmetrymcp/xlsx-to-qmetry"><img src="https://agentmods.dev/badge/skills/salehrifai42/qmetrymcp/xlsx-to-qmetry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,698 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00094	$0.02698
Opus 5	$0.00047	$0.01349
Sonnet 5	$0.00019	$0.00540
Haiku 4.5	$0.00009	$0.00270

Measured 12d ago against content hash 5875c514dd0e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

xlsx-to-qmetry scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

**The API key is NOT stored in `config.json`** — it lives only in the `QTM4J_API_KEY` env var (or the MCP launcher's `-e` flag). `config.json` has no `connection` block; don't try to read `apiKey` from it. The currently-

.claude/skills/xlsx-to-qmetry/SKILL.md · 165 lines

How it starts

The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.

xlsx → QMetry import

Triggered when the user wants to push a batch of Excel test cases into QMetry. Reference: docs/EXCEL-IMPORT-GUIDE.md.

Folder collapse rule: if a category subfolder contains exactly one workbook, the workbook-stem level is skipped — test cases land directly under the category folder. Categories with ≥2 workbooks keep the full category/workbook-stem/<cases> layout. The dry-run plan tags collapsed entries with [flatten].

Workflow (follow exactly)

Step 1 — Ask the user, in one batch, what's tenant-specific

Before any parsing, confirm:

Input folder path (e.g. Input/<batch-name>) — must exist on disk.
QMetry parent folder ID to nest under (default from config.json → xlsxImport.parentFolderId).
Component(s) to attach (default from config.json → xlsxImport.componentIds; empty list = none).
Status for new test cases (default from config.json → xlsxImport.statusId).
Whether the API Test custom field rule (Test Type == "API" → Yes, else No) still applies. If not, ask which custom fields they want set instead.

Don't assume defaults from a previous run — different batches go into different folders / components.

Step 2 — Sanity check the input

ls "<input-folder>"
find "<input-folder>" -name "*.xlsx" | wc -l

If the count is zero, stop and ask the user.

Step 3 — Verify the API key is current

The API key is NOT stored in config.json — it lives only in the QTM4J_API_KEY env var (or the MCP launcher's -e flag). config.json has no connection block; don't try to read apiKey from it. The currently-exported env var can be stale because the running MCP server caches its own copy at startup and keeps working even after the key rotates. Always verify with a direct curl that talks to the live API:

curl -s -H "apiKey: $QTM4J_API_KEY" -H "Accept: application/json" \
  "https://qtmcloud.qmetry.com/rest/api/latest/projects/<project-id>/testcase-folders" \
  -o /dev/null -w "%{http_code}\n"

Read the full file on GitHub · 165 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 165 lines · 94 tokens per session scan A 5875c514dd0e

Subscribe to this mod's changes

xlsx-to-qmetry is a skill published in the GitHub repository salehrifai42/qmetrymcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 94 tokens to every session and 2,698 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

qmetrymcp: Skill for Claude Code