Laravel’s AI SDK 1.1 lets an agent load a skill only when the job needs it: your refund policy, quoting rules, or service area, sitting as files inside the app you already run. That is how custom business software gets agents without stuffing every rule into a giant prompt.
Laravel News covered the 1.1 release on October 7, 2026. It is the first minor release since 1.0. The headline for owners is Agent Skills, the same folder format coding agents use. Each skill is a folder with a SKILL.md file. The agent gets one LoadSkill tool that lists names and descriptions. The model reads the full instructions only when the task needs them, and can pull a bundled reference file from that folder when it needs the fine print.
A refund-policy skill can live next to an EDGE-CASES.md for the 30-day exceptions. A quoting skill can point at your markup rules. A service-area skill can list the towns you actually cover around Statesville, Mooresville, and Lake Norman.
Why this matters if you already have a Laravel app
Most small businesses here do not need a new “AI platform.” They need the application that already holds jobs, customers, and invoices to do one more thing: answer a narrow question or draft a next step, using the same rules the office already follows.
Skills are that layer. You are not pasting the employee handbook into ChatGPT every morning. The agent inside your app loads “use this when a customer asks for a refund” the same way a new hire would open the binder.
Laravel News notes you can implement a HasSkills contract, point at a resources/skills folder, point at the same .agents/skills folder your coding agent uses, or load skills from the database per user or team. That last option is the one that matters for a multi-location shop: Cornelius gets a different coverage skill than Statesville, without a separate product.
The SDK also lets you require approval on built-in tools (MCP, filesystem, similarity search, and the agent tool). Approval is off by default, so existing agents keep behaving the same until you turn it on. Failover between providers no longer dies because the backup provider lacks one hosted tool. Cohere is available for chat, not only embeddings.
You do not need to care about every line of that. You need to care that the agent can be fenced.
What an owner should put in a skill
Write it like you would train a person on day one.
When to use it. What to check first. What never to do. Where the numbers come from.
A Statesville HVAC company might have three skills: after-hours triage, standard install quote ranges, and warranty vs. billable. A Mooresville clinic might have new-patient incomplete forms, no-show outreach, and “this is medical and a person has to answer.” A lake-area shop might have delivery radius and rush fees.
Keep customer records in your database. The skill tells the agent how to use them. That is Laravel development plus AI engineering, not a chatbot bolted onto the marketing site.
AI optimization is still the public-facing job: making sure AI search can cite you. Skills are internal. They are how the app behaves when a real customer is in the workflow.
What this is not
It is not “turn on AI and the app runs itself.” Laravel News’s own Decide with Jev series, published in the same October archive, is explicit: the model should not pick what the app does next. Your code should. Skills load the judgment. PHP still issues the refund, books the slot, or sends the quote.
It is also not a reason to rebuild if you are on a pile of disconnected SaaS tools. If the work still lives in three subscriptions and a spreadsheet, the first conversation is whether a custom app is even the right container. Skills help once the rules and the records have a home.
A practical first skill
Pick the decision your team already repeats ten times a week.
Write one SKILL.md. Connect the agent to the two or three fields it needs (order date, job type, zip code). Require a person before anything that moves money or a calendar. Run it on last week’s real inquiries and see where it guesses wrong. Fix the file. Do not add five more skills until that one is boring.
systemsevendesigns builds custom Laravel apps for businesses around Statesville and Lake Norman, and this is now the default way we attach agents to those apps: skills for the rules you already have, your database for the records, and a person on the decisions that matter. If you want that first skill scoped, bring the policy you already email to customers. That is the document.