Two things make a plain assistant usable for business: knowing what work to do, and knowing what your business means. Skills handle the first. Memory handles the second. Without either, every conversation starts from zero and you spend the first three messages teaching an AI things it should have known.
What a skill actually is
A skill is not a prompt template. It is a written procedure with the source list, the sequence and the checks built in. A month end close skill knows to read the accounting system, compare it against the payment processor, list the gaps, and report them in a fixed order. You do not have to know that order to ask for it.
CorpusIQ ships 150+ of them, exposed as 500+ tools. When you ask a question, the layer that holds those skills picks the one that matches and runs it. You see the answer, not the routing.
That is why the same question returns a similar shape every time. "What is my cash position" produces a cash figure, the near term obligations, and what is likely to land. Not because the model is clever, but because a procedure ran.
How the assistant picks one
Selection is driven by the words in your question and the sources you have connected. "Churn by cohort" lands on a retention skill. "Which invoices are late" lands on a collections skill. "Is this discount profitable" lands on a margin skill.
Two habits make selection reliable. Name the source when it matters, and name the period. "In Shopify, last 30 days, which products refunded most" is unambiguous. "How are refunds" is a question the routing layer has to guess at, and a guess is where wrong answers come from.
When you notice a question returning a weaker answer than expected, ask for the method: "which sources did you use for that?" The answer tells you whether the right skill ran or whether it improvised.
What memory holds
Memory holds definitions and decisions, not your raw records. Definitions look like this: our fiscal year starts in February, the primary store is the US one, revenue means net of refunds, the west region includes two states people keep omitting.
Decisions look like this: we agreed to stop discounting below 20 percent margin, we treat contractor spend as recurring for planning, the September spike was a one-off promotion. Written once, those stop being re-litigated every conversation and stop being re-explained to a new assistant.
The line that matters: memory stores the meaning, the connector holds the numbers. When a number changes, the connector is right and memory does not need touching. When a definition changes, memory is where you change it.
How to correct an answer so it sticks
A correction in a conversation fixes that conversation. A correction to memory fixes every conversation after it. Most people need both, and they only do the first.
Say the correction plainly and say that it is a standing rule: "for this account, revenue always means net of refunds. Remember that." Next time the question is asked, the definition is already applied and the answer is comparable to the last one.
Keep memory small and factual. Ten definitions that are true beat sixty notes that mix opinion with data. If a definition is contested inside the company, put the settled version in memory and settle the argument somewhere else.
The failure mode to watch for
A business that runs on memory and connectors drifts out of step in one specific way: the definition in memory stops matching what the company actually decided. Someone changes the pricing policy, memory still holds the old rule, and every answer stays internally consistent while being wrong on purpose.
Fix it with a short review rather than a big cleanup. Once a month, open the definitions and ask which one changed. Two minutes. That single habit is the difference between consistent answers and consistently stale ones.
Common questions
Do I have to know which skill to use?
No. The assistant selects it from the words in your question and the sources you connected. Naming the source and the period makes the selection reliable. Asking which sources were used is a quick way to check that the right one ran.
Does memory store my business data?
No. Memory holds definitions, preferences and decisions: what a metric means inside your company, which account is primary, what was agreed. The records themselves stay in the connected systems and are read on demand.
Can team members share the same memory?
Yes. Definitions held at the account level apply to everyone on the account, which is the point: two people asking the same question get the same number. Personal preferences can stay with the individual.
What happens to memory if I disconnect a tool?
Definitions survive, because they describe your business rather than the tool. Questions that depended on the disconnected source stop returning that source's figures until it is reconnected.
How many skills are there?
The catalog covers finance, commerce, advertising, support, CRM, project and operations work, grouped by the function rather than the vendor. The connectors page names what each one reads from.
Try CorpusIQ Free
Give the assistant your definitions once
30-day free trial. Cancel anytime. All 40+ connectors included.
Start free trial →