r/claudeskills • • 8h ago

Skill Share 9 free lesser know Claude skills for visual work

Post image
479 Upvotes

r/claudeskills • • 4h ago

Skill Share sfx-skill, a skill that lets your agent make sound effects, and some of my thoughts on vibe coding (sound on)

40 Upvotes

This is a skill I made with Claude. The idea came from music-skill, which I posted about last time. I thought maybe an agent could work on sound effects too, so I tried making this. It lets an agent layer real recordings and synthesis into editable sound effects, gives you multiple versions and a page to listen to them, and then exports them to game engines. For now the sound library only uses FSD50K by default, and for some sounds, like footsteps, it starts from a real sample as the base and processes it from there. I'm starting with only FSD50K because it's a public dataset built for audio research, and I only picked out the recordings their authors marked as CC0. They're only downloaded when needed, and it asks you first. You can also import your own material under whatever license it has. Basically, once you hand it to the AI, it'll check with you.

That's about it for the skill. Now I'd like to share some thoughts. Honestly, I really enjoy vibe coding, and most of what's on my GitHub was made by me using AI. My first time vibe coding was back in 2024. Later, around last year when MCP got popular, I also made a Discord MCP, a tool that lets an agent directly drive a Discord bot, though I didn't open source it. I'm 18 this year, and majoring in finance has been my plan from the start, so honestly I'm still pretty much a beginner at coding. On my own, I can write Discord bots that pull stock info and display it, and make simple little games, but that's about it. I do think I'm fairly careful though, since risk management is all about being careful. I really love making things with Claude, and ever since I first tried it I've had high hopes for where this is going, that feeling of "it's only been around for a short while, who knows how far it'll have come by the time I'm old." I don't think what I make with agents can be better than what professionals make, of course it can't. But I like using agents to make simpler things that are really fun. My music-skill actually came from wanting to make a skill that lets an agent create visual novels. After generating music a bunch of times during testing, I started thinking, why not just let the agent make the music itself? Claude is the main producer, it calls Codex CLI for images, Gemini TTS does the voices, and then music was the only thing missing. If it can make that too, the whole pipeline can fit inside a skill.

Lately I've been working on music-skill a lot, so the visual novel skill hasn't gotten much attention. I figure that if people are interested in music-skill, even if not many are following it right now, I should take responsibility and keep improving it. Of course, lately I've seen people telling others it's not "I made" but "I generated." Okay, in terms of the actual action, it's true nobody is typing it out line by line, and technically that's right too. But what I want to say is, if AI really let people produce things without spending time, money, energy, creativity, planning, integration, or pushing for testing and verification, the world wouldn't look the way it does now. You can say what I made with AI is garbage, but you can't say I didn't put thought and time into it.

To be clear, I'm not claiming AI is better than human work, and I really do support human creators, by buying books and tickets, paying for subscriptions and so on. When I study, the music I listen to is made by human creators too. What I mean is that I like AI because it lets me quickly bring the ideas in my head to life, fun ideas, whether or not they're actually good ones. Making things I find fun is a form of entertainment for me. I can try a lot of things, then plan more deeply around the ones that look promising, and I get to learn related knowledge and methods along the way. That's worthwhile, rather than just mindlessly pressing a button over and over. Of course, everyone does it differently.

Here's how I currently work with AI. I set the direction first, then have Claude draft something based on my plan. I check it and give suggestions, then have it plan this round's scope in more depth and look through relevant literature. Then I read it again, and at the same time give it to GPT Astra to check for blind spots or other suggestions. Then comes the build. When it's done, it goes through the safety net. For music-skill, that means running two self-checks, one with the sound libraries and one without, then tests with each fix removed, then testing that the sound-generating modules match the previous version bit for bit. Next, the projects get re-rendered with the new version and compared against the previous one, then come export tests and a privacy scan before it goes up to GitHub, where CI runs on Ubuntu, macOS and Windows (I don't have a Mac, so this is the only way). After that, I have the agent use GPT Astra through Codex CLI to review it, capped at 3 rounds for small versions and 6 for big ones. I usually let this run while I sleep since it takes a while, and when I wake up I have two review requests ready, which I give to two GPT 6 Pro sessions on the web for another pass. I do it this way because the same AI model tends to have the same thinking habits, so this helps avoid that, and I have to say GPT models really are better on the defensive side, noticeably so. Even so, it still has to go through a real local install test, because actually using it is how you find the landmines and mistakes. I think skills are a great fit for being built by agents, since some of them span a lot of ground and involve a lot of data, and the user is an agent anyway. Once it's done, I publish it and also back it up on a hard drive.

