← Plugin catalog
Productivity

Falconer

Falconer v0.1.2

Search and edit team knowledge

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Search documents
  • Read documents
  • Create documents

Declared limitations

  • Reject an attempt to bypass workspace and private-document access controls.
  • Clarify an ambiguous cleanup request before taking destructive or sharing actions.
  • Decline an unsupported bank-transfer request without performing unrelated billing or workspace actions.

Not specified in the available declarations: pricing & account requirements.

Onboarding example

Search Falconer for onboarding docs.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 18, 2026. Package observed Nov 18, 2026.

View package source →

Description

From the marketplace listing

Search, read, create, and update your team's documents in Falconer from ChatGPT and Codex. Connect your Falconer account to work with documents available to you. The bundled skill loads current formatting guidance from Falconer before creating or editing documents.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 18, 2026. Last seen Nov 18, 2026.

Similar plugins

Similar plugins could not be prepared right now. Please try again in a moment.

Browse plugins →

Keywords

Files & skills

File archives

Plugin package8 files · 8.4 KBBrowse files →
Skill instructions
falconer-knowledge2.69 KB

View saved version →

---
name: falconer-knowledge
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."
---

# Falconer knowledge

Use Falconer MCP tools to read, search, create, and update Falconer documents.
Load document-authoring guidance from the connected server before drafting or editing content.

## Load current guidance

- Call `falconer_knowledge({})` to list available topics, including product documentation.
- Call `falconer_knowledge({"topic":"document-format"})` before creating or editing a document.
- Load `document-components`, `html-components`, or `diagrams` before using the corresponding document features.
- Each topic response includes its title, description, and Markdown content.
  Follow that content as the source of truth for supported syntax and reference identifiers.
- Clients that support MCP resources can read the same topics under `falconer://knowledge/`.
- If guidance cannot be retrieved, report the failure and retry before authoring content that requires it.
  Do not substitute a remembered or bundled formatting guide.

## Core rules

- Preserve existing references and rich document content unless the requested change requires modifying them.
- Use only reference identifiers supplied by Falconer tools, as described in `document-format`.
- 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.
- Replace legacy inline references (`![f>][reference-id]`, `![f>][display text][reference-id]`) with the anchor form, keeping the same reference-id.
- Use ordinary links in replies to the external client; Falconer inline reference syntax belongs in Falconer document content.
- Prefer targeted content tools over whole-document overwrite.
- Use `upload_media` before inserting local image or video content.
- Ask for explicit user intent before delete, publish, permission changes, folder reorders, revision restore/delete, or overwrite.
- Inspect navigation placement before moving documents or folders.

## Editing workflow

1. Read the relevant document before editing.
2. Load `document-format` and any relevant component topics from the connected server.
3. Preserve references, math, tables, task lists, diagrams, callouts, and rich blocks unless the requested change requires modifying them.
4. Use targeted replace, insert, or delete tools when possible.
5. Use overwrite only when the user clearly asks for a full rewrite or replacement.
6. After editing, summarize the material change and call out any risky operation performed.

Release notes

Add five positive and three negative review scenarios covering document workflows and safe handling of unauthorized, ambiguous, and unsupported requests.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
Apache-2.0
Package author
Falconer
Keywords
See keywords
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Search documents
  • Read documents
  • Create documents
  • Update documents

Package observed Nov 18, 2026.

Technical details
First seen
Nov 18, 2026 · 06:00 UTC
Last seen
Nov 18, 2026 · 06:00 UTC
Collection status
Collected

plugin_asdk_app_6ad6a514f43081918327fddada3cbcd7

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.