Skills

Skills are reusable expertise blocks Toffu loads into the conversation when they are relevant. The best way to create, change, list, or delete a skill is to ask Toffu in the chat. The Skills page in the sidebar is an inspector, not the primary tool.

Manage Skills by Chatting

Every skill operation is one prompt. Toffu will confirm and do it.

Create a skill

You: Save this as a skill: when writing LinkedIn posts, lead with the problem the content addresses, not the product announcement. Keep it under 150 words. Short paragraphs. No exclamation marks. End with a question.

You: Create a skill called "report-format". Every report I get from you should start with a 3-bullet executive summary, use H2 for main sections, and end with exactly 3 concrete next-step recommendations.

You: Turn the feedback I just gave you in this chat into a skill so you don't need correcting next time.

List skills

You: What skills do I have?

You: List all my skills at the agency level.

You: Show me every skill that mentions reporting.

Read a skill

You: Show me the full content of the brand-voice skill.

You: What does my competitor-analysis skill say?

Update a skill

You: Update the brand-voice skill: also avoid the word "robust" and add that contractions are encouraged.

You: Rename "lp-rules" to "landing-page-rules" and tighten the description.

You: Disable the report-format skill for now.

Change the scope of a skill (move tiers)

You: Move the report-format skill to the agency level so every client gets the same report structure.

You: Make the report-format skill personal to me
other people in this workspace should not see it.

You: Promote this skill to the workspace so my whole team uses it.

Delete a skill

You: Delete the old-pricing skill.

You: Remove every personal skill I have that mentions "draft".

Why chat is better than the UI

One prompt covers create, list, update, scope changes, and delete. The UI needs separate clicks for each.
Toffu writes the skill text for you. You describe the rule, it produces the wording.
Skills you build while chatting capture how you actually work, not what you remembered to write down on a blank form.
Bulk operations ("delete every skill that mentions X", "move all my marketing skills to the agency") are one sentence, not 20 clicks.

What is a Skill?

A skill is a named block of expertise. Each skill has:

Name - a short identifier
Description - one line explaining when it applies
Content - the actual rule or knowledge
Scope - who can use it (see below)

Toffu reads the description across every conversation. When it looks relevant, Toffu loads the full content automatically. You do not have to mention or trigger a skill for it to apply.

Skill Examples

Skills are usually a few sentences to a few paragraphs. The more specific, the more useful.

Brand Voice

Write in a direct, conversational tone. Use short sentences. Prefer active voice. Never use corporate jargon - avoid words like "leverage", "synergy", "streamline", "best-in-class", "cutting-edge", and "robust". Don't use filler phrases like "In today's fast-paced world" or "It goes without saying."

When writing copy, lead with the concrete benefit or problem - not with our company name or product features. Readers care about their situation first.

Humor is fine but keep it dry. No exclamation marks except in truly exceptional cases. Contractions are encouraged (we're, you'll, it's). Write like you're explaining something to a smart colleague, not presenting to a board.

Target Audience

Our primary buyers are heads of marketing and VP-level marketers at B2B SaaS companies. Company size: 50 to 500 employees. They are measured on pipeline and revenue, not on vanity metrics. They're often skeptical of AI hype and respond better to specifics and ROI numbers than to abstract promises.

Secondary audience: marketing managers who report to the above, who are doing hands-on execution. They care about time savings and ease of use.

We don't sell to enterprise (500+ employees) or to SMBs under 20 employees. If content or outreach targets those segments, flag it.

Report Format

All reports and analysis should follow this structure unless the user asks for something different:

Start with an executive summary: 3 bullet points maximum, each under 20 words.

Use H2 headers for main sections. Don't nest more than two levels deep.

End every report with a "What to do next" section containing exactly 3 concrete recommendations. Each recommendation should include who does it, what they do, and an approximate timeframe.

Keep tables simple - no more than 5 columns. Do not add a conclusion section that just restates the summary.

Building Skills From Conversation Feedback

The fastest skills come from real work, not from a blank form.

Start a chat and work on something real - a piece of content, an analysis, a report
When Toffu gets something wrong, correct it
When it gets something right, note what worked
At the end, ask Toffu to turn those corrections into a skill

Example:

You: Write a LinkedIn post about our new HubSpot integration.

Toffu: [writes a formal announcement post]

You: Too formal. We don't lead with announcements - we lead with the problem it solves. Also shorter, no exclamation marks, and no phrase like "we're thrilled to announce."

Toffu: [rewrites]

You: Better. One more thing - always end with a question to drive comments.

Toffu: [rewrites again]

You: Turn what you've learned in this conversation into a skill I can save.

Toffu: Saved as "linkedin-post-rules". I will apply it in every future chat.

Prompts that work well:

"Turn the feedback I just gave you into a skill"
"Based on this conversation, what skill would mean you don't need correcting next time?"
"Write a skill that captures how we've been working in this chat"

For Agencies

If you are inside an agency workspace or any client workspace under it, you get one extra scope: Agency.

An agency-scoped skill is written once and applies in every client workspace under the agency. Each client sees it in their Skills list. Change the agency skill once and the update is live for every client immediately. No copy-paste across workspaces.

Use it for:

Reporting templates the agency standardizes on
QA checklists every account manager runs before launching a campaign
Pacing and budget guardrails the agency applies the same way to every client
Compliance, disclaimer, or process rules that should never drift between clients

Per-client knowledge - the actual brand voice, target audience, positioning, the things that differ between clients - stays at the client tier, not the agency tier.

How to set it:

You: Save this report-format skill at the agency level so every client gets it.

You: Move the QA-checklist skill to the agency tier.

Client-specific knowledge stays at the client. Agency-wide rules live at the agency tier and layer on top.

Skills vs. Playbooks

	Skills	Playbooks
What it is	Background expertise Toffu loads when relevant	Step-by-step workflow you run on demand
When it applies	Automatically, when the topic comes up	Only when you trigger it
Best for	Rules, voice, domain context	Repeatable multi-step tasks

Use a Skill when you keep explaining the same context, want a consistent style, or have rules Toffu should always follow.

Use a Playbook when you have a defined process you want Toffu to execute the same way every time. See Playbooks for how to build them.

The Skills Page

The Skills page in the sidebar is for inspecting and toggling - viewing full skill content, reading other people's skills in your workspace, and turning built-in system skills on or off. You can also create or edit a skill manually there if you prefer a form. For everything else, the chat is faster.