I basically just make things I'm interested in and would use myself. For example, a few days ago I made a mod that puts a background on Claude Code. JPEGs couldn't be displayed directly at the time, so I had to lower the resolution and color count and draw the background as an SVG with over 200,000 elements in two layers of characters (not sure if JPEGs can be displayed now, hope so). Okay, I'm obviously not a professional. I plan to take some CS courses in college and I'm teaching myself too, but right now I really can't build a truly professional system or piece of software. Still, I hope to keep making things I'm interested in and find fun.

If you're interested in sfx-skill, check it out at https://github.com/owoevan-dev/sfx-skill

P.S. I expected this post to be on the longer side. English isn't my first language, and for something this long I'm still more comfortable writing in my native language, so this post is AI translated, but the tone should be the same as my original. It did end up even longer than I planned though. If you actually read all of it, thank you for spending your valuable time hearing me out.


r/claudeskills • • 6h ago

Skill Share Model Lab: Get Better (Agent Skills)

Thumbnail
rakshazi.me
13 Upvotes

A "skill to write skills" that includes:

  • lessons learned from work with different model sizes (from 1.7B up to %whatever-count-of-params-modern-proprietary-models-have%)
  • scaffolding to spin up test stands with 3 different harnesses (Pi, OMP, Claude Code)
  • templates, examples, evals, etc.
  • and lots of other nice-to-have stuff, like a duplicates detector

r/claudeskills • • 5h ago

Skill Share Skill share: job hunting in Germany. Finds jobs under German and English titles, quotes the line when an ad really needs German, checks the Blue Card salary (free, MIT)

7 Upvotes

a lot of my friends in Germany aren't in tech, and watching them job hunt was rough: jobs listed only under German titles, English ads that say "fließend Deutsch" at the very bottom, no salary, and Blue Card thresholds nobody checks. i kept doing the same research for them by hand, so i turned it into a skill.

what it does:

  • searches Arbeitsagentur, Daily Berlin Jobs and company ATS boards (Greenhouse, Lever, Personio, Ashby) with German and English titles
  • reads each ad, quotes the line about German and checks a stated salary against the 2026 Blue Card thresholds
  • suggests where else to look for your field (public sector, academia, healthcare, Ausbildung...)
  • mock interviews in German or English, and an application tracker
  • optional CV and cover letter: a writer pass, then a separate reviewer pass that blocks any claim it can't trace back to your CV
  • never applies or sends anything

how it's built: SKILL.md is a short router, the reference files only load when the task needs them, and stdlib Python does the exact parts (API calls, the German scan, salary math, PDF). the first version was bad at the obvious stuff: "Munich" returned zero jobs where "München" worked, and a non-tech search returned mostly engineering jobs. per-field sources and phrase matching took on-target results from 29% to 87%.

Claude Code:

/plugin marketplace add umutyesildal/berlin-job-search

other agents: npx skills add umutyesildal/berlin-job-search

free, MIT: https://github.com/umutyesildal/berlin-job-search

how do you test a skill like this? i only had a few real profiles to try it on, and i'd like a better way.


r/claudeskills • • 7h ago

Skill Share A tool that turns your repeated Claude Code corrections into rules and suggested skills

8 Upvotes

Tired of telling Claude the same things every session? behavior-map reads your past Claude Code prompts and builds:

  • one rule file per habit, quoting your own words
  • suggested skills for jobs you keep asking for
  • CLAUDE.md, AGENTS.md and prompts for other tools

A local page lets you edit the rules and see which ones get broken. It runs entirely on your machine and needs no API key if Claude Code is signed in.

Repo: https://github.com/mos-ks/behavior-map

Hope it helps! Happy to get feedback, and PRs are welcome if you'd like to contribute.


r/claudeskills • • 1h ago

Skill Share I built explain-change to walk me through a PR before review

Thumbnail
gallery
2 Upvotes

I built explain-change for the point where an agent hands me a PR and I need to understand what it actually changed.

