# Inventory Lookup

> Answer questions about a developer's live inventory in QubeHub — available units, prices, statuses, unit stats per project, price history — through the QubeHub connector. Use for "what is available in", "price of unit", "how many 2-beds are left", "did the price change", unit selection for a buyer.

- Skill: `qubehub-ai/inventory-lookup` (Agent Skill)
- Install (CLI): `npx get-skill add qubehub-ai/inventory-lookup`
- Raw SKILL.md: https://api.skillmd.com/api/skills/qubehub-ai/inventory-lookup/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: qubehub-ai (https://skillmd.com/u/qubehub-ai)
- Updated: 2026-11-19
- Page: https://skillmd.com/skills/qubehub-ai/inventory-lookup

---


# Inventory lookup

Inventory is the one thing the business cannot get wrong: a unit quoted as available when it is reserved, or an old price, is an incident. Every answer is live data from this session.

## Gather

1. Resolve the project by name with the projects search tool; confirm with the user when the name is ambiguous.
2. Use the unit search with explicit filters (project, status, bedrooms, floor, price range). Do not list a whole project when a filter answers the question.
3. For a single unit, read the unit card; for "did it change", read its price or status history.
4. Use the unit stats tool for counts per status instead of counting a list yourself.

## Write

- Table for lists: unit number, type, floor, area, price with currency, status. Sort the way the user asked, otherwise by price.
- One line per unit for a short selection; always include the status word the CRM uses.
- State the moment of truth: "as of this query"; never imply a hold or a reservation.

## Rules

- Never quote a price that did not come from a tool result in this conversation.
- Units that are reserved or sold are not "available" even if the buyer likes them; say so.
- If the connector hides a project (visibility, role), it does not exist for this user.

