Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

kasetto Skill

Repository ↗

by pivoshenko★ 2191 skills

Install

What it does

📼 Declarative AI agent environment manager, written in Rust

  • Connects Instruction files the AI reads
  • Account or key Not confirmed yet (README not read yet)
  • Category Coding
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/pivoshenko-kasetto.svg)](https://mcp.popnx.com/en/skills/pivoshenko-kasetto)

Use together with

MCP servers that connect the AI to services for the same work

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 388.7K/wk★ 466.2KUpdated 7 days ago

MCP · Connects a serviceRuns on your computer

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

by fallow-rsWidely used↓ 2.4M/wk★ 5.4KUpdated 2 days ago

MCP · Connects a serviceRuns on your computer

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 740.3K/wk★ 10.3KUpdated yesterday

MCP · Connects a serviceRuns on your computer

Similar Skills

Same kind of work, ordered like the Skills list

Compared with similar ones
This one
kasetto
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
Makerpivoshenkomorlutomultica-aiGraphify-Labsharry0703
Skills11111
GitHub stars219467,235234,125149,873144,332
Last code changeNov 15, 2026Nov 18, 2026Apr 20, 2026Nov 18, 2026Nov 18, 2026
License–MIT–Apache-2.0MIT

1 skills (instruction sets) by pivoshenko that an AI reads and follows · not an MCP server

How a Skill differs from MCP

MCP = the hands

Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.

Skill = the manual

A text file that teaches the AI how to do a task. It connects to nothing.

Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.

Works with

Claude CodeCodexCursorGemini CLIGitHub CopilotWindsurfOpenCodeKiro

From the maker’s README and the folders in the repo

Install

Is it safe?

  • Who made it

    GitHub account pivoshenko (person), 8 years old

  • Use and upkeep

    ★ 219 stars, few users so far · code last changed Nov 15, 2026

  • Any scripts?

    2 scripts that can run on a computer: scripts/collect.py, scripts/render.py

  • Uses the internet?

    No internet calls found in the scripts

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit 687d711 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself

First: which AI do you use?

Pick your app and this page shows only how to install it there

Option 1Upload to claude.ai (web and app)

  1. Download from GitHub

    This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier

    Download from GitHub (whole repo) ↗

    Unzip it, then zip only the skills/kst-ai-assets-usage folder again. The ZIP must have a kst-ai-assets-usage folder with SKILL.md at the top level, no loose files

  2. Open Skills on claude.ai and upload

    +Create skillUpload a skillpick kst-ai-assets-usage.zip

    Open claude.ai/customize/skills ↗

  3. No Upload button? Turn on file creation first

    SettingsCapabilitiesCode execution and file creation

    Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free

Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)

Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)

Checked against official docs Nov 12, 2026 · Source: support.claude.com, support.claude.com, code.claude.com

Option 1Let Claude Code install it

Copy this sentence and paste it into a Claude Code chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Restart Claude Code, then type /kst-ai-assets-usage or ask for a matching task and Claude picks it up

Checked against official docs Nov 12, 2026 · Source: code.claude.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.claude/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Claude Code, then type /kst-ai-assets-usage or ask for a matching task and Claude picks it up

Skills you install yourself work in the ChatGPT desktop app, Codex CLI and the Codex IDE extension · ChatGPT on the web and mobile cannot use skills you install yourself, only skills that come with a plugin from the directory

ChatGPT desktop app

The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills

Option 1Let ChatGPT install it

Open Codex in the ChatGPT desktop app and paste this sentence into the chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Option 2Put the folder there yourself

Put the kst-ai-assets-usage folder at ~/.agents/skills/kst-ai-assets-usage

~ is your home folder ($HOME)

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

After installing

  • ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
  • To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
  • Codex picks up newly installed skills by itself; if one does not show up, restart Codex

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

ChatGPT on the web and mobile

Skills you install yourself do not work here; only skills that come with a plugin from the directory

To use this skill with ChatGPT, use the ChatGPT desktop app as above

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