I give it the PR URL. It reads the diff, callers and relevant tests at that commit. I want to know what the new design relies on, what happens when a step fails, and which files I should open first. The skill gives me Markdown with Mermaid and links to the specific source lines. So you can still drill-in into the code changes and explore them, while starting from the story told by diagrams.

I added an example from structured-output PR. This image shows one of those Mermaid diagrams created for dynamic HTML output. You also have an option to ask for text md file, which will produce a static version.

Install with:

npx skills add aictrl-dev/skills --skill explain-change -a claude-code,

then run:

/explain-change <PR URL>.

https://github.com/aictrl-dev/skills/tree/main/skills/explain-change


r/claudeskills • • 1d ago Bravo

Skill Share Claude Code + Playwright found 15/18 bugs. The false alarms were the real problem.

Post image
160 Upvotes

Claude Code + Playwright is actually pretty good at finding bugs. In my benchmark, it caught 15/18 seeded bugs.

The catch? It also averaged 3.15 false alarms per run.

Which made me wonder: how much time am I really saving if I still have to manually verify every finding?

So I built Stillhunter, a free, open-source Claude Code plugin that:

  • Tests your changes in a real browser, exploring edge cases and injecting failures.
  • Reproduces suspected bugs more than once from scratch, keeping intermittent failures separate.
  • Turns confirmed bugs into reusable regression tests.

I ran a benchmark against Claude Code + Playwright (27 runs each):

MetricPlaywrightStillhunter
Bugs detected15/1817/18
False alarms/run3.150.41
Precision64%90%

The detection difference isn't statistically conclusive, but reducing false alarms from 3.15 to 0.41 per run is the result I'm most excited about.

GitHub (MIT): https://github.com/stillhunter/stillhunter

To try it in Claude Code:

/plugin marketplace add stillhunter/stillhunter
/plugin install stillhunter@stillhunter

Curious how others deal with this. Do you manually verify bugs reported by AI agents, or have you found a reliable way to automate that too?


r/claudeskills • • 7h ago

Skill Share Chat naming / chat kickoff skill

4 Upvotes

Claude does a lot of things well. Claude does not do chat naming well. This skill does.

The chat routine skill sets up every chat and sub-chat with titles that reflect current working status and 3-5 words describing the outcome. It’s hands down my fave utility skill.

Hope you enjoy this as much as I do!

https://github.com/daftstar/chat-routine


r/claudeskills • • 12h ago

Skill Share When CC stops, is it done or waiting on background tasks? I built a tracker to tell you the overall progress.

Thumbnail
gallery
10 Upvotes

Codex Pacer is a free, open-source app for macOS and Windows. It already has 184 stars on GitHub, and that number is growing fast.

Pacer is built specifically for Claude Code, optimized for its unique task state machine, and tells you:

  • A progress ring per task, from agent's own estimate of how much of the request is done.
  • Every running task at once, with its step, model, speed and turn time.
  • A task that needs your approval turns amber and moves to the top.
  • The 5-hour and weekly quota on one ring with a pace mark, plus your banked resets and a reminder before one expires.
  • Tasks on SSH hosts, not only on your mac/PC.
  • Other coding agents, like Codex, DeepSeek Harness and WorkBuddy tasks in the same list, if you run those too.

Everything is fully customizable, so you can hide anything you don't need.

Compared to similar tools, Pacer has been carefully tuned and optimized for performance. It uses just a few dozen MB of memory, consumes remarkably little power, and is especially gentle on your SSD. In fact, Pacer has one of the smallest disk footprints in its category, with daily disk reads and writes totaling just a few to a few dozen MB.

I'll keep building more genuinely useful features for Pacer, with the goal of making it a great companion for your coding workflow. Pacer is completely free to use, and I'd love to hear your ideas and feedback. Contributions are always welcome, too! We already have 7 contributors, and I'd love to see our community grow even further.

Download on Github (MacOS & Windows)


r/claudeskills • • 1h ago

Skill Share Most useful skill?

Thumbnail
reddit.com
1 Upvotes

My most useful Claude code skill is /session-relay. I use it when I start a session that is going to go for days or weeks.

What it does:

- When context is at 50% or if the session is older than 6 days, writes a handoff document, starts a new session and passes all the work to the new session to continue

- Prints a status check every 2 hours

