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

- Skill: `leon-sg/orbid-read-compare` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add leon-sg/orbid-read-compare`
- Raw SKILL.md: https://api.skillmd.com/api/skills/leon-sg/orbid-read-compare/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Data & Analytics
- License: MIT
- Author: Leon-SG (https://skillmd.com/u/leon-sg)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/leon-sg/orbid-read-compare

---


# 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).

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