Option 1Let Codex install it

Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Codex, then ask for a matching task; Codex lists the skill

Option 1Let Cursor install it

Copy this sentence and paste it into a Cursor chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

In Cursor’s Agent chat, type / and pick kst-ai-assets-usage

Checked against official docs Nov 12, 2026 · Source: cursor.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.cursor/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. In Cursor’s Agent chat, type / and pick kst-ai-assets-usage

Option 1Let the AI install it

For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.

View on GitHub ↗

Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026

View the original SKILL.md

The text below comes from the maker’s repo, not from PopNx MCP

Showing the first 8,000 characters · Open the full file on GitHub

---
name: kst-ai-assets-usage
description: Report which kasetto-installed skills and MCP servers are actually being used across the AI agents on this machine, and render a branded HTML dashboard of the result. Use whenever the user asks what agent assets they actually use, which skills or MCPs are dead weight, what to prune or clean up from kasetto.yaml, why their context is bloated with unused MCP servers, whether a skill has ever been invoked, or wants a usage report, audit, or dashboard of their agent setup. Also trigger on "kst ai assets usage", "ai asset usage", "what skills do I actually use", "which MCPs are worth keeping", "audit my agent assets", "am I using all these skills", or any request to review, trim, or justify an installed agent toolkit.
---

# kst-ai-assets-usage

Kasetto knows what you installed. Each agent knows what it ran. Nothing on the
machine joins the two, so installed-and-forgotten assets accumulate silently -
skills nobody has ever invoked, MCP servers loading tool definitions into every
request for a server the user stopped using months ago.

This skill closes that loop: read the lock, read each agent's local session
store, join them, and say plainly what is alive and what is dead.

## Run It

Two scripts, both standard-library Python 3, both offline.

```bash
python3 scripts/collect.py --out usage.json        # scan + join
python3 scripts/render.py usage.json --out usage.html
```

`collect.py` is the slow one on a cold cache (a few seconds for a large history)
and near-instant afterwards - it caches per-file results in
`$XDG_CACHE_HOME/kasetto/usage-scan.json` keyed on size and mtime, so a rerun
only touches files the agent appended to. Delete that file to force a full
rescan.

Open the dashboard when it is written, then give the user the short version in
the terminal: how many assets are idle, the biggest surprises, and what you would
cut. The HTML is the artifact; your reading of it is the value.

## The Rule That Matters: Never Overstate Coverage

`collect.py` reports a `coverage` block listing every agent it knows about and
whether it found a readable session store. Honour it.

An asset the user drives daily from an agent that has no provider **looks
completely dead in this report**. If you present "55 skills never used" without
saying which agents that claim covers, and they act on it, they delete something
they rely on. That is the one way this skill can actively hurt someone.

So:

- State the coverage before any count that depends on it. The dashboard carries
  this as a Review insight naming the unread agents rather than a banner, so it
  is easy to scroll past - say it out loud in your summary
- Phrase the finding as "never invoked in *the agents kasetto can read*", not
  "never invoked"
- When a `status: absent` agent is one the user actually uses, say so directly
  and treat the idle list as a shortlist to review rather than a cut list
- A `verified_format: false` provider parsed a store whose layout has not been
  confirmed against a real sample. A zero from it is weak evidence, not proof

## Reading the Output

Start with `insights` - `collect.py` computes the findings worth acting on
rather than leaving them to be read off a chart. Each carries a `severity`, a
`title` already phrased as a claim, a `detail` explaining why it matters, and
the `items` it refers to. Lead your summary with these, in order; they are
already sorted by severity. Then use the rest of the JSON to answer follow-ups.

Severity is a deliberately narrow vocabulary, and it drives colour in the
dashboard:

- `bad` (red) - Concrete waste, meaning a source repository with nothing in use. This
  is the only thing red is spent on, because an unused skill is dormant, not
  broken, and colouring it red would burn the strongest signal on the least
  urgent finding
- `warn` (amber) - Act on it: idle MCP packs, coverage gaps, unverified formats
- `info` (cyan) - Context: concentration, freshly installed assets, unmanaged
  finds