- Waits up to 15m for my decisions and then takes the recommended decision to continue the work. The decision is in the next status card under “What’s New” with an option to reverse it.

Too long to include in a Reddit post, but here is the whole skill: https://docs.google.com/document/d/1DK1EU4bxWVKtGlLWFpNz9hlyFziTVcz4fcLPi-rAS0k/edit?usp=drivesdk


r/claudeskills • • 1h ago

Skill Share AI assistants Claude vs Gemini

Thumbnail reddit.com
1 Upvotes

r/claudeskills • • 10h ago

Skill Share Made a page where scrolling down is a snowflake falling, from inside the cloud to a kid's mitten

4 Upvotes

The whole page is one camera move. Scroll down and you fall with a single snowflake: it grows its six arms inside a winter cloud, drops out over a valley at night, drifts past a church clock and a street lamp, floats by a frosted window where a family is decorating a tree, and lands on a red mitten. No cuts anywhere, and the transitions are real video.

I built it in Claude Code with sn-motion-html from SenseNova-Skills. What I liked is that it doesn't just start generating. It wrote a style sheet and a shot plan for every chapter, rendered three test stills, and waited until I signed off on both. Then it made the rest of the stills and nine 5-second clips, and each transition is generated from the actual last frame of one clip and the first frame of the next, which is why nothing jumps.

The stills came from SenseNova-U1.5-8B-MoT running on my laptop. The video was Seedance 2.5 through OpenRouter: 9 clips, $25.80, every one usable on the first try. It also handled a phone layout and a reduced-motion fallback.

The recording speeds up the scroll parts. The transitions play at real speed.

https://github.com/OpenSenseNova/SenseNova-Skills

Next I want to try one of these as a product story.


r/claudeskills • • 2h ago

Skill Share rust-anything turned Ruby's Shellwords into Rust: 5x faster, all identical

Post image
1 Upvotes

rust-anything takes one unit of an existing codebase (Ruby, Python, TS, Go, Java, C, PHP, C#), records what the original actually does, builds a Rust port behind a bridge, and diffs every recorded case before you switch anything over.

Repo: https://github.com/erkamyaman/rust-anything

The GIF is Ruby's standard-library shellwords.rb:

- diff: all 1617 recorded calls give identical results and errors.

- bench (per call, crossing the Ruby/Rust boundary included): shellsplit 3.17x, shelljoin 5.82x, shellescape 6.83x. 5.01x overall.

- Batch: 50,000 mixed values (strings, ints, floats, nil, symbols) go through shellescape 12.0x faster. That's Rust on 4 cores against Ruby on one thread, so it's the "hand the whole loop to Rust" number, not a like-for-like one.

It doesn't always win, and it says so. On C# Protobuf's tiny size functions it measured 0.03x, because each call into Rust costs more than the work itself, and bench said "do not ship this unit". Knowing which units to leave alone matters as much as the speedups.

Repo: https://github.com/erkamyaman/rust-anything

What would you want it to port next?


r/claudeskills • • 2h ago

Question I'm migrating a project from dev to prod. The prod server will contain sensitive information that I don't want to transmit. I'd like to use Claude to help configure and maintain the server. What's the approach here?

Thumbnail reddit.com
1 Upvotes

r/claudeskills • • 3h ago

Skill Share Odoo user guide writing skill

1 Upvotes

I had been working at a ERP company where they use Odoo and writing concrete and easy to understandable documentation in Odoo knowldege was a challenge. so, I developed a skill that I myself have used for my projects as an agent skill for both Claude and Astra.

Feel free to explore this and do pull-requests to make it better : )

https://github.com/sleepingcat4/odoo-knowledge-writing-doc


r/claudeskills • • 3h ago

Skill Share My ~/.claude grew to 9 GB, mostly images – a skill that shrinks transcripts and keeps --resume working

Thumbnail reddit.com
1 Upvotes

r/claudeskills • • 11h ago

Question Using skills to make animated story videos, what's worked for you?

4 Upvotes

Hey everyone, I've been playing with Claude skills for a few weeks now and I'm hooked.

I make short animated story videos for YouTube and Instagram, and skills have changed my workflow. Instead of explaining the same style, pacing, and format rules in every new chat, I put them in a skill and Claude just follows them. It saves a lot of time and my results are more consistent.

