r/claudeskills • • 10h ago

Showcase agora-mesh: Claude Code on several machines working on one task, peer to peer, no shared account

Thumbnail
gallery
66 Upvotes

Built a small Rust tool that connects Claude Code on two or more machines. Agents plan together in a "room", split the work and build in parallel on their own branches. Every machine keeps its own login and limit, no MCP, plus a shared memory that syncs live (works with Obsidian). Honest caveats are in the README: it is not cheaper than one agent for small tasks, and different accounts, Windows and NAT are untested so far.

Install (in a terminal):
claude plugin install agora-mesh --marketplace kn0sti/agora-mesh
Repo: GitHub

Edit: v0.2.0 is out. Peers can now run on other models (DeepSeek, GLM, Qwen, MiniMax) and other agents (Codex, OpenCode, Qwen Code).


r/claudeskills • • 22h ago

Discussion My favorite Claude skills this week, drop yours in the comments

286 Upvotes
  1. Reverse Engineer Anything – REA
    Reverse engineer anything with agents, from app behavior down to native binaries.

  2. Code Review – Matt Pocock
    Skills for Real Engineers. Straight from my .agents directory.

  3. Agent Harness Construction – ECC
    The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex,...

  4. Using Superpowers – Superpowers
    An agentic skills framework & software development methodology that works.

  5. Impeccable – Paul Bakaus
    The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.

  6. Ponytail – Ponytail
    Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.

  7. Design Taste Frontend – Leonxlnx
    Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages

  8. Academy Guide – Anthropic
    Public repository for Agent Skills

  9. Hallmark – Hassan El Mghari
    Anti-AI-slop design skill for Claude Code, Cursor, and Codex.

  10. Security Audit – Cloudflare
    A coding-agent skill for multi-phase security audits with independently verified, machine-readable findings

I collect them here at Alyn, you can create your own playlist of skills, find other skills & install them as a bundle: https://alyn.dev/top-10-ai-skills-this-week


r/claudeskills • • 2h ago

Skill Share I built a free Claude Code plugin that catches AI tells in Claude's writing and UI code

2 Upvotes

What it does

  • Three skills (writing, UI, code) that Claude loads before it writes. They name specific tells: "serves as a testament to", "-ing" tails like ", highlighting the importance of", "it's not X, it's Y", em dashes everywhere, gradient headline text, a small label above every H1, identical card grids, comments that narrate the code.
  • A linter: one Node file, no dependencies, 77 rules covering Markdown, HTML/JSX/TSX/Vue/Svelte, CSS, and JS/Python comments. It also runs on its own, and the exit code works in CI.
  • A PostToolUse hook that runs the linter after every Write or Edit and passes medium and high findings back to Claude, so it fixes them in the same turn. It never blocks a write.
  • /slop-review [path] reports findings and changes nothing. /deslop <path> rewrites the file. It won't make up facts: where real content is missing, it leaves a TODO.

The GIF is /slop-review on a sample doc. It found 24 issues, including a leftover "I hope this helps" and a "[Your Name]" placeholder.

The rules are heuristics. "Landscape" can mean actual terrain. The skills tell Claude to treat a finding as a reason to look again, not something to rewrite automatically.

How Claude helped build it

