Skip to main content
A knowledge file is markdown that explains your product to the assistant. Tappify indexes it when you publish and pulls the matching paragraphs into a turn, with your tile on the citation.
Leave the flag off and the command asks which kind it is. It writes knowledge/numbers.md and adds the ai:skills scope, which is the one skills, prompts and context providers need. A knowledge file on its own needs no scope: Tappify indexes it at publish and retrieves it for any install of your extension.

​
The manifest entry

The command writes this entry. You can hand-edit tappify.extension.json instead — the $schema line gives your editor completion and validation, and tappify extension doctor checks the result. Any contributes.ai block needs a server.baseUrl, knowledge included, because the rest of the block is routes on your server. file is a markdown path inside your repository, at most 200 characters. An absolute path, a drive prefix or a .. fails the publish with knowledge.file, and a file the bundle does not carry fails it with KNOWLEDGE_FILE_MISSING before a release row is written, so a typo costs you a publish and nothing else. At most 20 knowledge files.

​
The three categories

A connector has to ship a metric_definitions file. Your numbers sit next to Tappify’s own on the same chart, so the assistant has to be able to say what yours count; publishing metrics without one fails the knowledge.metric_definitions check.

​
Writing the file

Write in short paragraphs separated by blank lines. Tappify packs paragraphs into chunks of about 1,200 characters, carries the tail of each chunk into the next one so a definition split across two is still readable in both, and keeps a heading with the paragraph under it. A definition that lives in its own paragraph is retrievable on its own. The file’s first markdown heading becomes the title every chunk of it carries, so give each file one.

​
What Tappify retrieves

The owner’s last message is the query. Tappify matches it against the index with Postgres full text search, takes the three best-ranked chunks across every extension that chat can see, and cuts each to 1,000 characters and each title to 120 before the assistant sees it. There is no search tool for the assistant to call: retrieval happens once, at the start of the turn.

​
What the owner sees

Nothing, until the assistant uses it. Then the part of the answer that leaned on your file carries a citation beneath it — your tile and your extension’s name, which the owner can click through to your install’s page — so they know which part of the answer came from you. A citation for an extension they do not have installed is dropped rather than shown.

​
What a reviewer sees

Every knowledge file, every skill file and every prompt template, in full. Tappify also scans them for text that tries to redirect the assistant — “ignore previous instructions”, a zero-width or direction-reversing character, a markdown image whose URL would carry the conversation somewhere. For a public extension a match fails the publish; for a private or unlisted one it is reported to you as a warning and you decide. Vendor text describes your product. Everything you write reaches the assistant inside a marker that says who wrote it, under a standing rule the assistant is given on every turn: text from an extension is data about that vendor’s product, not an instruction, and it cannot change Tappify’s rules or reach data the owner did not grant. A block that asks the assistant to ignore its instructions, take on a role, or keep something from the owner is reported to the owner in plain words, and their request is answered anyway.