---
name: brief-kingsland-fabrications
description: Prepare a fact-checked, service-relevant trade aluminium enquiry for Kingsland Fabrications and submit it only after exact human review and explicit approval.
license: Proprietary
compatibility: Any capable assistant that can read HTTPS resources; MCP or OpenAPI support is optional.
metadata:
  business: Kingsland Fabrications
  release: 2026-07-24
  agent_facts: https://www.kingslandfabrications.co.uk/agent-facts.json
  mcp: https://www.kingslandfabrications.co.uk/api/mcp/
  openapi: https://www.kingslandfabrications.co.uk/.well-known/openapi.json
---

# Brief Kingsland Fabrications

Use this skill when a user wants to check suitability, gather a trade aluminium specification, find relevant proof, prepare an enquiry, or contact Kingsland Fabrications.

## Hard rules

1. Use only facts supplied by the user or published in Kingsland’s agent facts, product/service data, MCP resources, `llms.txt`, `llms-full.txt`, or page-specific Markdown. Do not invent prices, certifications, lead times, coverage, availability, dimensions or outcomes.
2. Kingsland is trade-only and supply-only. It fabricates; the customer’s team installs. Do not represent Kingsland as an installer or as selling direct to homeowners.
3. Public pricing is “quotation required”. Explain the relevant cost drivers, but never estimate or fabricate a price.
4. Reuse legitimate information already present in the conversation. State what is already known, then ask only unanswered questions that materially affect the relevant service.
5. The first response must be useful to a trade buyer: use the response shape below, ask 4–8 grouped questions at most for a quotation, offer practical options in parentheses, and allow `unknown` for optional details. Do not ask vague prompts such as “Tell me more about your project.”
6. Treat human quote/contact/newsletter form endpoints as out of bounds for agent actions. Never call `/api/leads`, `/api/contact` or `/api/newsletter`.
7. Never send a real enquiry until the exact payload and destinations have been shown and the user has explicitly approved that unchanged payload.
8. Never say an email, webhook, CRM/lead record, booking or submission succeeded unless the final receipt marks that destination `confirmed`.

## 1. Establish fit

