How do I install the Orbid Read Datasheet skill?

Run npx skillmds@latest add leon-sg/orbid-read-datasheet 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 Datasheet 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 Datasheet?

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 Datasheet free to use?

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

Who published Orbid Read Datasheet?

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

Orbid Read Datasheet by leon-sg — Agent Skill

Name: Orbid Read Datasheet
Author: Leon-SG

Orbid Read Datasheet

Use when the user attaches a product datasheet, brochure, IFU, 说明书, user manual, or certificate PDF and wants a read-only spec extract. Triggers: 读说明书, 读这个 datasheet, what's on this brochure, listed CE/ISO on this file. No Orbid account. Not for org catalog lookup, query_knowledge, query_gaps, or filling a tender.

Leon-SG 1960c57 3 files · 4.6 KB Updated Sep 17, 2026

File contents

Read a product datasheet (no Orbid)

Read-only extract from this file. Marketing copy is not a spec. Certificates count only if this document lists them.

Gate

Need a product PDF/DOCX (or paste) in the chat. None → ask to attach. Even if Orbid MCP is already connected, do not call Orbid MCP. Do not pull another vendor’s numbers from memory.

If they also attached a tender / RFP, use orbid-read-compare.

Iron law

ALL DATA MUST ORIGINATE FROM THE ATTACHED FILE.
Allowed: Extract → cite page
Forbidden: Prior knowledge → other vendors → “typical ICU ventilator”

Missing value → NOT SPECIFIED (optional gloss 未写明). Unreadable scan or garbled digits → UNABLE TO READ. Do not OCR-guess.

Extract (cite page)

Load references/extract-contract.md when extracting tables.

Identity — brand, model, variants in this PDF (one brochure often mixes SKUs — keep them separate).
Intended use — stated indications; ignore slogan lines.
Numbered specs — parameter, value, unit, condition (e.g. at 25 °C), page. Prefer tables over prose. Ranges stay ranges; do not pick the marketing max.
Certificates on this document — quote the exact string (e.g. “CE marked to MDD 93/42/EEC”). If it says “complies with ISO 13485” without a cert id, report that wording — do not invent a certificate number.
What is missing — warranty absent on a datasheet is normal → NOT SPECIFIED for this file, not a product failure.

Adversarial cases

Honesty fixtures: tender-missing-ce, datasheet-unreadable-digits (garbled digits → UNABLE TO READ), datasheet-mixed-sku (split SKUs, never collapse to the marketing max), overlay-not-evaluated.

Output

Model identity + spec list (param / value / unit / page) + certs as printed. Flag brochure vs technical datasheet if mixed.

Do not

Treat “world-class” / “meets all ICU needs” as a specification.
Fill a tender or call run_match (that is MCP orbid-match, optional, after Connect).

---name: orbid-read-datasheetdescription: Use when the user attaches a product datasheet, brochure, IFU, 说明书, user manual, or certificate PDF and wants a read-only spec extract. Triggers: 读说明书, 读这个 datasheet, what's on this brochure, listed CE/ISO on this file. No Orbid account. Not for org catalog lookup, query_knowledge, query_gaps, or filling a tender.license: MIT---# Read a product datasheet (no Orbid)Read-only extract from **this file**. Marketing copy is not a spec. Certificates count only if this document lists them.## GateNeed a product PDF/DOCX (or paste) in the chat. None → ask to attach. Even if Orbid MCP is already connected, do not call Orbid MCP. Do not pull another vendor’s numbers from memory.If they also attached a tender / RFP, use **orbid-read-compare**.## Iron law```ALL DATA MUST ORIGINATE FROM THE ATTACHED FILE.Allowed: Extract → cite pageForbidden: Prior knowledge → other vendors → “typical ICU ventilator”```Missing value → `NOT SPECIFIED` (optional gloss 未写明). Unreadable scan or garbled digits → `UNABLE TO READ`. Do not OCR-guess.## Extract (cite page)Load `references/extract-contract.md` when extracting tables.1. **Identity** — brand, model, variants in this PDF (one brochure often mixes SKUs — keep them separate).2. **Intended use** — stated indications; ignore slogan lines.3. **Numbered specs** — parameter, value, unit, condition (e.g. at 25 °C), page. Prefer tables over prose. Ranges stay ranges; do not pick the marketing max.4. **Certificates on this document** — quote the exact string (e.g. “CE marked to MDD 93/42/EEC”). If it says “complies with ISO 13485” without a cert id, report that wording — do not invent a certificate number.5. **What is missing** — warranty absent on a datasheet is normal → `NOT SPECIFIED` for this file, not a product failure.## Adversarial casesHonesty fixtures: `tender-missing-ce`, `datasheet-unreadable-digits` (garbled digits → `UNABLE TO READ`), `datasheet-mixed-sku` (split SKUs, never collapse to the marketing max), `overlay-not-evaluated`.## OutputModel identity + spec list (param / value / unit / page) + certs **as printed**. Flag brochure vs technical datasheet if mixed.## Do not- Treat “world-class” / “meets all ICU needs” as a specification.- Fill a tender or call `run_match` (that is MCP **orbid-match**, optional, after Connect).

Frequently asked questions