Skip to content
Fonsent

Teach it how your team works. A skill is a set of instructions for one kind of request.

Five skills are built in. Duplicate one, edit it, test it in chat, and your team’s way of reviewing a deal becomes the agent’s.

FonsentSkills
The built-in Deal Review skill: its name and description, its files SKILL.md and references/meddpicc.md, version 1, and the controls Test in chat and Duplicate.

In early access today. The AI model isn’t switched on yet. Field updates come from built-in rules, which pick up only sentences that state a value outright. What works today

Good prompts don’t stay put. Where know-how leaks.

  1. It lives in one person’s headYour best rep has a way of preparing for a call. Nobody else has it.
  2. Every request is worded differentlyTen people ask for a deal review and get ten shapes of answer.
  3. Changes leave no traceSomeone improves the instructions. Nobody knows what changed, or when.

How it works. Written once, read when it applies, versioned every time it changes.

What a skill is

Instructions for one kind of request, kept as a SKILL.md file with any reference files beside it. Only the name and description are always in the agent’s context; it reads the rest when a request matches.

Five to start with

Each is a file you can open and read before you rely on it.

  • Build ICP drafts your ideal customer profile from the deals you have won, as a version a person approves.
  • Call Prep builds a one-page brief before a customer meeting.
  • Close Plan lays out a dated plan from today to signature and flags steps that can’t fit.
  • Deal Review inspects one open opportunity against MEDDPICC and its activity history.
  • Follow-up Email drafts a follow-up and places it in For review.

Make it yours

Built-in skills are read-only. Duplicate one to edit your own copy. Every save is a new version, and earlier versions are kept.

Test before you rely on it

Test in chat runs the skill on a real request before your team depends on it.

A skill doesn’t widen permissions

A skill changes what the agent knows how to do, not what it is allowed to do. The Follow-up Email skill says it plainly: it never sends.

Enforced

The same rules, whatever the skill says.

A skill is text. The approval rules are code and database constraints, and they apply to every skill, built in or your own.

A skill that drafts email
The draft waits in For review.
A skill that proposes an ICP
Scoring uses it only after a person approves that version.
A built-in skill
Read-only. Duplicate it to change it.
A saved change
A new version. Earlier ones are kept.

Questions

Can a skill send email or approve a draft?

No. A skill changes what the agent knows how to do, not what it is allowed to do. Email is always a draft, and only a person approves.

What does a skill look like?

A SKILL.md file with a name, a description and the instructions, plus any reference files it points to. The built-in Deal Review skill carries a MEDDPICC reference, for example.

Can I change a built-in skill?

Not in place. Duplicate it and edit your copy; the original stays as it was.

How do I know a change made it better?

Run it with Test in chat on a real request, and compare with the earlier version, which is kept.

Start with your own records.

Create an account, import a CSV or a few emails, and read the first proposals with their quotes. An import is one change you can undo.

Early access. No payment details are asked for.