How do I install the Orbid Read Compare skill?

Run npx skillmds@latest add leon-sg/orbid-read-compare in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Orbid Read Compare safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Orbid Read Compare?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Orbid Read Compare free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Orbid Read Compare?

Leon-SG (@leon-sg) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Orbid Read Compare by leon-sg — Agent Skill

Name: Orbid Read Compare
Author: Leon-SG

Orbid Read Compare

Use when the user attached both a tender/bid and a product datasheet or manual and wants a read-only overlay: does this PDF meet that RFP, 对照标书和说明书, side-by-side, no catalog. No Orbid account. Not for run_match, credits, filling Excel, or org gaps.

Leon-SG 23a5512 3 files · 5.2 KB Updated Sep 17, 2026

File contents

Compare tender vs datasheet (no Orbid)

Read-only overlay of two user files. Not Orbid run_match. No scores, no fill, no catalog UUID.

Gate

Need both: a tender and a product document in this chat. Only one file → extract that side, then ask for the other. Even if Orbid MCP is already connected, do not call Orbid MCP. Do not invent the missing side.

Iron law

ALL DATA MUST ORIGINATE FROM THE ATTACHED FILES.
Allowed: Extract → cite page or sheet on both sides
Forbidden: Prior knowledge → catalog UUID → “typical ICU ventilator”

Missing → NOT SPECIFIED. Unreadable → UNABLE TO READ.

Steps

Load references/overlay-contract.md for the full overlay (this folder is self-contained; do not open a sibling skill file).

Tender extract — shall / must rows: value, unit, mandatory vs preferred (do not collapse). Buyer, lots, deadline, compliance clauses quoted. Cite page or sheet.
Datasheet extract — numbered specs: parameter, value, unit, condition, page. Keep SKUs separate. Certs only as printed.
Align on parameter + unit. Convert units only when both sides state them; otherwise verdict unit unclear.
For each row pick exactly one verdict: meets / short / not in datasheet / not in tender / conflict / unit unclear / not evaluated. Cite pages on both sides. not evaluated ≠ meets.
Regulatory lines: only if both documents mention the same scheme. “CE” on a brochure is not proof against “valid CE certificate under MDR” in the tender — that row is not evaluated unless both sides state the same scheme.

Adversarial cases

Honesty fixtures: tender-missing-ce, datasheet-unreadable-digits, datasheet-mixed-sku, overlay-not-evaluated (tender shall the datasheet never mentions → not evaluated or not in datasheet, never meets).

Output

A table: requirement | tender (page) | datasheet (page) | verdict. Then gaps and questions. No win probability. No “fill the Excel.”

If they want org catalog match or credits, say that needs Orbid MCP (orbid-match) after Connect — do not call it from this skill.

Do not

Call run_match or write xlsx.
Borrow specs from a different model or from memory.
Collapse preferred and mandatory.

---name: orbid-read-comparedescription: Use when the user attached both a tender/bid and a product datasheet or manual and wants a read-only overlay: does this PDF meet that RFP, 对照标书和说明书, side-by-side, no catalog. No Orbid account. Not for run_match, credits, filling Excel, or org gaps.license: MIT---# Compare tender vs datasheet (no Orbid)Read-only overlay of **two user files**. Not Orbid `run_match`. No scores, no fill, no catalog UUID.## GateNeed both: a tender and a product document in this chat. Only one file → extract that side, then ask for the other. Even if Orbid MCP is already connected, do not call Orbid MCP. Do not invent the missing side.## Iron law```ALL DATA MUST ORIGINATE FROM THE ATTACHED FILES.Allowed: Extract → cite page or sheet on both sidesForbidden: Prior knowledge → catalog UUID → “typical ICU ventilator”```Missing → `NOT SPECIFIED`. Unreadable → `UNABLE TO READ`.## StepsLoad `references/overlay-contract.md` for the full overlay (this folder is self-contained; do not open a sibling skill file).1. **Tender extract** — shall / must rows: value, unit, **mandatory** vs **preferred** (do not collapse). Buyer, lots, deadline, compliance clauses quoted. Cite page or sheet.2. **Datasheet extract** — numbered specs: parameter, value, unit, condition, page. Keep SKUs separate. Certs only as printed.3. Align on **parameter + unit**. Convert units only when both sides state them; otherwise verdict `unit unclear`.4. For each row pick exactly one verdict: `meets` / `short` / `not in datasheet` / `not in tender` / `conflict` / `unit unclear` / `not evaluated`. Cite pages on both sides. **`not evaluated` ≠ `meets`.**5. Regulatory lines: only if both documents mention the same scheme. “CE” on a brochure is not proof against “valid CE certificate under MDR” in the tender — that row is `not evaluated` unless both sides state the same scheme.## Adversarial casesHonesty fixtures: `tender-missing-ce`, `datasheet-unreadable-digits`, `datasheet-mixed-sku`, `overlay-not-evaluated` (tender shall the datasheet never mentions → `not evaluated` or `not in datasheet`, never `meets`).## OutputA table: requirement | tender (page) | datasheet (page) | verdict. Then gaps and questions. No win probability. No “fill the Excel.”If they want org catalog match or credits, say that needs Orbid MCP (**orbid-match**) after Connect — do not call it from this skill.## Do not- Call `run_match` or write xlsx.- Borrow specs from a different model or from memory.- Collapse **preferred** and **mandatory**.

Frequently asked questions