knowledge-setup

Knowledge setup

The knowledge folder is what your agent knows about a company: what it sells, its offer and prices, who it sells to, its proof and competitors, and how its people write. It is plain markdown files on the user's machine, kept next to their campaign folders, so every campaign starts from the same facts: client-research reads it when it writes a campaign's research.md, and every campaign skill after it reads that.

This skill writes the folder and keeps it true. It writes files only: no account, no API keys, nothing sent anywhere.

The folder

Default ./knowledge/ under the current directory, next to ./cold-email/; use another path when the user names one.

./knowledge/
├── company-overview.md        # what the company does, for whom, and why it wins
├── ideal-customer-profile.md  # who buys, their problems, who is not a fit
├── pricing.md                 # plans and prices exactly as stated, with source and date
├── proof/                     # one file per case study or result
│   └── {customer-slug}.md
├── competitors/               # one file per competitor
│   └── {competitor-slug}.md
├── voice.md                   # how the company's people write, each rule with its source
└── instructions.md            # rules every email follows, each with its source

Related skills

• client-research researches a company for one campaign and writes research.md in the campaign workspace (./cold-email/{slug}/). It reads this folder first when it exists.
• qualification writes who is in and who is out for a campaign (qualification.md).
• prompt-writer writes and tests the personalization prompts for a segment (prompts.md).
• create-campaign builds a whole campaign, from plan to ready-to-send copy.

Rules

• Extract, never invent. Every fact in a file comes from a source you can name: the website, a call, a document, or the person's words in this conversation. Never invent a price, a customer, a result or a number. A gap stays a gap: write it as an open question and ask.
• Cite what people want. A rule about how the company writes, or a claim about what a client wants, carries its source: who said it, where and when ("Dana, kickoff call, 2026-10-14"). With no source, ask; never fill the gap from a ticket's or an issue's claim.
• A yes before each write. Show what you will write, file by file, and save after the person agrees. A yes to the pricing file covers that file, not the folder.
• Read, then write. Read a file before you change it. When it changed since you read it (the person or someone else edited it), read it again, merge, show the person, save.
• Edit sections, keep files. Change the one section that changed and leave the rest. A restructure rewrites the same file, never a delete and a new file. When the folder sits in a git repo, its history keeps every version.
• Keep secrets out. Never write a password, an API key or a private link into these files: people share and commit them.
• This skill never sends, launches, or changes a campaign's schedule or volume. A person approves every send and launch.