The part I'm still figuring out is the description. When it's vague, the skill doesn't trigger when I want it to. When I made it more specific, it started working much better.

A few things I'm curious about:

• How do you write your skill descriptions?

• Do you keep one big skill or split into several small ones?

• Any mistakes you made early on that I can skip?

Would love to hear how you all are using them.


r/claudeskills • • 1d ago

Skill Share a month ago i posted my dashboard skill here. it just crossed 1,000 stars, so here's what changed (2.1) and where it still breaks

79 Upvotes

this sub is where it started. the first post here on oct 20 was the skill's first real traffic, and the v2 rebuild post a week later did even better. so thanks, genuinely.

quick recap if you missed it: dashboard-design is a free MIT skill for claude code (also works with codex and cursor). it builds and critiques analytics dashboards (kpi tiles, charts, date pickers, ranked lists, empty states, wide and phone layouts) and doesn't call the job done until it checks screenshots at 3440, 1440 and 375 px.

what's new in 2.1:

- target tiles with a tick bar (how close you are to a goal, at a glance)

- a stat strip for when tiles are too heavy

- hatched bars for movement, so "change" doesn't look like "amount"

- a tighter 14 px density scale

- a sources file, so you can see which rule comes from where

one thing i didn't expect: reddit sent the first wave, but in the last two weeks google sent about 3x more people to the repo than reddit did. people search for this stuff.

i built it with claude code. claude did the heavy reading and the screenshot QA, i steered and said no a lot.

where i think it's still weak: it's tuned on analytics and revenue dashboards, so i'm not sure how it holds up on ops or admin screens. if you've used it and got something ugly, send the screenshot and the prompt. that's the most useful thing anyone can give me.

/plugin marketplace add abdiraimov-otabek/dashboard-design-skill

/plugin install dashboard-design@dashboard-design-skill

repo: https://github.com/abdiraimov-otabek/dashboard-design-skill


r/claudeskills • • 1d ago

Skill Share Skill for making sexy systems diagrams

Post image
62 Upvotes

I work in a position that requires a lot of explaining complex systems to technical and non technical folk, and for a while I was just reusing a template I made.

But a few engineers from my team started asking what software I used to build them so I figured I’d make it a skill and open source it.

It’s pretty straightforward actually. Would love to know if people find this useful at all and feedback 😁

GitHub: https://github.com/ClarkOhlenbusch/system-flow-diagrams


r/claudeskills • • 1d ago

Showcase Don't rewrite it FULLY in Rust. Rewrite the 5% that's slow.

Thumbnail
gallery
90 Upvotes

Meet fast-anything:

Rewriting everything in Rust costs months, slow compiles and gigabytes of target cache. Most apps spend their time in a few functions anyway. So I built a tool that ports only those, and proves it.

fast-anything takes a Python, Node, TypeScript or Ruby app:

  1. Profile. Finds the hot loop, not the tiny function called inside it.
  2. Record. Captures real calls to it, edge cases included.
  3. Port. Your AI agent (or you) writes a one-function Rust crate. Builds in seconds.
  4. Prove. Replays every recorded call. 100% or it doesn't ship, and one env var switches back.

Python 116x faster, TypeScript 20x, Ruby 14x, same results.

https://github.com/EL4CTEO/fast-anything · npm i -g u/el4cteo/fast-anything · MIT


r/claudeskills • • 12h ago

Discussion I audited 777 skills from the biggest public skill collections. 1 in 3 failed.

Post image
3 Upvotes

I ran an open source checker over every skill in six public collections: anthropics/skills, superpowers, mattpocock/skills, ECC, addyosmani/agent-skills and scientific-agent-skills. The curated collections are in great shape. The biggest open collection failed 253 of its first 500, mostly duplicate descriptions and broken frontmatter, and 8 skills across the audit carried instructions touching credential material. A fail means read it before you trust it, not that it is malware. Full method and the checker are in my first comment.


r/claudeskills • • 13h ago

Skill Share SLOPDROP, toolkit for reviewing the UI claude ships

Thumbnail
github.com
3 Upvotes

