← FalconerCONTENT HISTORY
WHAT CHANGED
Update to Falconer
Snapshot Nov 18, 2026 · 06:17 UTC · version 0.1.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Falconer and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when working with Falconer documents through MCP: reading, searching, drafting, editing, preserving Falconer Markdown syntax, using rich document blocks, uploading media, or changing document navigation, comments, permissions, or revisions.",
"included_files": [],
"name": "falconer-knowledge",
"skill_md_contents": "---\nname: falconer-knowledge\ndescription: \"Use when working with Falconer documents through MCP: reading, searching, drafting, editing, preserving Falconer Markdown syntax, using rich document blocks, uploading media, or changing document navigation, comments, permissions, or revisions.\"\n---\n\n# Falconer knowledge\n\nUse Falconer MCP tools to read, search, create, and update Falconer documents.\nLoad document-authoring guidance from the connected server before drafting or editing content.\n\n## Load current guidance\n\n- Call `falconer_knowledge({})` to list available topics, including product documentation.\n- Call `falconer_knowledge({\"topic\":\"document-format\"})` before creating or editing a document.\n- Load `document-components`, `html-components`, or `diagrams` before using the corresponding document features.\n- Each topic response includes its title, description, and Markdown content.\n Follow that content as the source of truth for supported syntax and reference identifiers.\n- Clients that support MCP resources can read the same topics under `falconer://knowledge/`.\n- If guidance cannot be retrieved, report the failure and retry before authoring content that requires it.\n Do not substitute a remembered or bundled formatting guide.\n\n## Core rules\n\n- Preserve existing references and rich document content unless the requested change requires modifying them.\n- Use only reference identifiers supplied by Falconer tools, as described in `document-format`.\n- Write new inline references as `<a href=\"link\" data-id=\"reference-id\">display name</a>`; a plain anchor without `data-id` is an ordinary link.\n- Replace legacy inline references (`![f>][reference-id]`, `![f>][display text][reference-id]`) with the anchor form, keeping the same reference-id.\n- Use ordinary links in replies to the external client; Falconer inline reference syntax belongs in Falconer document content.\n- Prefer targeted content tools over whole-document overwrite.\n- Use `upload_media` before inserting local image or video content.\n- Ask for explicit user intent before delete, publish, permission changes, folder reorders, revision restore/delete, or overwrite.\n- Inspect navigation placement before moving documents or folders.\n\n## Editing workflow\n\n1. Read the relevant document before editing.\n2. Load `document-format` and any relevant component topics from the connected server.\n3. Preserve references, math, tables, task lists, diagrams, callouts, and rich blocks unless the requested change requires modifying them.\n4. Use targeted replace, insert, or delete tools when possible.\n5. Use overwrite only when the user clearly asks for a full rewrite or replacement.\n6. After editing, summarize the material change and call out any risky operation performed.\n"
}SHA-256 of public snapshot: f9963b1cff49f30122e100e8b72b844b6540439f01709e0c8e305c753b836373