Skills Governance logo

Skills Governance

Community
cnfjlhj
skills-governance

Use when auditing a large local skill collection, identifying duplicate or imported skills, comparing skill roots, or deciding what to keep, disable, or archive across Codex and adjacent agent skill directories.

Overview

Publishercnfjlhj
Repositoryai-collab-playbook
Skill nameskills-governance
Stars
455
Forks
44
Bundled files
1
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.

  • 1 bundled files

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

  • Open source

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

Installation

Install the Skills Governance 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/cnfjlhj/ai-collab-playbook/tree/main/skills/full/skills-governance
  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/cnfjlhj/ai-collab-playbook.git /tmp/ai-collab-playbook
mkdir -p .claude/skills
cp -r /tmp/ai-collab-playbook/skills/full/skills-governance .claude/skills/skills-governance
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Skills Governance 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 Skills Governance 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 Skills Governance 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.

Skills Governance

Purpose

Use the bundled scanner as the source of truth for local skill inventory. Base recommendations on real directories and SKILL.md frontmatter instead of stale catalogs or memory.

When to Use

  • The user says they have too many skills and cannot tell what is useful.
  • The user wants a Codex-first keep or disable plan.
  • The user needs duplicate-name groups across multiple skill roots.
  • The user suspects imported plugin packs or mirrored skills are causing confusion.
  • The user wants a filesystem-backed inventory before changing skill settings.

How to Run It

Invoke the bundled scan.js from this skill directory.

  • Codex-first inventory: node scan.js --mode codex --format markdown
  • Cross-agent inventory: node scan.js --mode all --format markdown
  • Duplicate review only: node scan.js --mode all --duplicates-only --format markdown
  • Machine-readable output: node scan.js --mode all --format json

Workflow

  1. Run the scanner in codex mode first.
  2. If the results still do not explain the user's confusion, rerun in all mode.
  3. Explain the problem from roots, duplicate groups, and suspicious flags before recommending changes.
  4. Prefer Codex [[skills.config]] disable suggestions over editing individual SKILL.md files unless the user explicitly asks for direct file edits.
  5. Separate recommendations into three buckets: keep, disable for now, and archive or external mirror.
  6. If the user asks to execute changes, list exact target paths and wait for confirmation first.

Output Contract

Report at least:

  • scanned roots
  • total skills
  • enabled and disabled counts
  • duplicate-name groups
  • suspicious flags such as plugin-import, system, or backup-like
  • a compact per-skill list when needed

Acceptance

A good run:

  • completes without external dependencies
  • reflects the actual filesystem state
  • shows duplicate groups by skill name
  • remains stable across repeated runs unless files changed

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 Skills Governance AI skill do?

Use when auditing a large local skill collection, identifying duplicate or imported skills, comparing skill roots, or deciding what to keep, disable, or archive across Codex and adjacent agent skill directories.

Why use Skills Governance on TypingMind?

Because you install it once and use it with any model. Skills Governance 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 Skills Governance in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cnfjlhj/ai-collab-playbook/tree/main/skills/full/skills-governance. 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 Skills Governance?

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 Skills Governance?

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

Is the Skills Governance AI skill free?

It is published on GitHub by cnfjlhj. Check the repository for licensing terms. 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 👇