Docs · Behavior
Teach it once. It sticks.
A skill is a playbook Cedric follows: your report format, your tone, your rules for a tool. Saved in a sentence, shared with the team, removable in a click.
- A skill is written instructions, not code: what good looks like for your team, in plain language.
- Save one from chat in a sentence: "from now on, do it like this" becomes a named, durable behavior.
- Skills are team-wide or just for you, and the Skills page lists every installed one.
- The catalog has ready-made playbooks; anything installed is visible in full, never a black box.
- Most "can Cedric do X better?" gaps are behavioral. A skill fixes them in minutes.
Behavior is teachable
When Cedric's work is almost right, the gap is usually taste, not ability: the report opens with the wrong thing, the reply is too long, the numbers are not in the house format.
Skills close that gap. You state the rule once, it becomes part of how Cedric works for the whole team, and it stays until someone removes it.
Taught once
Sam Okonkwo
From now on, every weekly report opens with the three numbers that changed most.
CedricApp
Saved as a team skill.
Weekly report format · team
Lena Brunner
The weekly report, please.
Every report after
Weekly report
The loop: one sentence becomes a team skill, and every report after opens the way Sam asked, whoever requests it.
Save from chat
"From now on" actually means from now on.
Sam Okonkwo9:14 AM
@Cedric from now on, every weekly report opens with the three numbers that changed most.
CedricAPP9:15 AM
Saved as a team skill: "Weekly report format". Every report now leads with the three biggest movers. It is listed on the Skills page, one click to edit or remove.
A sentence is enough
No settings screen, no template editor. State the rule where you already work and it becomes durable.
The whole team inherits it
A team skill shapes everyone's results, so the standard is set once instead of person by person.
Visible in full
Open any skill on the Skills page and read exactly what it tells Cedric. No hidden behavior.
Install from the catalog
The playbook someone already wrote.
Maya Chen10:02 AM
@Cedric install the support replies skill from the catalog.
CedricAPP10:03 AM
Installed for the team: support replies stay short, lead with the fix, and link the relevant doc. You can read the full playbook or uninstall it on the Skills page.
Ready-made starting points
The catalog covers common jobs and connected tools, so the first improvement takes a minute, not a workshop.
Per-tool playbooks
Some skills teach Cedric how to behave inside a specific tool, and they load only when that tool is in play.
Any member can manage them
Installing and removing team skills takes the same standing as connecting a team tool. No admin bottleneck.
FAQ
An automation is work on a schedule; a skill is how the work is done. "Send the report every Friday" is an automation. "Reports open with the three biggest movers" is a skill. They combine well.
Skills are visible text, so a conflict is fixable the honest way: open the Skills page, read them, edit or remove one.
No. Skills shape style and approach; the approval gate is structural and sits underneath. Anything that sends, changes records, or spends still asks first.
Only the catalog and your own team. Cedric never picks up instructions from third parties on its own.
Ready when you are
Set the standard once.
Install Cedric, hand it a task, and teach it your way in a sentence. $50 in free credits, no card needed.
$50 in free credits, no card needed.