u/pcx_wave

If you've been collecting Claude Code skills for a while, you know the problem.

You've got 20, 30, maybe 40 SKILL.md files in ~/.claude/skills/. Some cloned from GitHub, some from marketplace installs, some from a gist you found six months ago. There's no pip list. No version tracking. No way to know if a fix was shipped last week.

When a skill breaks or gets improved, you just... don't know.

So here is update-skills, a simple command so you can keep your skills up-to-date.

What it does:

- Resolves source repos - searches DuckDuckGo with verbatim phrases extracted from each local SKILL.md and finds the canonical GitHub repo. It validates by comparing the first 10 lines of the remote file against your local copy, so it rejects forks and similarly-named-but-different repos. One-time cost per skill.

- Checks for updates - compares your installed version against upstream (SHA-level with a GitHub token, SKILL.md content diff without)

- Updates in bulk — python update_skill.py all

- Backs up + reverts — previous version saved automatically before each update, --revert if something breaks

No pip dependencies. No mandatory API keys. Stdlib only.

GitHub: https://github.com/pcx-wave/update-skills

Install:

git clone https://github.com/pcx-wave/update-skills ~/.claude/skills/update-skills

Then simply use /update-skills

If you're anything like me, your ~/.claude/skills/ folder is a graveyard of SKILL.md files you installed once and forgot about. You know there's a skill for that — you just can't remember what it's called or how to invoke it. So you end up answering the question yourself, and the skill rots.

Skill Router is a meta-skill that solves this. Once activated, it scans all your installed skills, builds a lightweight index, and routes requests to the right one automatically.

Two modes:

Suggest (default) — you ask something, it checks the index and surfaces 1-2 matching skills before deciding. Like this:

User: run a GEO audit 

Router: Suggested skills for this request:
        1. geo-audit — full site GEO+SEO audit with parallel subagent delegation
        Use skill 1, or answer directly? (1/no)

User: 1

Router: [loads geo-audit and starts working]

Auto (/skill-router on --auto) — silently routes to the best match and appends *(via skill-name)* at the end of the response. No prompts, no fuss.

It's deliberately conservative — only fires on high-confidence keyword matches. Chatty or trivial inputs go straight to the LLM's own knowledge. One skill per request, no conflicts, no spiral of meta-routing.

Install in one line:

mkdir -p ~/.claude/skills/skill-router && curl -o ~/.claude/skills/skill-router/SKILL.md https://raw.githubusercontent.com/pcx-wave/skill-router/main/SKILL.md

Then hit it with /skill-router on and watch your forgotten skills finally earn their keep.

Repo: github.com/pcx-wave/skill-router

Hi, for multi-model users, this can be useful : an Askclaude skill to ask Claude anything, eg plan, review, reflect, from another cli (Vibe in my case).

If​ you've used Claude I don't need to explain it's capability. For others, I like it's vision and approach to problems. Issue is Claude is quite expensive, so I find using it for pure coding is not optimal. So while I use vibe to implement code, I can get it's input on what I'm doing or even assist with planning or review.

Question in title. Mistral says a 'generous' amount of tokens is included with Le chat pro, but doesn't say how many. Has anyone tried and reached the limit before getting pivoted to API pay per use pricing?

​

Verbatim 1h08.

En gros, ils font du Vibe (cli).

Il insiste "avant vous étiez un artisan, maintenant vous êtes un manager".

Edit: qq part je trouve que la situation rappelle celle des tisserands lors de l'arrivée des métiers à tisser.