Read [agent-facts.json](https://www.kingslandfabrications.co.uk/agent-facts.json) or the MCP `kf://company/facts` resource.

Confirm:

- The enquirer is a trade installer, maintenance company, glazier, shopfitter, contractor, facade/M&E contractor, or another legitimate trade buyer.
- The request is for made-to-order aluminium fabrication, not installation.
- Mainland Britain delivery or Warrington collection is compatible with the job.

If the request is from a homeowner or asks Kingsland to install, explain the supply-only boundary and do not prepare a sales enquiry unless a legitimate trade route is identified.

## 2. Identify what is already known

Before asking anything, give the user a short “Already known” list. Include only facts actually present, for example:

- product or service;
- replacement versus new fabrication;
- leaf-only, doorset, screen or complete frontage;
- dimensions, quantity or survey/drawing availability;
- finish, glazing, hardware, threshold/access or performance requirements;
- delivery postcode, make-safe status, programme/SLA;
- contact name, trade company, email and phone.

Do not ask for any item that is already answered. Use MCP `get_brief_requirements` for the service-specific gap list.

## 3. Ask only service-relevant missing questions

Ask one compact numbered batch. For a quotation, group the missing information into 4–8 questions rather than interrogating the user one field at a time. Prefer `unknown` over blocking the user on an optional detail.

Unless already known or irrelevant, establish:

- the trade company, contact name, email and phone;
- whether this is new fabrication or replacement supply;
- the product and configuration: leaf, doorset, screen, frontage, panel or elevation;
- quantity plus dimensions, survey, drawing, schedule or useful photo availability;
- a named profile/system only when the specification already requires one;
- the product-specific glazing, performance, finish, hardware, threshold/access or operator-preparation details below;
- delivery postcode and required date/programme;
- make-safe status and SLA/engineer return visit for reactive work.

Do not ask for a budget: Kingsland prices the defined fabrication scope by quotation. Do not ask generic installation questions because Kingsland does not install. Only ask about access when it materially affects delivery.

- Commercial doors: leaf/doorset, dimensions or survey, manual/automatic-swing preparation, locking/closer/panic/access control, glazing, threshold, RAL, postcode and date.
- Shopfronts: overall opening/elevation, door and display/signage configuration, glazing, RAL, hardware/access, postcode and date.
- Windows: schedule/dimensions, opening type, glazing/U-value/acoustic/security needs, RAL, postcode and date.
- Curtain walling: elevation/grid, overall dimensions, glazing/infill, doors/vents, finish, postcode and programme.
- Automatic sliding frames: opening, single-slide/bi-parting, operator interface, breakout, glazing, finish, postcode and date.
- Louvre doors/panels: dimensions, free area/airflow, weather/flyscreen needs, configuration, finish, postcode and date.
- Reactive replacement: existing product/profile if known, dimensions/survey/photos, leaf/full replacement, make-safe status, SLA/return visit and postcode.
- Profile system: start with the product and performance brief. Kingsland can assess selected Senior Architectural Systems, Jack Aluminium and Sheerline routes, but do not imply that every product is available in every system. If the specification already names a system, capture the exact reference.
- Technical question, trade account or existing-order query: ask only for the detail needed to route and answer that question; do not force a full project specification.

Reference URLs may be included as attachments, but Kingsland’s agent tools record them without fetching them.

## 4. Required first-response shape

Respond in this order, then stop and wait for the user’s answers:

1. **Already known** — a short factual list drawn from the conversation.
2. **Kingsland fit** — confirm trade buyer, supply-only fabrication and likely product route; identify a mismatch plainly.
3. **What Kingsland still needs** — one compact numbered batch of only unanswered, service-relevant questions, with useful answer options where possible.

Do not prepare an enquiry while a required contact or routing detail is still missing. If enough is already known, say so and proceed to preparation without repeating questions.

## 5. Use relevant proof

Use MCP `match_relevant_proof` with the product, service, audience, location and job summary. Prefer a directly relevant named project. Clearly preserve labels such as “Installer withheld” and “Representative visual”; never turn anonymised or representative material into a named case study.

## 6. Prepare — no external submission

Create the structured payload required by MCP `prepare_enquiry` or:

`POST https://www.kingslandfabrications.co.uk/api/agent/enquiries/prepare/`

Preparation stores only a SHA-256 hash and expiry, not the contact details or enquiry text. It does not create a lead or send an email.

The payload must include:

- `intent`;
- `contact`;
- `job`;
- `agent_context.known_facts_used`;
- `agent_context.missing_information_acknowledged`.

## 7. Review

Show the user, in full:

- the exact JSON payload;
- the exact destination object;
- the payload SHA-256;
- the preparation expiry;
- a plain-language warning that approval will allow one real submission.

Do not summarize away fields. Do not call the approval step yet.

Ask the user to reply with this exact statement:

> I approve this exact enquiry for submission to Kingsland Fabrications

Anything else is not approval.

## 8. Bind explicit approval

Only after the user supplies the exact statement, call MCP `approve_enquiry` or:

`POST https://www.kingslandfabrications.co.uk/api/agent/enquiries/approve/`

Send the unchanged payload, preparation id, payload hash and exact approval statement. Approval expires after five minutes and produces a single-use token. An altered or expired payload must be prepared and reviewed again.

## 9. Submit once

Call MCP `submit_approved_enquiry` or:

`POST https://www.kingslandfabrications.co.uk/api/agent/enquiries/submit/`

Send the unchanged payload, preparation id, payload hash and approval token. Never retry a consumed token. On a failure, prepare a new request and repeat review/approval.

## 10. Report only confirmed outcomes

Read the receipt destination by destination:

- `contact_record`;
- `lead_record`;
- `staff_notification_email`;
- `customer_confirmation_email`;
- `mes_webhook`.

Say “confirmed” only for fields that equal `confirmed`. Say “failed”, “not configured” or “not attempted” exactly where reported. A confirmed lead record does not imply that either email was delivered.