Birdview Compatibility logo

Birdview Compatibility

Community
Qiuner
birdview-compatibility

Audit the installed AI skill environment for duplicate installations, broad triggers and possible instruction conflicts. Use only when the user invokes birdview-compatibility; it does not activate architecture mapping or modify skills.

Overview

PublisherQiuner
Repositorybirdview
Skill namebirdview-compatibility
Stars
701
Forks
69
Bundled files
4
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Qiuner on GitHub. Read the source before you install it.

Installation

Install the Birdview Compatibility AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Qiuner/birdview/tree/main/compatibility-audit
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Qiuner/birdview.git /tmp/birdview
mkdir -p .claude/skills
cp -r /tmp/birdview/compatibility-audit .claude/skills/birdview-compatibility
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Birdview Compatibility in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Birdview Compatibility on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Birdview Compatibility is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Birdview skills audit

中文

Run the read-only inventory from the installed Birdview bundle:

sh
node <skill-root>/scripts/birdview.mjs skills audit --project <project-root> --language en --write <project-root>/.birdview/compatibility-audit.json

Set --language to the language of the current user conversation (zh for Chinese, en for English); the CLI cannot infer conversation language by itself. Always pass it when producing the human-readable Markdown report.

The JSON is deliberately two-layered. skills, duplicateNames and issues are inventory facts; assessment is the required human conclusion. Inventory is not the finished audit. In the same turn, read every discovered SKILL.md and compare at least names, trigger descriptions, explicit invocation requirements, automatic invocation policy, disable-model-invocation, write permissions and approval gates. Then write the assessment using the report contract and render both artifacts:

sh
node <skill-root>/scripts/birdview.mjs skills audit --project <project-root> --language en --assessment <project-root>/.birdview/compatibility-assessment.json --write <project-root>/.birdview/compatibility-audit.json --write-markdown <project-root>/.birdview/compatibility-audit.md

The Markdown report is for people: every pair with overlapping trigger scope must state the triggering language, whether the skills are compatible, need ordering, may conflict or remain unresolved, with confidence, rationale, quoted evidence and a recommended execution order. Keep a relationship unresolved only when the bodies or host rules cannot be read; do not leave an empty unreviewed report merely because the inventory succeeded.

Report the discovered roots, skills, duplicate names and metadata flags, then complete trigger compatibility analysis. Read both bodies for skills with similar trigger descriptions, automatic activation, shared task domains, or an instruction that applies to every conversation. Classify each such relationship as compatible, ordered, potential conflict or unresolved. Compare activation policy, write permissions, approval gates, output ownership and explicit scope. Show both source passages for any claimed conflict; duplicate names alone are not a semantic conflict.

This instruction is an audit request, not approval to change configuration. Do not disable, rewrite, delete or reinstall another skill. Do not start Birdview architecture or constraint mapping unless the user separately asks for it. The inventory is only candidate discovery, not semantic compatibility; preserve the facts, conclusions and specific gaps.

Deliver the Markdown report for human review. Keep it textual and concise: show the conclusion, scenario, impact, evidence and next action. Do not create a graph or label unknown relationships as compatible.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Birdview Compatibility AI skill do?

Audit the installed AI skill environment for duplicate installations, broad triggers and possible instruction conflicts. Use only when the user invokes birdview-compatibility; it does not activate architecture mapping or modify skills.

Why use Birdview Compatibility on TypingMind?

Because you install it once and use it with any model. Birdview Compatibility is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Birdview Compatibility in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Qiuner/birdview/tree/main/compatibility-audit. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Birdview Compatibility?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Birdview Compatibility?

As many as you like. As long as a model supports skills, you can use Birdview Compatibility with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Birdview Compatibility AI skill free?

Yes. It is published on GitHub by Qiuner under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