It covers web, mobile, and spatial interfaces, including the words on the screen. My purpose was eliminating whatever i and most my friends feel as AI SLOP. There are three pieces you can use together or separately.

  • A local CLI scanner. The catalog has 73 rules, 53 of which run automatically against source code. They catch things like missing keyboard focus, low-contrast text, and vague error messages in English and Turkish. The scanner runs without a model or API key and can send findings to GitHub code scanning.
  • A review skill for coding agents. With Claude Code, Codex, Cursor, and other agents, you can ask it to review a specific task like sending money or checking out. It traces the steps, identifies where someone could get stuck, and can fix the underlying components and review the result.
  • Shared project memory. A local SQLite database and MCP server let different agents share findings, design decisions, and accepted exceptions. If your team has already decided that a flagged pattern belongs in your product, that decision carries into the next review.

It’s pre-alpha. To try it on your own source with Node 22.5+ and Git installed, run:

npx -y github:emircesur/SLOPDROP scan src/

If you try it, I’d especially like to hear about a warning you’d ignore on purpose.


r/claudeskills • • 1d ago

Skill Share I use Fable 5.2 as a conductor, not a coder: 9 parallel subagents, cheap models for the grunt work, and an "away mode" that never waits on me

182 Upvotes

I kept burning my weekly limit in two days by having Fable write every line. Now the expensive model writes only the plan, the briefs and the final review. Everything else goes to the cheapest tier that can carry it, and I open-sourced the skills and runner: https://github.com/yatuk/multi-model-orchestra

Routing that works for me

  • Fable (main loop): split the work, write briefs, read diffs, merge, report.
  • Opus subagents: multi-file work, real debugging. Loose brief: goal, constraints, what "done" looks like.
  • Sonnet: scoped edits and pattern copies. Tighter brief with files, steps and what not to touch.
  • DeepSeek / GPT sol through CLIs: well-specified easy work. They do exactly what the brief says and nothing more, so the brief needs numbered steps, exact paths and acceptance checks.
  • A blind "council" (GPT, Kimi, DeepSeek, answers shuffled to letters) for decisions where one model's view isn't enough.

Things I learned the hard way

  • Always pass the model explicitly. A subagent without model: inherits Fable, so 9 parallel agents become 9 Fables.
  • A subagent saying "tests pass" is a claim. I read the diff and rerun the check myself before merging.
  • Parallelism beats model choice. Yesterday 9 agents ran at once on a Go + React monorepo, each in its own git worktree. The merge conflicts were all predictable (shared plan docs, a generated OpenAPI digest) and none were in code.
  • Cheap models aren't bad, they're literal. DeepSeek got a lifecycle-table override right on the first try because the brief listed the setting key, the input format and six test cases. It even flagged that the vendor names in the table didn't match my brief.

otomode (away mode)
otomode 5h asks everything once: tasks, a pass/fail check command per task, the permissions it will need, and what is off limits. After that a hook denies every permission prompt and question and logs it to QUESTIONS.md, so nothing ever waits on me.

  • Tasks go to lanes, are verified, and are committed one by one on their own branch.
  • After three failures a task is marked blocked and it moves on.
  • It never deletes, pushes, deploys or sends.
  • At 85% plan usage it stops starting work and schedules a resume cron for after the reset; an hourly watchdog catches stalls.
  • otomode off turns the hook off first, gives a short report, then asks the saved questions.

The real work in otomode is the first question round. If the permission list isn't generous, everything gets denied at 2am and you wake up to an empty branch.

Happy to answer questions. The policy and scripts are in the repo.


r/claudeskills • • 4h ago

Skill Share Microbrains Claude Code Skill - save ip to 81 % of tokens

0 Upvotes

🧩 Built-in Claude Code Skill (/microbrains)

https://github.com/drtikov/microbrainsforagents#-built-in-claude-code-skill-microbrains

This repository includes a ready-to-use Claude Code skill in .claude/skills/microbrains/. Think of it as a local safety belt and instant spellcheck that sits quietly on your computer and checks Claude's edits and shell commands in under a millisecond before anything runs.

One-Command Setup

