# Orbid Certs

> Use when the user asks whether a product has ISO, CE, FDA, or other certificates, or for a numeric spec value from the Orbid catalog. Triggers: 有没有证, CE, ISO, query_knowledge, query_structured_specs, datasheet numbers. Requires connected Orbid MCP. Not for match, gaps lists, or filling Excel.

- Skill: `leon-sg/orbid-certs` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add leon-sg/orbid-certs`
- Raw SKILL.md: https://api.skillmd.com/api/skills/leon-sg/orbid-certs/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-certs

---


# Orbid certs and specs

Split **numbers** from **narrative**. Specs are structured; certificates-as-stories live in knowledge.

## Gate

Need Orbid MCP `query_structured_specs` and `query_knowledge` (names may be prefixed). Missing / 401 → stop. Connect `https://app.orbid.dev/mcp`. Do not invent ISO/CE numbers.

## Which tool

| Ask | Tool |
|-----|------|
| Numeric / range / “is it 12.1 inch” / listed cert **codes** on the datasheet | `query_structured_specs` `mode=lookup` with `productId` or `productQuery` |
| “Do we have ISO 13485 for Kenya”, past bids, regulation notes | `query_knowledge` with `query` (optional `country`, `category`, `sessionId`) |

If they named a model and you need a UUID, `search_product_catalog` first.

Prefer specs for parameter values. Prefer knowledge for process / market / “last time we bid”. If both are empty, say the org has no hit — do not quote another company’s certificates.

## Do not

- Treat `query_knowledge` hits as live spec values.
- Fill Excel or run match unless they asked (then **orbid-match**).
- Pass org_id, workspaceId, or skipAutoFill in arguments.