Skill Inventory

CommunityPopular

hoangsonww

skill-inventory

Inventory the installed skills and which plugins contribute them, then flag overlap with the user's own skills — read through the Agent Monitor Config Explorer API. Reads /api/cc-config/skills and /api/cc-config/plugins. Use when managing skills: deduping, deciding what to keep, or tracing a skill back to the plugin that ships it.

Overview

Publisher	hoangsonww
Repository	`Claude-Code-Agent-Monitor`
Skill name	`skill-inventory`
Stars	1.1K
Forks	260
Bundled files	1
License	MIT
Links	Skill source Repository Homepage

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 hoangsonww on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-config/skills/skill-inventory
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-config/skills/skill-inventory

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

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/hoangsonww/Claude-Code-Agent-Monitor.git /tmp/Claude-Code-Agent-Monitor
mkdir -p .claude/skills
cp -r /tmp/Claude-Code-Agent-Monitor/plugins/ccam-config/skills/skill-inventory .claude/skills/skill-inventory

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Skill Inventory 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 Skill Inventory 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 Skill Inventory 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.

Skill Inventory

Map every skill available to the user — both their own (user/project scope) and the ones contributed by installed plugins — read through the Agent Monitor dashboard at http://localhost:4820.

Input

The user provides: $ARGUMENTS

This may be:

empty — inventory all skills (default).
a skill name fragment — focus on skills whose name matches.
a plugin name — show only the skills that plugin contributes.

Data Sources

Endpoint	Returns
`GET /api/cc-config/skills`	`{ items:[{ scope:"user"\|"project", name, path, file, size, mtime, frontmatter, preview }] }` — the user's own skill directories
`GET /api/cc-config/plugins`	`{ manifestPath, manifestExists, plugins:[{ key, name, marketplace, scope, version, enabled, installPath, contributes:{ skills, agents, commands, outputStyles, hooks } }] }`

Report Sections

1. User & project skills

From /skills, list each skill with scope, name, size (KB), and frontmatter.description (or the start of preview). Separate user-scope from project-scope skills.

2. Plugin-contributed skills

From /plugins, list each plugin with enabled state and its contributes.skills count. Note that /skills reports only the user's own skill dirs — plugin skills are counted via contributes, so reconcile: total available skills ≈ user skills + Σ enabled-plugin contributes.skills.

3. Overlap & duplication

Flag where a plugin name or a plugin's contributed-skill domain overlaps with a user-authored skill of the same name or purpose (compare against frontmatter.description from /skills). Recommend keeping one source of truth — prefer the plugin version if it is maintained upstream, or the user version if it is customized.

4. Disabled / orphaned plugins

Flag plugins with enabled: false (their skills are inert) and any whose installPathExists is false (manifest references a missing install) — these are dead weight to clean up via the Claude Code plugin manager.

Output

Section 1 as a table (Scope | Name | Size | Description).
Section 2 as a table (Plugin | Enabled | Skills | Agents | Commands).
A reconciliation line: user skills + plugin skills = total available.
Cite only fields the API returned — never fabricate skills or counts.
Note: plugins are read-only via the Config Explorer; manage them with the Claude Code plugin commands, not this dashboard.
If the dashboard is unreachable at http://localhost:4820, say so and tell the user to start it with npm start from the repo root.

Bundled files

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

agents/openai.yaml1 KB

Frequently asked questions

What does the Skill Inventory AI skill do?

Why use Skill Inventory on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-config/skills/skill-inventory. 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 Skill Inventory?

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 Skill Inventory?

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

Is the Skill Inventory AI skill free?

Yes. It is published on GitHub by hoangsonww 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

Android Clean Architecture

affaan-m

CommunityPopular

Android と Kotlin Multiplatform プロジェクトのクリーンアーキテクチャパターン — モジュール構造、依存関係ルール、UseCase、Repository、データ層パターン。

Blackbox

Delegate coding tasks to the Blackbox AI multi-model CLI.

Comps Analysis

Build comparable-company valuation workbooks in Excel.

Weights And Biases

W&B: log ML experiments, sweeps, model registry, dashboards.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Skill Inventory

Input

Data Sources

Report Sections

1. User & project skills

2. Plugin-contributed skills

3. Overlap & duplication

4. Disabled / orphaned plugins

Output

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now