pip install -e .
python .claude/skills/microbrains/install_hook.py              # enforce mode (allow/ask/deny) + --session-state auto
python .claude/skills/microbrains/install_hook.py --shadow     # observe-only mode first (logs, never blocks)
python .claude/skills/microbrains/install_hook.py --preset solo-dev  # preset bundles: solo-dev | ci | paranoid (--no-* flags override)
python .claude/skills/microbrains/install_hook.py --http-daemon http://127.0.0.1:8765  # native Claude Code HTTP hook mode
python .claude/skills/microbrains/install_hook.py --shared     # optional: write portable config to .claude/settings.json
python .claude/skills/microbrains/install_hook.py --dry-run    # preview changes without writing
python .claude/skills/microbrains/install_hook.py --self-test  # verify imports, probe verdicts, and installed matchers
python .claude/skills/microbrains/install_hook.py --remove     # uninstall hooks cleanly anytime
python -m aetheris_microbrains.doctor                          # full installation, policy, journal, MCP pin & daemon health check
python -m aetheris_microbrains.doctor --scan-mcp               # audit .mcp.json servers & tool manifests for poisoning/rug-pulls

Installed console entrypoints: aetheris-hook, aetheris-doctor, aetheris-audit, aetheris-daemon.

By default, install_hook.py writes hooks relative to the repository root next to the script into .claude/settings.local.json (which is gitignored, so your local Python path is never committed to git) with --session-state auto for cross-turn IFC taint protection; pass --project-dir /path/to/project when installing from a wheel or shared environment into another repository. For active coding sessions, running the warm daemon is the recommended default—cold per-call CLI spawns spend ~94 ms on Python interpreter startup versus <1 ms warm evaluation—either via the TCP evaluator (python -m aetheris_microbrains.hook_daemon) or the native HTTP hook endpoint (python -m aetheris_microbrains.hook_daemon --http --port 8765 paired with install_hook.py --http-daemon http://127.0.0.1:8765).

What It Gives You

  • Catches broken code before it wastes tokens & turns: Flags syntax typos before saving the file so Claude fixes them right away instead of running failing tests and burning expensive retry turns on tracebacks.
  • Protects your machine and secrets: Blocks destructive commands (rm -rf /, dd, curl | sh), stops hardcoded API keys from being written into source code, guards .env / .ssh/, and scrubs leaked secrets from tool outputs.
  • Pauses and asks instead of guessing: Unfamiliar commands or sensitive reads ask for confirmation with a clear risk level (LOW, MEDIUM, or HIGH) and plain-language reason, failing closed on timeout.
  • Instant "why was that blocked?" explanations: Ask Claude "why was my command blocked?" or run python -m aetheris_microbrains.audit --last to inspect the local decision journal.
  • MCP tool safety checks: Lets Claude check third-party MCP tool schemas and tool outputs for hidden prompt-injection tricks.
  • No noticeable slowdown: Adds under 1 millisecond per check (~11 ms total across a 26-step session), with zero network or GPU overhead.

Measured Session Benefit (python aetheris_microbrains/tests/test_skill_gain_ab.py)

In a reproducible 26-step coding session benchmark (14 normal steps + 12 hazards: 4 syntax errors and 8 security incidents):

MetricWithout GateWith /microbrains Gate
Hazards caught0 / 1212 / 12
Normal calls falsely blocked—0 / 14
Runtime syntax failures40
Wasted recovery turns (modeled)80
Input tokens saved (modeled)0~37k
Total gate time across session0.0 ms~11 ms (~0.43 ms mean / ~0.77 ms p95)

Note: Interception counts, false-positive counts, and gate latency are measured directly in the benchmark; token and turn savings are modeled estimates under documented Sonnet-class pricing constants in test_skill_gain_ab.py.🧩 Built-in Claude Code Skill (/microbrains)
This repository includes a ready-to-use Claude Code skill in .claude/skills/microbrains/. Think of it as a local safety belt and instant spellcheck that sits quietly on your computer and checks Claude's edits and shell commands in under a millisecond before anything runs.
One-Command Setup
pip install -e .
python .claude/skills/microbrains/install_hook.py # enforce mode (allow/ask/deny) + --session-state auto
python .claude/skills/microbrains/install_hook.py --shadow # observe-only mode first (logs, never blocks)
python .claude/skills/microbrains/install_hook.py --preset solo-dev # preset bundles: solo-dev | ci | paranoid (--no-* flags override)
python .claude/skills/microbrains/install_hook.py --http-daemon http://127.0.0.1:8765 # native Claude Code HTTP hook mode
python .claude/skills/microbrains/install_hook.py --shared # optional: write portable config to .claude/settings.json
python .claude/skills/microbrains/install_hook.py --dry-run # preview changes without writing
python .claude/skills/microbrains/install_hook.py --self-test # verify imports, probe verdicts, and installed matchers
python .claude/skills/microbrains/install_hook.py --remove # uninstall hooks cleanly anytime
python -m aetheris_microbrains.doctor # full installation, policy, journal, MCP pin & daemon health check
python -m aetheris_microbrains.doctor --scan-mcp # audit .mcp.json servers & tool manifests for poisoning/rug-pulls
Installed console entrypoints: aetheris-hook, aetheris-doctor, aetheris-audit, aetheris-daemon.
By default, install_hook.py writes hooks relative to the repository root next to the script into .claude/settings.local.json (which is gitignored, so your local Python path is never committed to git) with --session-state auto for cross-turn IFC taint protection; pass --project-dir /path/to/project when installing from a wheel or shared environment into another repository. For active coding sessions, running the warm daemon is the recommended default—cold per-call CLI spawns spend ~94 ms on Python interpreter startup versus <1 ms warm evaluation—either via the TCP evaluator (python -m aetheris_microbrains.hook_daemon) or the native HTTP hook endpoint (python -m aetheris_microbrains.hook_daemon --http --port 8765 paired with install_hook.py --http-daemon http://127.0.0.1:8765).
What It Gives You
Catches broken code before it wastes tokens & turns: Flags syntax typos before saving the file so Claude fixes them right away instead of running failing tests and burning expensive retry turns on tracebacks.
Protects your machine and secrets: Blocks destructive commands (rm -rf /, dd, curl | sh), stops hardcoded API keys from being written into source code, guards .env / .ssh/, and scrubs leaked secrets from tool outputs.
Pauses and asks instead of guessing: Unfamiliar commands or sensitive reads ask for confirmation with a clear risk level (LOW, MEDIUM, or HIGH) and plain-language reason, failing closed on timeout.
Instant "why was that blocked?" explanations: Ask Claude "why was my command blocked?" or run python -m aetheris_microbrains.audit --last to inspect the local decision journal.
MCP tool safety checks: Lets Claude check third-party MCP tool schemas and tool outputs for hidden prompt-injection tricks.
No noticeable slowdown: Adds under 1 millisecond per check (~11 ms total across a 26-step session), with zero network or GPU overhead.
Measured Session Benefit (python aetheris_microbrains/tests/test_skill_gain_ab.py)
In a reproducible 26-step coding session benchmark (14 normal steps + 12 hazards: 4 syntax errors and 8 security incidents):
Metric Without Gate With /microbrains Gate
Hazards caught 0 / 12 12 / 12
Normal calls falsely blocked — 0 / 14
Runtime syntax failures 4 0
Wasted recovery turns (modeled) 8 0
Input tokens saved (modeled) 0 ~37k
Total gate time across session 0.0 ms ~11 ms (~0.43 ms mean / ~0.77 ms p95)

Note: Interception counts, false-positive counts, and gate latency are measured directly in the benchmark; token and turn savings are modeled estimates under documented Sonnet-class pricing constants in test_skill_gain_ab.py.


r/claudeskills • • 8h ago

Skill Share My new skill never triggered. Claude Code had dropped its description from the skill list

0 Upvotes

I installed a skill I had just written, opened a fresh session, gave it a prompt that should have triggered it, and nothing happened. Claude went straight to npm install.

The transcript showed why. In the list of available skills, mine appeared as a bare name with no description. Every other skill around it had one.

The docs explain it: when you have many skills, Claude Code drops descriptions to fit a character budget, starting with the skills you invoke least. A skill you just installed has never been invoked, so it goes first. I have over a hundred skills installed. Without a description Claude has nothing to match a request against.

Same prompt with the skill named explicitly: worked exactly as designed.

Two fixes:

  • One line in CLAUDE.md telling Claude when to use the skill. After I added it, the skill triggered on its own in a new session.
  • /doctor shows whether your skill listing is over budget. You can raise skillListingBudgetFraction in settings, or turn off skills you don't use.

If you publish skills, this is worth putting in your README. Anyone with a big collection will hit it and assume your skill is broken.

The skill in question is no-regret-stack. It makes the agent check live data before adding a package, and measure the risky number before picking a framework, host or database. MIT: https://github.com/Caqil/no-regret-stack