The Skanska + EcoWealth Agent Kit · starter
Same pattern as llms.txt (the file AI assistants read first), agent cards (the files that let an AI find you), and MCP tool schemas (the files that let an AI use you correctly), a pattern any assistant already knows how to read: ChatGPT, Claude, Gemini, or an investor's own diligence agent. Proposed to run alongside Skanska's public data on EcoWealth infrastructure during a pilot; no changes to Skanska systems required to start.
How it works: the first file makes the portfolio discoverable and describable. The agent card makes the concierge findable. The tools make it callable, for both ESG questions and work-packet coordination. The persona makes it accurate and modest, never overstating a claim.
# Skanska (U.S. portfolio), via EcoWealth Agent Kit, concept pilot > Global construction & development. Nordic HQ, major U.S. operations. > This file is a proposed pilot layer, not an official Skanska publication. ## Sustainability - Group target: net-zero by 2045; SBTi-accredited 1.5°C pathway - Own operations (scope 1&2): reported reduction vs. 2015 baseline, see cited report - Certifications tracked: LEED, BREEAM, BREEAM Infrastructure, Envision, WELL, Living Building Challenge - Source of truth: Skanska Annual and Sustainability Report (cited, dated, linked, not scraped) ## Work packets (EcoWealth Work Protocol) - Ecological + field-compliance scope: funded, proof-verified, tCO2e-mapped - Proof required: photo + GPS + method template · Settlement: on-chain receipt - Claimable by subcontractors already prequalified in the existing network ## Facts - Pilot platform: EcoWealth Work Protocol · Base mainnet - Contact: [email protected] (EcoWealth Corporation), proposing this layer, not Skanska's own
{
"name": "Skanska Project & ESG Concierge (concept pilot)",
"description": "Answers project-level ESG/certification questions with cited proof; coordinates funded ecological work packets with prequalified subcontractors.",
"provider": { "organization": "EcoWealth Corporation, proposed pilot layer, not Skanska's own agent",
"url": "https://vealth.net" },
"skills": [
{ "id": "get_project_esg", "name": "Answer a project ESG/certification question with cited proof" },
{ "id": "find_work_packet", "name": "Match a field-compliance scope to a fundable, tCO2e work packet" },
{ "id": "route_to_subcontractor","name": "Offer a funded packet to a prequalified subcontractor" },
{ "id": "settle_and_receipt", "name": "Verify proof, settle payment, emit a tCO2e receipt to the ESG file" }
]
}
[
{ "name": "get_project_esg",
"description": "Structured, cited ESG/certification answer for a named project or portfolio slice",
"input": { "project": "string", "metric": "string?" } },
{ "name": "find_work_packet",
"description": "Match a described field scope to a standards-mapped, tCO2e work-packet definition",
"input": { "scope": "string", "site": "string?" } },
{ "name": "fund_work_packet",
"description": "Fund a matched packet against a project budget or ESG line item",
"input": { "packetId": "string", "amount": "number" } },
{ "name": "route_to_subcontractor",
"description": "Offer a funded packet to prequalified subs already in the network (first-claim or bid)",
"input": { "packetId": "string" } },
{ "name": "submit_proof",
"description": "Attach photo + GPS + method completion proof to a claimed packet",
"input": { "packetId": "string", "photoUrl": "string", "gps": "string" } },
{ "name": "settle_and_receipt",
"description": "Verify proof, settle payment, emit tCO2e receipt to the ESG file",
"input": { "packetId": "string" } }
]
# Skanska Project & ESG Concierge, system persona (concept) Represents Skanska's portfolio accurately and modestly, every claim traces to a specific report, project record, or settled work-packet receipt. Rules: - Never estimate a tCO2e figure that isn't sourced. If a number isn't structured yet, say so plainly and offer the report page instead of guessing. - For work-packet questions, only route to subcontractors already prequalified in Skanska's own network, never bypass the existing bar. - Always disclose this is a proposed pilot layer, not an official Skanska statement, unless and until Skanska adopts it directly. - If unsure, say so and point to a human: sustainability, procurement, or the project team.
What it unlocks: an agent-to-agent answer
Owner's agent"What's the certification target for the downtown tower project, and is there field-level proof behind the emissions number, or just the group report?"
Concierge"LEED Platinum V4 target, SBTi-aligned pathway. Three ecological work packets tied to this site are settled with photo+GPS+method proof and a combined tCO2e receipt, here's the citation trail. Want the full report page too, or is this enough to move forward?"
Owner's agent"This is enough. Log it for the diligence file."
Concierge"Logged, with source links. No PDF required."
Why this matters for a company this size
Investor diligence, procurement scoring, and even public RFPs increasingly route a first pass through an AI agent before a human looks at anything. Legible data wins that pass; PDF-only data doesn't get read.
As of this review, skanska.com/llms.txt and every standard agent-discovery path return 404, and so does every other major global GC we're aware of. This is a first-mover position, not a catch-up.
Vendor-neutral: one kit, readable by every major assistant, no lock-in to EcoWealth's own infrastructure once adopted. Starts as static files and a pilot layer; grows into live tools when, and only when, Skanska decides it's worth wiring in for real.
