Solutions
Skills and plugins
A skill is a set of instructions that tells an AI assistant how to do one task the way your company does it. A plugin adds a function to the assistant, and a connector gives it controlled access to one of your systems. Together they let the assistants your team uses work with your own procedures and your own data.
What it is and how it works
Most AI assistants can already write, summarise and answer questions in a general way, but they know nothing about how your company specifically does things unless someone tells them each time. A skill is a written set of instructions, and often example files alongside it, that teaches the assistant your company’s own way of doing one task, so it does not have to be re-explained in every conversation.
A plugin is a smaller addition that gives the assistant a function it did not have before, such as a particular kind of calculation or a specific output format your company relies on. A connector is different again: it gives the assistant controlled, limited access to one of your own systems, such as a document archive or a customer database, so its answers can be grounded in your company’s own information rather than only in general knowledge.
None of the three replaces the assistant your team already uses. They sit alongside it, adding what it was missing for your company specifically, while the assistant itself stays the same tool people already know how to use.
Where it fits
Architecture firms
A skill drafts project descriptions and tender texts in the firm’s own structure and wording.
Accounting firms
A connector lets the assistant search client documents, so answers come from the firm’s own files.
Real estate agents
A skill writes property listings from the firm’s template and checks them against its rules.
How we implement it
The five stages we use are the same for every solution. For skills and plugins, that starts with finding the tasks your team already repeats using AI assistants today, often working around the fact that the assistant does not yet know your company’s own way of doing it, and identifying which systems it would need reaching to do the task properly.
We write one skill for one task with the people who actually do it, testing it on real work rather than a hypothetical example, before it goes anywhere near daily use. Only once that first skill has proven itself do we add further skills, plugins or connectors, each one shaped by how your team actually used the one before it.
What an assistant is allowed to reach stays under your control throughout. We connect only the systems a given skill genuinely needs, at the access level that task requires, rather than opening broad access because it happened to be convenient at the time.
- Soil We find the tasks your team repeats with AI assistants and the systems they need.
- Seed We write one skill for one task with the people who do it, and test it on real work.
- Rooted We install it in your team’s assistants and connect only the systems it needs, with access you control.
- Growth We add skills, plugins and connectors phase by phase, based on how your team used the last one.
- Care We update them when the assistants or your procedures change, and remove what nobody uses.
What it gives your company
Without a skill, the same instructions get typed out again in every conversation, by whoever happens to be using the assistant that day, with small differences each time. With a skill in place, the assistant already knows your company’s own way of doing the task, so the result is consistent regardless of who asked for it.
A connector means the assistant can answer from your own systems directly, rather than a person first having to find the relevant document or record and paste it into the conversation by hand. That step, small as it looks, is often the one that made using an assistant for real work more trouble than it was worth.
As your team’s assistants and your own procedures change, the skills, plugins and connectors around them can change too, rather than becoming a fixed setup that quietly falls out of date while everything around it moves on.
Why Lynggaard Jardim
Lynggaard Jardim is run by its two founders together: Alexander across operations and finance, Victor across web development, AI and IT infrastructure. A skill we write reflects both, how the task is actually done in your company, and how safely it can be connected to your systems.
We work from Copenhagen and build each skill, plugin or connector around the assistants and the systems your team already uses, naming no vendor as a partner and adding only the access a task genuinely needs. What we build follows your own procedures; it does not ask your team to change them to fit a tool.