THE SHORT VERSION
A model provides capabilities. Tools let a system act. Skills describe methods. An agent coordinates steps toward a goal. Connectors provide access, plugins package extensions, and artifacts are the things you make.
01 / THE HUMAN ANALOGY
A useful comparison. Not a literal brain.
You already know that having hands and knowing how to play piano are different things. You also know that being a wonderful pianist does not automatically make someone a wonderful runner. Those ordinary distinctions make AI terminology much easier to understand.
Think of an AI system as a combination of capabilities, ways to act, instructions, and access to information. The human analogy helps us separate those parts. It does not mean an AI system has a human mind, intentions, feelings, or a biological body.
AI is the broad field of building systems that perform tasks associated with intelligence. A language model is one kind of component within that field. It generates language using patterns learned during training and the information available in its current context. Other models work with images, sound, video, or combinations of these.1
02 / THE VOCABULARY
Eight terms. One everyday picture.
| Term | A useful human comparison | What it means in AI |
|---|---|---|
| AI | The broad idea of intelligent activity | The field and the systems built within it; not a single product or model. |
| Model | A set of learned mental capabilities | A trained system that processes inputs and produces outputs, such as text or images. |
| Tool | A hand, a voice, or an instrument | A callable function or program that performs a particular operation. |
| Skill | A practiced method or a recipe | Reusable task instructions, often packaged with scripts, examples, or other resources. |
| Agent | A person carrying out an assignment | A system that uses a model to choose and carry out steps toward a goal, within its available tools and limits. |
| Connector | An authorized line to someone or somewhere | An integration that gives an application access to a service or data source. |
| Plugin | An equipment kit | A product-specific extension that can bundle tools, connections, instructions, or other features. |
| Artifact | The drawing, report, or performance you produce | A usable output: for example, a document, spreadsheet, image, or small application. |
These labels are not a universal anatomy. Products use them differently, and one feature may fit more than one label. The useful question is what the component actually does.
03 / MODELS & MINDSETS
The model is the capability. The prompt sets the approach.
Imagine asking two people to explain a difficult idea. One gives a quick, plain-language answer. Another works through the details slowly. Both might help, but in different situations. Models also differ in their strengths and trade-offs.
A model may be strong at writing, coding, reasoning through a complex problem, interpreting images, or handling speech. Some tasks need a fast, inexpensive response; others benefit from more computation and careful checking. A larger model is not automatically the best choice for every task.
Those differences come from how models are built and trained: their design, training material, training methods, and the computation used to produce a response. Some are built for broad use; others specialize. Think of a runner and a pianist: neither comparison makes sense until you say what you need them to do.
A prompt is the instruction or information you give the system. Asking it to “explain this to a beginner” is a little like asking a person to adopt a teaching mindset. It changes the requested approach; it does not replace the underlying model or give it new qualifications.
- Capability: can it do this kind of task reliably?
- Input and output: can it work with the text, image, audio, or video involved?
- Context: can it handle the amount of information the task requires?
- Trade-offs: are its speed, cost, and deployment constraints appropriate?
- Evidence: how does it perform on examples of your actual work?
Instead of asking which model is “smarter,” ask which model, with which tools and information, performs this task well enough. A polished answer is not evidence that its facts are correct.
04 / TOOLS & SKILLS
Hands are useful. Knowing what to do with them is different.
A tool gives an AI system a way to do something beyond generating its next response. A calculator can calculate. A browser tool can retrieve a page. A document tool can create or edit a file. In our analogy, these are the hands, senses, and instruments available to the system.
A skill supplies a reusable method for a task. For a presentation, that method might cover the audience, the narrative, the slide structure, and a final layout check. In systems that support packaged skills, it can include instructions, scripts, examples, and reference material.2
Walking, running, and jumping use overlapping body parts but different coordination. The same is true of making a budget, building a chart, and checking a financial model: the tools can overlap while the methods differ.
The analogy has a limit. Installing a skill usually provides instructions and resources. It is not the same as a person practicing for years, and it does not, by itself, retrain the model.
05 / AGENTS & WORKFLOWS
An agent connects the steps.
An agent is a system that uses a model to decide what to do next while pursuing a goal. It may choose a tool, inspect the result, and choose another step. The surrounding software manages execution, access, and limits. An agent is not necessarily a new or separate model.3
A workflow follows a predefined route, like a fixed warm-up routine before a run. An agent can choose among steps based on what happens, like adjusting a route when a path is closed. Real applications often combine both approaches.
More independence is not always better. A clear stopping point matters. Finding an available lesson, drafting a booking, and paying for it are different levels of authority. The system should know which actions it can take and which need your approval.
06 / CONNECTORS & PLUGINS
Access is different from ability.
Knowing how to read a calendar does not give someone access to yours. A connector is the integration that lets an AI application reach a particular service or data source, with the permissions you have granted.
For example, a calendar connector might expose tools for finding free time or creating an event. A read-only connection can support checking availability without allowing bookings. Some connections expose only information; others also allow actions.
MCP, short for Model Context Protocol, is one standard applications can use to connect to external tools and information. It is a connection standard, not a model, and it does not itself grant permission to your accounts.4
Plugin is a broader product label. Think of it as an equipment kit: it may package tools, connectors, skills, or other features. A plugin and a connector can overlap. Always check what a particular product includes and what access it requests.
07 / ARTIFACTS
The artifact is what you can take away.
If drawing is the activity, the finished illustration is an artifact. If planning a concert is the assignment, the schedule and budget are artifacts. In AI products, the word commonly describes a usable output that stands on its own: a document, spreadsheet, image, dashboard, or small application.5
The distinction is useful because discussing a budget is different from receiving a working spreadsheet. Ask for the thing you want to use, then check whether it is complete, editable, accurate, and in the right format.
08 / TRAINING, CONTEXT & MEMORY
More information is not always more experience.
People get better at a sport through practice, feedback, and changes in their bodies and habits. An AI application can appear to improve for several different reasons. Separating those reasons helps you choose the right improvement.
- Training and fine-tuning change a model’s learned parameters. Think of this loosely as changing underlying learned capabilities.
- Context is the information supplied for the current response, such as instructions, conversation history, examples, and retrieved documents. Think of the notes in front of you.
- Saved memory is an application feature that stores selected information and may bring it into later interactions. Think of a notebook you can consult. What is saved and reused depends on the product.
- Retrieval looks up relevant information and supplies it as context. Finding a new page in a manual is not the same as rewriting the model.
Correcting an answer can improve the next response because the correction is now in context. That does not establish that the model’s parameters changed or that it will remember the correction next month. Whether conversations are used for later training is a separate, product-specific policy.
09 / PUTTING IT TOGETHER
Build a useful setup, not a collection of labels.
Imagine you want a weekly practice plan. The model helps interpret your goal. A skill guides the plan’s structure. A calendar connector provides authorized access to free time. Calendar tools retrieve available slots. An agent coordinates those steps. A plugin might package some of those capabilities. The plan you receive is the artifact.
The same pattern applies at work. Preparing a clear delivery update may require a suitable model, access to project information, a repeatable reporting method, and a document or dashboard as the result. Buying a more powerful model will not fix missing access or unclear goals.
- Start with the outcome: what should exist when the task is finished?
- Choose the capability: what must the model be able to interpret or produce?
- Provide the information: what context and authorized access does it need?
- Define the method and boundaries: what should it follow, check, and ask permission for?
- Evaluate the result: did it work on your real task, and can you verify it?
10 / QUICK ANSWERS
A few common questions.
Is an AI model a human brain?
No. The brain is a living biological organ. An AI model is a computational system with learned parameters. Neural networks use connected mathematical units, but the human comparison in this article is a guide to the roles of different components, not a claim that they work or experience the world in the same way.
Is an AI model the same as an agent?
No. A model provides capabilities such as language generation or image interpretation. An agent is a system that uses a model to choose and carry out steps toward a goal, usually with tools and execution controls.
What is the difference between a tool and a skill?
A tool performs an operation, such as reading a calendar or editing a spreadsheet. A skill provides a reusable method for a task and can include instructions, examples, scripts, and resources that guide tool use.
Does adding a skill train the model?
Not by itself. A skill generally adds task guidance and resources. Model training and fine-tuning change learned parameters; supplying instructions or reference material does not necessarily change them.
Does a connector give AI access to all my data?
Access depends on the service, connector, account, and permissions you authorize. A connection can be limited to particular resources or read-only operations. Check the actual permission scope.
Are bigger models always better?
No single measure determines the right model. Compare task performance, supported inputs and outputs, speed, cost, context requirements, and deployment constraints using examples of your actual work.
Sources & further reading
These sources support the technical distinctions. The human comparisons are explanatory analogies. Terminology and product features evolve.