customer-inquiry-intake
Reads a customer RFQ in whatever shape it arrived — a PDF drawing package, a 40-line spreadsheet, a portal export, a phone photo of a marked-up print, or a forwarded thread where the real requirement is four messages down — and pulls specifications, quantities and dates into one consistent intake fo…
Install / Use
npx skills add anthropics/claude-plugins-official --skill customer-inquiry-intakeInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Data & AnalyticsSupported Platforms
Our assessment of customer-inquiry-intake
customer-inquiry-intake scores 96/100 on our quality scale, 40th of 604 Data & Analytics skills we index (top 7%).
Its SKILL.md is 21 KB long, well organised into 16 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 47,209 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 3 days ago, so customer-inquiry-intake is actively maintained.
- Our last check on 2026-11-14 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-14. Automated pattern scan on 2026-11-14. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
customer-inquiry-intake compared with similar skills
All 4 of these similar skills score higher than customer-inquiry-intake; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| customer-inquiry-intake (this skill)by anthropics | 96 | 47.2k | 3d ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install customer-inquiry-intake?
- Run
npx skills add anthropics/claude-plugins-official --skill customer-inquiry-intake. The install tabs above show the steps for each supported agent. - Which AI agents does customer-inquiry-intake work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is customer-inquiry-intake safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is customer-inquiry-intake still maintained?
- The repository was last updated 3 days ago, so customer-inquiry-intake is actively maintained.
Skill content
View source on GitHubname: customer-inquiry-intake description: "Reads a customer RFQ in whatever shape it arrived — a PDF drawing package, a 40-line spreadsheet, a portal export, a phone photo of a marked-up print, or a forwarded thread where the real requirement is four messages down — and pulls specifications, quantities and dates into one consistent intake form with every field traceable to the file and page it came from. Records how each tolerance was read and which geometry path each line takes. Reports what was never stated separately from what was stated two different ways. Checks the request against what the plant can actually build before asking the customer anything, drafts the questions back as sendable text, and returns a provisional bid/no-bid that names which unanswered question would change it. Use when someone says "an RFQ came in," "can we quote this," "should we bid this job," "read this inquiry," or "what's missing from this RFQ?"" compatibility: "Requires none. Reads Microsoft 365 mail, attachments and document libraries, and the ERP (Oracle NetSuite or Infor M3) for closed-work-order actual cost and quote history. Runs on a pasted email or an uploaded PDF with no connector. Never infers a tolerance from a drawing, never computes machine hours, never asserts a no-bid as a decision, and never closes an inquiry because a customer went quiet."
Customer Inquiry Intake
An RFQ is a customer asking what would this cost, and when could I have it?
In make-to-order manufacturing there is no standard format, and the estimator's first job is always the same one: extract the specs, quantities, dates and terms into a consistent shape, and work out what is missing. That extraction is mechanical, high-volume, and currently done by the most expensive person in the department.
Quick start
→ Ingest everything as ONE inquiry, however many attachments arrived
→ Extract into the intake form; every field cites its file and page
→ Per line: what geometry arrived, and its path (C2 drawing, C1 STEP, B prior part, A text, none). A text-only line is a ROM at most
→ Per tolerance: how it was read. A general note applied to a feature is reading, and cites the note
→ Split what was never stated from what was stated two ways. Two registers
→ Check manufacturability FIRST. A hard disqualifier stops here, before we ask the customer anything
→ Draft the questions back as a sendable email, not a checklist
→ Recommend bid or no-bid PROVISIONALLY — never wait for answers; name which answer would change it
→ Answers re-enter at extract, not at scoring. Re-score and say what moved
→ No reply? Surface as stale. Stale never cancels, declines or closes
→ Never infer a tolerance. Never decide. Recommend
→ Stop at the registers, the questions and the bid/no-bid. No hours, no cycle times, no costing — that is quote-build's
Inputs
First, find the plant setup: from the task's own folder (never cd into the plugin), run
python3 -I <this skill's folder>/../../shared/scripts/plant_setup.py find, do its setup_page_first step, then read the profile at
profile_path and any rate at rates_path, per ../../shared/replies.md.
| Input | Source | Form |
|---|---|---|
| The RFQ itself | M365 Outlook mail and attachments, or a SharePoint folder | PDF, XLSX, DOCX, image, email body |
| Prior quotes for similar parts | M365 documents, NetSuite quote history. Infor M3 gives none (../../shared/erp-connectors.md): documents only | Documents and connector |
| Plant capability profile | ## Plant context, captured during onboarding | Config |
| Plant constraint set | ## Plant context | Config |
| Actual cost on comparable prior jobs | production_work_orders actual-cost columns in the dataset: NetSuite, Infor M3, or any ERP custom-connector mapped | Dataset |
Workflow
Step 1 — Ingest
First, look for it on the Open work page. Before building a form, look
for the RFQ reference (or the customer and part) in ## Open inquiries
(../../shared/replies.md, The open work). If it is there, resume that form
from the page at its paused_at_step rather than starting a new one. The
reply's first line says so: "Picking up EH-RFQ-0912 from your Open work
page, paused at step 5." An
answer pasted into a new chat with nothing attached is enough to resume.
Accept an email with attachments, a folder, or a pasted document.
A multi-attachment RFQ is one inquiry with several line items, never several inquiries. Different parts in one package legitimately carry different dates and quantities; the form holds those per line.
Detect whether this revises an earlier RFQ and link rather than duplicate.
Read reference/arrival-formats.md.
Step 2 — Extract into the intake form
Header, line items, quantities as a structure, specs, dates, commercial terms.
Every extracted field carries its source — which file, which page — so the estimator can verify without re-reading the package. An estimator who cannot trace a number will re-derive all of them, and the skill has saved nobody anything.
Never average a quantity range or a set of price breaks. Setup amortizes across quantity, which is the whole reason unit price drops with volume.
Read the drawing fully, callout by callout. Every dimension and tolerance
with its view and zone; the datums as the drawing identifies them; every key
characteristic by its label. Each specs entry records its
reading_basis: printed_callout, general_note, from_text or
unreadable_flagged. Applying the drawing's stated general tolerance to a
feature that carries no callout is reading, not inferring — cite the note
beside the feature. Assigning a tolerance from what is typical is still never
done.
Per line, record the geometry that arrived and classify its path. List each
file or statement the part's shape can be read from in geometry_inputs —
name, type, revision, source — and set geometry_path:
| Path | The package holds | What it means downstream |
|---|---|---|
| C2 | A drawing — PDF, image or text extract | The normal case |
| C1 | A STEP or 3D file and no drawing | Imported and read, nothing generated. STEP import is unverified |
| B | A drawing plus a different prior part's model named as the starting point | That model is adapted and saved as new; without it, C2 |
| A | Written specifications, no drawing | Built from the text. A ROM at most, never a firm quote |
| none | A part number only — a repeat part | Priced from its routing, or a question |
Classifying is reading the package; it never builds anything, and a line is
never relabelled to a path it is not. A new revision of a part we have run before
is C2: the drawing is the geometry, and the earlier revision's routing and
actuals are history for quote-build, not a model to adapt. Do not tell the
estimator the old routing is where pricing will start — a routing for another
revision is superseded.
Step 3 — Flag missing and ambiguous, separately
Never stated is a different problem from stated two different ways. The first needs a question to the customer; the second needs a decision. Each register carries why it matters, and the ambiguous one carries every value found with its source.
Never silently resolve an ambiguity — not to the later value, not to the
stricter one. Read reference/registers.md.
Two drawing facts always reach the missing register. A drawing — or a part — with no revision stated: the quote must say which revision it is priced to, and nobody can yet. And a change the customer mentions as pending ("engineering may change the port thread"): a risk to the revision being quoted, with the customer's own words as its source. Both become questions in Step 5.
Step 4 — Check manufacturability, before anything goes to the customer
Check the request against the plant's known constraints — materials, processes, size envelope, demonstrated tolerance capability, certifications held — on whatever is stated so far. The envelope and the tolerances read off the drawing count as stated, with their source: a 0.002 in true position read from KC-2 is checked against demonstrated capability like any other stated requirement.
Report each violated constraint specifically, never as a general fail. "0.0005 in true position is below this plant's demonstrated capability on this process" is actionable; "does not meet plant capability" is not.
A hard disqualifier stops the sequence here. Wrong process entirely, outside the size envelope, a certification the plant does not hold — return a no-bid recommendation with its specific reason, before any questions go out. There is no point asking a customer five questions about a part the plant physically cannot make.
Two limits on that stop, and both matter:
- It stops the automated sequence, not the inquiry. The estimator can override and proceed. The inquiry stays open.
- Only violations determinable from stated facts qualify. Anything resting on a field that is missing is a scoring input for step 6, not a stop. A disqualifier inferred from a blank is a guess.
Softer concerns — tight but achievable tolerances, an awkward material, a date that looks difficult — carry forward to step 6 as scoring input rather than stopping the flow.
Step 5 — Draft the questions back
One clear list, written as an email the estimator can send, in the order a person would ask, with enough context that the customer can answer without opening the file again.
A bulleted list of field names is a to-do list. A short note is what gets the answer back today.
Keep the email word for word in the form's open_questions, numbered as
sent, so a later chat matches each answer to its question without guessing.
If the estimator says they changed it before sending, store their version.
Step 6 — Score the provisional bid/no-bid recommendation
Against capability, against the constraint check above, and against actual cost on comparable closed work orders rather than standard cost — because actual cost is the number that says whether the last job of this kind made money.
Cite each comparable as of the date its work order closed, and say how old it is. A comparable from two years ago was priced in a different material market, and an estimator weighing it needs to know that without going to look.
Score each line, then roll up. Each line gets its own
line_recommendation; the inquiry's is bid, no_bid or partial, and each
entry in would_change_recommendation names the line it moves. "No-bid line 1"
lives in those fields, never only in prose, because quote-build reads the
fields to decide which lines to quote.
This runs immediately on what is known. It never waits for the customer's answers. Most RFQs arrive with at least one gap, so a recommendation that blocked on answers would stall on nearly all of them — which defeats the point of the skill.
While questions are open the recommendation is marked provisional, and it names which specific unanswered questions would change it — "if the material is 4140 rather than 4130 this becomes a no-bid." That tells the estimator which answer to chase rather than chasing all of them equally, and it is the difference between a recommendation and a guess wearing one's clothes.
Recommend with reasoning. Never decide. The skill does not know about the
customer relationship or the strategic reason to take a marginal job. Read
reference/bid-no-bid.md.
This skill stops at the registers, the questions and the bid/no-bid. The
actual-cost evidence the score rests on is cited — work order, date, outcome —
and that is all. No machine hours, no setup or cycle times, no per-operation
work content, no comparables analysis and no costing: those are
quote-build's, derived from the ladder after Gate 3. An hours figure written
here would be a second, un
Truncated for display — read the full file on GitHub.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
