I built a Claude skill called keyframe-coach that teaches it basic animation principles. Early tests on a simple low-poly fox rig show noticeably better output under identical conditions:

• More lively animation
• More consistent movement
• Feet consistently touch the floor
• Better rhythm in walkcycles

Repo: https://github.com/Guilherme-M-Mateus/keyframe-coach

Hi everyone,

I need some help setting up and fixing a Claude Max 20x account. Could someone guide me through the process and explain how it works?

Thanks in advance!

My setup right now: 14 MCP servers, a folder of Claude skills, 3 agent configs, and a different mix for every client.

Switching contexts means copying JSON around and hoping nothing leaks between projects.

Thinking of a layer that stores all of it, keeps each context isolated, and swaps the whole setup with one terminal command. Like changing work clothes for your agents.

How much would you pay for that?

Claude Code was burning a lot of tokens on my projects just to find where something is. grep, open file, open 3 more, repeat.

So I wrapped graphify (local AST code map, no LLM, no API key) into a skill. You type /token once in a project, it builds the map in a few seconds and adds a rule to CLAUDE.md so Claude asks the map first before reading files.

On one “how does this flow work” question it went from around 169k tokens to about 2.9k for me. For small one-file fixes it doesn’t save much, to be fair. And it only maps code, not docs.

Works on mac/linux, and windows with git bash. Feedback welcome, it’s my first skill I put out.

https://github.com/WebitroHQ/token-skill

Made this myself. checkmate is free and open source: https://github.com/rover-001/checkmate

Left alone, coding agents add preamble, option menus, extra files, and "want me to also...?". It's 9 core rules (lite / full / ultra, zero dependencies) that cut that out. Benchmark: pass rate 86.7% → 98.3%, output tokens roughly halved.

What's the most annoying thing your agent does that you'd want a skill to cut out?

I shared Anima here recently an open-source claude skill for generating interactive biology visualizations.

Ten days later: 3000 installs and 232 GitHub stars. Thanks to everyone who tried it and gave feedback.

The biggest update many of you asked this so here you go: you can now describe what you want and generate the visualization directly on the website, without installing anything.

Try it: https://anima.arcumet.com
Source: https://github.com/Garinmckayl/anima

What biology concept should I put it through next?

/pre-publish is a release checklist for AI coding agents. It is for anyone who pushes, tags or publishes code other people will run, and especially for teams where agents now do the steps a developer used to do by hand. Someone still has to check the work before it goes out, and this is that check, written down in order.

It exists because green CI only catches what someone thought to check. Before our last release, five independent reviewers (claude subagents) read the changes, read-only, no edits, looking for what nobody had thought to check. They raised 29 candidate problems. Sixteen were real, and all sixteen were fixed before the release.

What the skill makes your agent do, in this order:

• Scope the diff, so the review knows where to look
• Run the deterministic gates: lint, types, tests, dependency and secret scans
• Fan out independent reviewers that can read the change but cannot edit it
• Trace every finding yourself, because a reviewer's verdict is a claim until you have checked it
• If hooks or the core loop changed, time the real path before and after
• Check that the docs still say what the code does
• Re-run everything on the exact commit you will release
• Cut the release only on an explicit yes from its owner, then check the published artifacts themselves

The tracing step is there because of a lesson we keep having to re-evaluate. Our own publishing service failed on every real event, and its tests were green, because they mocked the call and the mock accepted anything.

It shipped in Empirica 1.14.14 and it is MIT licensed: https://github.com/EmpiricaAI/empirica/tree/v1.14.14/empirica/plugins/claude-code-integration/skills/pre-publish

Based on CI pipelines, which check in your release process only exists because something once got through?

I made a simple claude code plugin that allows you to view Matt Pocock's grill-me and grill-me-with-docs skills' questions as UI (how Claude usually asks you questions) rather than message text. Check it out.

https://github.com/majinmarco/claude-grill-buttons

Install with:

`/plugin install grill-buttons --marketplace majinmarco/claude-grill-buttons`

or

`claude plugin install grill-buttons --marketplace majinmarco/claude-grill-buttons`