- `good` (green) - Nothing idle

Idle skills are grey throughout. Keep that distinction when you talk about them:
"dormant" and "worth a look", not "bad".

`usage.json` carries more than the dashboard shows. Worth reading directly when
the user asks something specific:

- `skills` / `mcps` - Per asset: `total`, `last_used`, `by_agent`, `days` (a
  date-keyed histogram), plus `source` and `scope` from the lock. Skills carry
  `age` and a `fresh` flag; MCP packs carry `by_server` and `by_tool`
- `by_source` - Per source repository, how many of its assets are live, fresh and idle.
  **Usually the most useful view.** Assets go idle in clusters, because a repository
  gets added for one skill and brings twelve. A wholly idle source is a single
  `source:` block to delete rather than N rows to prune, so lead with this when
  recommending cuts
- `activity` - Daily invocation totals for skills and MCPs, which is what
  separates "used heavily last year" from "used steadily this week"
- `unmanaged` - Names called locally that are not in the lock: installed by hand
  or shipped by the agent. A heavily used one is worth bringing under
  `kasetto.yaml` so it syncs everywhere
- `counts` - Headline numbers, with `skills_idle` and `skills_fresh` already
  separated

An MCP pack can merge several servers, so usage is counted per server and rolled
up. A pack alive on one server and idle on another is worth calling out; that
detail is invisible in the pack-level total.

## Recommending Removals

The idle list is a starting point, not a verdict. Before suggesting a cut:

- Skills cost almost nothing when idle - only their description is loaded until
  invoked. An unused skill is clutter, not a real tax
- **MCP servers are different.** Their tool definitions load into context on
  every single request whether or not you call them. An idle MCP pack is a
  standing cost, so it is the far stronger cut candidate and worth leading with
- An asset installed last week that has not been used yet is not dead, it is new.
  `collect.py` already separates these into `skills_fresh` using a 7-day
  threshold, and the dashboard holds them in their own section. Never move one
  into a cut list because its count is zero
- Some assets exist for rare high-stakes moments (an incident runbook, a release
  procedure). Low count is the design, not a defect

To act on a decision, the existing CLI does it - `kst remove` edits
`kasetto.yaml` in place and preserves comments and key order, then `kst sync`
uninstalls the asset. Do not hand-edit the lock.

## Adding an Agent

The provider list is a table at the top of `scripts/collect.py`. Adding one is a
new entry plus, sometimes, a reader. `references/providers.md` documents each
known agent's store, which are verified against real data, and which are
inferred from documentation.

Two things to hold onto when you extend it:

**Match patterns, not schemas.** Session formats churn - Goose moved JSONL to
SQLite, OpenCode JSON to SQLite, Copilot CLI flat files to per-session
directories. What did *not* move through any of those migrations is the tool-name
string. Matching `mcp__<server>__<tool>` survives a schema rewrite that would
break a field-by-field parser. Resist the urge to "properly" parse these files.

**Anchor on an invocation position.** Session logs also record the tools
*offered* each turn, as arrays of names repeated on every request. An early
version matched the bare `mcp__x__y` string anywhere and reported 38,743 calls
for a server with zero real invocations. Every pattern must require a key
position (`"name": "mcp__..."`), and any new provider needs a sanity check
against an independent count before its numbers are trusted.

## Scope

Skills and MCP servers only. The other four asset kinds are deliberately out:

- Commands - In the logs they are mostly agent built-ins rather than kasetto
  assets, so a count would mostly measure the agent
- Instructions - Injected as context and never "invoked", so usage

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

From GitHub

GitHub stars
219
Maker
pivoshenko
License
No license stated This repo states no license. By default the author keeps all rights: ask before you share it or use it commercially.
Last code change
Nov 15, 2026
SKILL.md files in the repo (including translated copies and templates)
1
Topics
ai, ai-agent, ai-commands, ai-skills-manager, antigravity, claude, claude-code, claude-skills, codex, copilot, cursor, developer-tool