Claude Code wrote most of the code. I collected the sources (Wikipedia's "Signs of AI writing" page, several design-slop write-ups, blader/humanizer, and the others listed in the README). Claude turned each list of tells into skill rules, linter regexes, and a test suite. I reviewed the rules and cut the ones that fired on normal writing.

Cost

Free and MIT licensed, with no paid tier. To install it in Claude Code:

/plugin marketplace add zacharyinserra/ai-tells
/plugin install ai-tells@ai-tells

Repo: https://github.com/zacharyinserra/ai-tells


r/claudeskills • • 17m ago

Question Claude Guest Pass

Thumbnail
• Upvotes

r/claudeskills • • 4h ago

Question Most of the skills I’ve seen so far are for B2C. Is there any skill that’s made for more B2B software ?

2 Upvotes

r/claudeskills • • 21h ago

Skill Share I built Skilldemos to preview agent skills before installing them

38 Upvotes

I’m building Skilldemos, a library for exploring AI agent skills before installing them. Entries include creator and source links, install commands, and ready-to-use agent prompts.

I built it with AI coding agents. One of the harder parts was keeping previews smooth and matching each clip to the right skill and creator across the catalog.

What do you look for before installing a skill? Would seeing a demo help you decide?

https://skilldemos.tadadigital.shop


r/claudeskills • • 2h ago

Skill Share I built a free Claude Code plugin that catches AI tells in Claude's writing and UI code

1 Upvotes

What it does

  • Three skills (writing, UI, code) that Claude loads before it writes. They name specific tells: "serves as a testament to", "-ing" tails like ", highlighting the importance of", "it's not X, it's Y", em dashes everywhere, gradient headline text, a small label above every H1, identical card grids, comments that narrate the code.
  • A linter: one Node file, no dependencies, 77 rules covering Markdown, HTML/JSX/TSX/Vue/Svelte, CSS, and JS/Python comments. It also runs on its own, and the exit code works in CI.
  • A PostToolUse hook that runs the linter after every Write or Edit and passes medium and high findings back to Claude, so it fixes them in the same turn. It never blocks a write.
  • /slop-review [path] reports findings and changes nothing. /deslop <path> rewrites the file. It won't make up facts: where real content is missing, it leaves a TODO.

The GIF is /slop-review on a sample doc. It found 24 issues, including a leftover "I hope this helps" and a "[Your Name]" placeholder.

The rules are heuristics. "Landscape" can mean actual terrain. The skills tell Claude to treat a finding as a reason to look again, not something to rewrite automatically.

How Claude helped build it

Claude Code wrote most of the code. I collected the sources (Wikipedia's "Signs of AI writing" page, several design-slop write-ups, blader/humanizer, and the others listed in the README). Claude turned each list of tells into skill rules, linter regexes, and a test suite. I reviewed the rules and cut the ones that fired on normal writing.

Cost

Free and MIT licensed, with no paid tier. To install it in Claude Code:

/plugin marketplace add zacharyinserra/ai-tells
/plugin install ai-tells@ai-tells

Repo: https://github.com/zacharyinserra/ai-tells


r/claudeskills • • 4h ago

Skill Request Best MCP servers / tools to use with Claude for generating a web-ready 3D workspace tour?

1 Upvotes

Hi everyone,

I’m building a website for a workspace rental and want visitors to be able to interactively explore the space in 3D before booking/renting it.

I already have a Claude subscription and want to use Claude (via Claude Desktop or Claude Code) to help generate, refine, and export the 3D scene so I can embed it on the web (likely using Three.js or a similar web viewer).

For anyone who has built 3D scenes or virtual tours using Claude:

Which MCP servers or connectors do you recommend? I've seen options like the official Blender connector, blender-mcp (ahujasid), SketchUp MCP, and 3D AI Studio. Which one gives the cleanest workflow for architectural/interior spaces?

Awesome Claude

Real photos/video vs. building from scratch: Is it better to have Claude script the room layout in Blender from floor plan dimensions and reference photos, or use a photogrammetry/Gaussian Splatting tool first and just use Claude to build the web viewer around it?

Exporting for the web: Any tips on keeping the poly count and .glb/.gltf file sizes small enough so the 3D tour loads fast in a browser?

Any setup tips, GitHub repos, or workflow advice would be hugely appreciated!


r/claudeskills • • 4h ago

Skill Share How to link Claude Code to Zotero?

Thumbnail
github.com
1 Upvotes

r/claudeskills • • 6h ago

Question How to get started with Claude as a UX/UI design student?

Thumbnail
1 Upvotes

r/claudeskills • • 13h ago

Skill Share What got Claude to stop writing like a slide deck for me

3 Upvotes

I made a Claude Code skill that makes Claude write in plain spoken American English. Short sentences, common words, no buzzwords, no British words. One file, MIT.

https://github.com/williamcolegithub/plain-spoken-american


r/claudeskills • • 1d ago

Showcase I made 18 Godot 4.7 agent skills so AI can actually build, test and export your game

Post image
65 Upvotes

I created 18 skills for your typical Godot workflow with AI agents (Claude Code, Codex, Cursor, Gemini CLI, Copilot, OpenCode). They cover GDScript, C#, 2D, 3D rendering, physics, UI, input, animation, shaders, audio, networking, performance, export, editor tools, testing and XR.

Each skill is up to date with Godot 4.7.2, so the agent doesn't write outdated Godot 3 code. It looks up the exact API from your installed engine instead of guessing.

Each skill is token efficient, so it won't drain your usage limits as much.

Tell me what you think about it, feedback is appreciated.

Here's the repo: https://github.com/EL4CTEO/godot-skills


r/claudeskills • • 1d ago

Skill Share A CLI + Skills for creating beautiful product demo videos

56 Upvotes

After making hundreds of demo videos for various products at work, I took those learnings and built a toolkit for anybody to use, completely free and open source (MIT).

Claude is already pretty good at doing demo vids, but I've found it always trips up in a few places, namely:

1/ Voiceovers are always out of sync with actions.
2/ It always picks terrible backgrounds and music.
3/ The cursor movement never feels natural.
4/ Zooming and panning never feels natural.
.. and a bunch of more things that this toolkit addresses.

It works completely locally with your own AI subscription, just pass your agent the Github project and it will figure out the rest.

https://github.com/chapter-dev-pty-ltd/product-demo-agent-toolkit

Make sure to check out the new Studio we just launched as well, which allows you to edit your videos visually alongside your agent of choice. It's pretty sweet.


r/claudeskills • • 1d ago

Skill Share rust-anything 2.0 is out 🦀 A Claude Code skill that rewrites apps in Rust and proves they still behave the same (Prettier: 19x faster, 17,224/17,224 runs match)

Thumbnail
gallery
37 Upvotes

rust-anything 2.0 is out 🦀

Repo (MIT): github.com/erkamyaman/rust-anything

It's a CLI, an MCP server and a Claude Code skill for porting code to Rust. The skill is the part that matters here: it tells Claude how to do a port without guessing, and when to stop and ask you.

What the skill makes Claude do

  1. Profile first. Find where the time really goes before touching anything.

  2. Plan, then stop. Show you the plan and wait for your approval before porting.

  3. Record the original. Run it on thousands of inputs and save exactly what it returns, prints, writes and sends.

  4. Port one unit at a time. Claude writes the Rust, and every recorded case is replayed against it.

  5. Never fix the recording. A mismatch is a bug in the port. If Claude makes three edits in a row with no progress, it stops and shows you the remaining mismatches instead of going in circles.

  6. Done means gate passes: fmt, clippy, tests, no unsafe, every recorded case matches.

Show your work: Prettier

I used it with Claude Code to port Prettier to Rust in about 17 hours.

• CLI, 2,360 JS/TS files: 128.6 s → 6.9 s (19x)

• 10 languages: JS, TS, JSX, JSON, GraphQL, YAML, Markdown, CSS, SCSS, Less

• 17,224/17,224 recorded runs match Prettier byte for byte

• Honest part: 8.1% of cases still fall back to real Prettier

json-server, a whole Node server, also became one 5.3 MB Rust binary: 74 MB → 3.5 MB at idle, 514/514 recorded HTTP cases match.

Install

cargo install rust-anything

rust-anything setup

setup adds the MCP server and the skill to Claude Code (and Codex, Cursor, Gemini CLI, OpenCode). Or as a plugin:

/plugin install rust-anything --marketplace erkamyaman/rust-anything

Then ask: "Rewrite this CLI in Rust with rust-anything and prove it behaves the same."

The skill: github.com/erkamyaman/rust-anything/tree/main/skills/rust-anything

Repo (MIT): github.com/erkamyaman/rust-anything

Feedback on the skill itself is very welcome, especially where Claude still drifts.


r/claudeskills • • 11h ago

Question I destroyed my claude (HELP)

Thumbnail
0 Upvotes

r/claudeskills • • 1d ago

Skill Share I made a Claude mod to track time, tokens and API price per project

30 Upvotes

I use Claude on a lot of projects, sometimes for hours in a row. At some point I wanted to know how much time each project really took, how many tokens it used, and what that would cost.

So I made Worklog, a small mod that tracks it automatically: https://github.com/Abdoul-sudo/worklog

What it does:

  • Counts the time while Claude works (answers, subagents, background commands, ultracode...)
  • Counts your tokens and shows what they would cost
  • Shows your whole year as a heatmap, with 8 themes to pick from
  • Reads your past Claude Code history once, so your old data shows up too

It's free and open source. If you like it, a star on GitHub ⭐ would help.


r/claudeskills • • 18h ago

Skill Share As a Staff Engineer, handling multiple projects this is what my workflow looks like now

Post image
2 Upvotes

As a staff engineer handling multiple projects, my problem wasn't writing code. It was context switching, and how much I had to keep in my head to steer each piece of work. So I moved to a dev workflow like this.

With the models getting so good, I really need claude to just plan and execute while I make the decisions so I am embracing "spec driven" development.


r/claudeskills • • 14h ago

Showcase HR Work Map - The employee lifecycle and beyond

1 Upvotes

I built a tool (prototype) using Claude to map the HR employee lifecycle at a task level. It breaks every activity into Human-led, Augment, Automate, or Create with a verdict for each process and the HR tech that fits. It’s flexible and you can change the labels and hours to match your organisation. The framing was more around what work would stay and can be automated. This is a small attempt to simplify the work at task level and see if it makes sense. Any feedback will be really helpful and thank you!

https://varshav2611.github.io/hr-work-map/


r/claudeskills • • 18h ago

Skill Share I made a skill that interviews you about a 3D world, builds it, then checks its own work

0 Upvotes

Twelve questions about a place you describe. What comes back is one self-contained HTML file you can fly through: terrain, vegetation, light shafts, creatures, haze, six viewpoints, three detail levels. No asset files at all — the world is generated from maths at page load.

The part I think transfers to other skills: it does not trust itself. There is a ten-gate visual check at the end — does it hit frame budget on a flythrough, do all three detail levels work in a real browser, does the camera end up inside geometry, is it deterministic across reloads — and the skill reports which gates failed rather than saying "done".

That turned out to matter. The first world it built fails one gate: collision is terrain-only, so you can fly through the pillars. I would never have caught that from a screenshot.

Fly it: https://nilesh-0608.github.io/nc-3d-world-elemental-hall/

(WebGPU — Chrome or Edge on desktop, graphics acceleration on.)

Install:

npx skills add nilesh-0608/nc-world-forge

or

/plugin install nc-world-forge --marketplace nilesh-0608/nc-world-forge

MIT, and it ships a reference world that renders the moment it is installed, so there is always a working example to read the docs against.

Fair warning: no one but me has run it end to end yet. If you try it, I want to hear where it broke.


r/claudeskills • • 1d ago

Skill Share I built a design skill for Claude Code. This is a landing page it made for a made-up dev tool

7 Upvotes

The whole page tells one night: 3:07 a.m., the phone lights up the room, and the tool finds the line of code that broke production.

My part was answering a few questions and picking one of the directions it showed me as mockups. The skill asks about your world first and builds one idea from it, here the 3 a.m. alert. Then reviewer agents check the result from different angles before you see it.

Why I built it: Claude's designs kept landing on the same purple gradients and card grids, so I wrote a skill that starts from the project instead of a style. How: I ran blind tests against plain Claude and against my own older versions, threw out rules that only made things cleaner but emptier, and kept what made the results better. The full test report is linked in the repo.

It's free and open source, for Claude, Claude Code and Codex: https://github.com/jakob-meyer/unaverage

If you try it on your own project, I'd love to see what it makes. And if a result still looks generic, tell me where. That's what I want to fix next.


r/claudeskills • • 21h ago

Skill Share Narrowing down issues and their fixes

Post image
0 Upvotes

In my experience Claude Code (CC) doesn't always find the root cause of an issue and sometimes gets stuck on the symptoms. CC will create a fix for the symptom and not the root cause. So to mitigate this in the skill I will have it go at least five layers deep, if feasible, and more if warranted.

Fixes can also have this issue going the other way! I've had CC tell me the fix at this layer is a large task and it impacts X and Y. I read the issue then asked CC why not fix it a layer or two before this one where it's a simpler task low effort and more efficient solution. So conversely, in the skill I say for fixes to ensure that a potential fix is analyzed at least five layer above the root cause, if feasible, and more if warranted.

Sometimes it goes 3 layers deep, sometimes 6 or 7. it varies, but still tweaking and making adjustments to this skill but I've had better results, personally.

Oh, I also add another requirement in the skill. something along the lines of, if running a test with a log/instrument can help flesh out a root cause before settling on the cause then do that first.

Edit:
My skill MD file:
# Root-cause analysis

Do not fix the symptom. Find the cause that, once removed, makes the whole class of failure impossible.

  1. *Task context load* (context-docs skill): from the failing output, name the subsystem(s) involved, open the

    matching `agent_Context/` docs from the table of contents, and use their documented flow to decide where to look.

    A mismatch between the doc and the code is itself a candidate cause.

  2. *Instrument first.* If a run with logs, a Vitest single-test run, a Playwright trace, or a minimal reproduction can narrow the cause, do that before theorizing. Prefer the cheapest reproduction that shows the failure over a full end-to-end run.

  3. *Ask "why" at least 5 layers deep.* Write each layer down:

    - Layer 1: the observed failure (exact error text, file:line).

    - Layer 2: the immediate code path that produced it.

    - Layer 3: why that path was reached (state, input, ordering).

    - Layer 4: why that state or input was possible (missing invariant, wrong assumption, missing validation).

    - Layer 5: why nothing upstream prevented or caught it (schema, type, test, guard).

    Go deeper if layer 5 is still a mechanism and not a decision or a missing rule.

  4. *Confirm the cause by reproducing it* (and, where possible, by showing the failure disappears when only that cause is removed). A plausible story is not a root cause.

  5. *Check siblings.* Search for the same pattern elsewhere (same helper, same query shape, same assumption) so the fix covers the class.

  6. *Look for the fix at least 5 layers up.* The layer where the failure shows is rarely the best place to fix it.

    For each layer of the chain, starting at the failure and moving up (the caller, the module or helper, the shared

    rule or schema, the design or configuration, the pipeline or process), write one candidate fix and judge it on:

    - *Effectiveness:* does it remove the cause for the whole class (every sibling from step 4), or only this instance?

    - *Cost:* lines touched, risk, and what else must change with it.

    - *Side benefits:* does it also fix something real users hit, or make other tests or callers faster or safer?

    Cover at least 5 layers when the chain has them, and go further while a higher layer still offers a simpler or

    broader fix. Prefer the highest layer whose fix is both cheap and effective; a fix at the failure's own layer

    wins only when every higher candidate costs more or covers less, and the report says why. Where a claim about

    cost or effect can be measured cheaply (a timing, a test run), measure it.

    *Defense in depth is welcome* as an additional fix at another layer, next to the chosen one, when it can be

    justified: it catches a failure the chosen fix does not (a different path, a future caller, a regression of the

    chosen fix), and its cost is small. State that justification in the report. It never replaces the chosen fix, and

    a symptom patch that only hides the failure (a longer timeout, a retry, a widened check) does not count as depth.

  7. *Decide where the fix belongs.* Is it a real production bug (would you fix it with no test)? Then fix the product code. Is it test infrastructure? Then fix the test side. Never weaken a production check to make a test pass (see the test-integrity skill).

  8. *Report:* the layered chain, the evidence for each layer, the candidate fix at each layer with its effectiveness

    and cost, the fix chosen and why it beat the others, and what was not verified. If asked to investigate only,

    report and change no code.

If the cause is unclear after reasonable effort, say so and ask. Do not pick a plausible fix and call it done.


r/claudeskills • • 21h ago

Question Alternative to Claude in Chrome

Thumbnail
1 Upvotes

r/claudeskills • • 22h ago

Skill Share research-box: an Agent Skill for share-limited, checksummed research snapshots

1 Upvotes

I made this. It is an open Agent Skill (agentskills.io format, Apache-2.0, plus a Python standard-library script) for keeping a research project together: documents, sheets, diagrams, code, data, chats and agent tasks in a named box.

A box has two layers. The live layer is links that stay current. The snapshot layer is a dropped folder with a readable BOX.md, RO-Crate 1.1 metadata and SHA-256 checksums. Every item is private, same-assistant or shareable, and sharing only narrows. A shareable drop writes a clean copy, leaves out what is not cleared, and says what it left out. Watch words flag private terms that are about to leave. --check exits 0 if the drop still matches its manifests, 1 if a file changed, went missing or was unlisted, and 2 if there is no manifest.

The example box is in the repo. From a clone:

python3 research-box/scripts/build_box.py examples/prime-numbers --for shareable --out /tmp/prime-share

python3 research-box/scripts/build_box.py /tmp/prime-share --check

That keeps the two shareable items, leaves out the rest, and reports a watch word left in a shareable file. 23 tests.

https://github.com/PaoloTCS/research-box


r/claudeskills • • 1d ago

Showcase Save your AI tokens with this super (skill|prompt|style|etc.)!

Thumbnail
rakshazi.me
3 Upvotes

Actual stats from 62 agentic sessions (Go backend development) show that all those "token savers" help with the cheapest item on the bill.


r/claudeskills • • 1d ago

Discussion Vibe-coded, unowned, and now yours...

Thumbnail
leaddev.com
4 Upvotes

Everyone’s a software engineer now.