r/claudeskills

▲ 881 r/claudeskills+5 crossposts

Hey r/ClaudeCode

I am a software engineering student and I wanted to share a milestone I just hit using Claude as my main pair programmer. My app Caffeine Curfew just crossed 2000 downloads and 600 dollars in revenue.

Since this is a developer community, I wanted to talk about how Claude actually handled the native iOS architecture. The app is a caffeine tracker that calculates metabolic decay, built completely in SwiftUI and relying on SwiftData for local storage.

Where Claude really shined was helping me figure out the complex state management. The absolute biggest headache of this project was getting a seamless three way handshake between the Apple Watch, the iOS Home Screen widgets, and the main app to update instantly. Claude helped me navigate the WidgetKit and SwiftData sync without breaking the native feel or causing memory leaks.

It also helped me wire up direct integrations with Apple Health and Siri so the logging experience is completely frictionless. For any solo devs here building native apps, leaning on Claude for that architectural boilerplate and state management was a massive boost to my shipping speed.

I am an indie dev and the app has zero ads. If anyone is curious about the UI or wants to see how the sync works in production, drop a comment below and I will send you a promo code for a free year of Pro.

I am also happy to answer any questions about how I prompted Claude for the Swift code.

I’m a student with 0 budget, a dream, and a small chance of making it. Any feedback or support truly means the world.

Link:

https://apps.apple.com/us/app/caffeine-curfew/id6757022559

u/pythononrailz — 8 hours ago
▲ 113 r/claudeskills+4 crossposts

Claude Code skill that delegates coding tasks to Mistral Vibe, saves ~2-4x on tokens, with mistral tokens at least 50% cheaper, and avoid hitting usage limits

TLDR; title says it all - use CC to delegate to Mistral vibe, save tokens, costs and avoid hitting limits.

Been using Claude Code for various side projects and kept hitting usage limits (i'm on Pro plan). At the same time i had Mistral Vibe which i did not use much because i appreciate CC's capacity to reason and structure its work.

So I'm sharing a skill that lets Claude Code delegate those tasks to Mistral Vibe while keeping Claude as the orchestrator - benefit from CC thinking and Mistral cheap labor. Vibe natively uses mistral-medium-3.5, inputs 1.5 USD/M tokens, output 7.5/M - to compare with Sonnet's 2x rates. I've observed in my usage i save 2x-4x claude tokens on big tasks.

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

Type /vibe before each instruction.

Claude decomposes the task, writes a self-contained prompt for Vibe, runs vibe-delegate, supervises the streaming output in real time, then checks the git diff before reporting back.

I had to tweak the skill quite a bit to get to a reliable stage because Vibe can have some rough edges - detailed in repo. I can certainly still be improved.

You need Vibe-CLI to use it. https://docs.mistral.ai/mistral-vibe/terminal

EDIT 13/5 : I've seen a few questions regarding this skill applied to other models. Note that Vibe can be configured to use any llm provider/model you want. Yes you can use vibe with deepseek/qwen/etc within. Your model would then access all vibe tools to do what it needs to.

u/pcx_wave — 12 hours ago
▲ 2 r/claudeskills+1 crossposts

I packaged a Claude Code skill to Github that fixes the "go to sleep" nagging

Built a Claude Code skill last night that fixes two things that were bugging me.

Problem: The nagging. "Time to rest, you've earned it." Claude has no idea what my energy state is and I hate it when it interrupts work to tell me to sleep at noon LOL

Solution: This skill instructs Claude to ask you if you are ready for a break or if you want to keep going. It's nice to have the check in but this keeps the interaction a conversation instead of a command from Claude.

Problem 2: I'm legit addicted to Claude Code and I really do need to take a break but I don't want to stop making progress.

Solution: This skill pairs the ask with suggestions of what tasks it could knock out while you're away so it can keep working. Tasks suggested tend to be ones that require few permissions and will take a long time to execute. Further, it front-loads permission requests so it's more likely to get the job done without further interaction.

Skill repo + permission cheat-sheet: https://github.com/TheTalentCat/sleep-solution.git

PRs welcome on the cheat-sheet especially since it gets more useful the more edge cases it covers.

reddit.com
u/ScriptureSlayer — 19 hours ago
▲ 27 r/claudeskills+14 crossposts

Ask questions across your Markdown notes using a fully local Graph RAG engine. Built for Obsidian vaults, works with any folder of Markdown files. Extracts entity-relation triples from wikilinks & YAML frontmatter, retrieves answers via hybrid search (vector + BM25 + temporal). Multilingual. No cloud. Runs on Ollama.

https://github.com/benmaster82/Kwipu

u/WritHerAI — 1 day ago
▲ 17 r/claudeskills+1 crossposts

I built a skill that cuts Claude's output by up to 70% — without losing any technical accuracy

I got tired of Claude and other agent starting every response with:

“Sure! I’d be happy to help…”

So I built crisp — a terse mode skill that strips filler while keeping technical accuracy intact.

Example:

Without crisp:

>“Sure! I’d be happy to help you with that. The issue you're experiencing is likely caused by a problem in your authentication middleware…”

With crisp:

>“Bug in auth middleware. Token expiry check uses < not <=.”

Same fix. Way fewer words.

The interesting part is that crisp doesn’t compress everything equally.

If the model detects:

  • destructive commands
  • risky operations
  • security warnings
  • irreversible actions

it automatically switches back to full clarity before continuing.

So you don’t end up with something absurd like:

>“DROP TABLE users;”

without context or warnings first.

That “auto-clarity exception” ended up becoming the core design decision.

Benchmarks (real API output tokens, averaged across runs):

  • Haiku 4.5 → 29% fewer tokens
  • Sonnet 4.6 → 70% fewer tokens
  • Opus 4.7 → 61% fewer tokens

Install:

npx skills add shubhamv123/crisp

Or just paste SKILL into any Claude conversation.

Still experimental, but I’d genuinely love feedback from people using Claude Code, local agents, or terminal-heavy workflows.

Repo:
GitHub - crisp

github.com
u/Deady213 — 1 day ago
▲ 0 r/claudeskills+1 crossposts

I built a Claude skill to stop overthinking and cut token usage by ~60–80%

Claude tends to overthink and produce very long responses, especially during coding tasks. With usage limits being a real issue, this was burning through tokens much faster than expected.

While experimenting, I came across the idea of “antigravity-style” task handling - where the goal is faster, more direct, and controlled outputs instead of verbose reasoning.

That got me thinking, so I built a custom Claude skill around this idea.

It:

- Reduces token usage (~60–80%)

- Cuts unnecessary reasoning / overthinking

- Produces cleaner, more structured outputs

Instead of letting Claude freely generate long explanations, this adds constraints and forces it to stay focused and efficient.

I’ve been testing it on coding and explanation tasks, and the difference is pretty noticeable in both speed and token usage.

Still improving it , would love feedback or ideas.

If anyone else is struggling with token limits or unnecessary overthinking, this might help. It responds faster, focuses directly on the task, avoids reading or dumping unnecessary context, and gives more efficient outputs overall.

GitHub: https://github.com/KINGSTAR-OMEGA/claude-token-optimizer

u/KingstarOMEGA — 1 day ago

Built a skill that gives Claude persistent memory of your project — decisions, blockers, what you were doing last session

You know that 15 minutes you spend at the start of every Claude session re-explaining your own project?

I got tired of it and built a fix.

npx second-mind install

Installs a skill into Claude Code. Then:

  • /second-mindinitialize — scans your repo, builds a full knowledge vault
  • /second-mindrestore — next session, Claude opens already briefed. What's working, what's broken, what to do next
  • /second-mindupdate — end of session, auto-documents everything

Vault is plain Markdown, fully Obsidian-compatible. Drops a START-HERE.md newcomer guide, ADR-style decision files, session history, the works.

https://preview.redd.it/i01lovi3ec2h1.png?width=2880&format=png&auto=webp&s=2c703c8cd321e63a035562bbb52498a9006d8141

That graph was auto-generated from my project. Didn't draw a single node.

Free, open source, one command to install.

GitHub: second-mind

reddit.com
u/IN_Lucifer — 1 day ago

Priority-check - for people who suffer from FOMO

I got myself into a loop with Claude where I got excited with every tiny idea I had, and my mind started to feel overheated, with a constant dopamine and anxiety drip from all the different ideas that I suddenly had to log an start working on. I have ADHD as well.

At the same time, I'm a dude with two small kids, none of their grandparents anywhere near, I'm trying to survive in the current software engineering market, and I need to FOCUS on important and high priority stuff.

I created a skill I initially named fomo-check for myself, and it helped me immensely, to ground me with every new idea. I created the skill the morning after I cut 3 hours of my regular sleep time to work on a fantasy novel project. I'm not a writer and never wrote anything aside from t technical articles. You get the gist of it.

Then I got excited about the fomo-check skill itself (we're going meta here) and spend a few days working on it, refining it, tinkering to make it publishable and usable by others.

Then I renamed it to priority-check because it is not just about FOMO.

Well, I think it is quite useful, feel free to try it. I'm certain there are already hundreds of alternatives that achieve the same result, but this one is mine.

https://github.com/milanvrskovy/mvsd-ai-skills

u/Usual-Bet-4824 — 1 day ago

Claude-skills weekly: academic-research and scientific-agent bundles jumping, opcode looks abandoned, one sleeper for NotebookLM users

I run a tracker that snapshots a few thousand AI/ML repos daily — stars, commits, releases. Pulled the May 10 → May 17 window for Claude-skill / Claude-Code repos. Two bundles broke out, one once-popular GUI looks abandoned, and one sleeper most people haven't seen.

**K-Dense-AI/scientific-agent-skills: +2,664 stars in 7 days (+12.9%)**

20,680 → 23,344. A ready-to-use Agent Skills bundle for research, science, engineering, analysis, finance and writing. Last commit May 18. This is the kind of pre-baked skill pack that gets traction with users who don't want to author skills from scratch. Worth a fork before customizing for your own domain.

github.com/K-Dense-AI/scientific-agent-skills

**Imbad0202/academic-research-skills: +2,417 stars in 7 days (+39.7%)**

6,084 → 8,501. A narrower, sharper play than the K-Dense bundle. Workflow is research → write → review → revise → finalize, all as Claude Code skills. The +40% week is the kind of breakout that usually means it landed in a popular dev's video or thread; the value is the workflow shape, not any single skill.

github.com/Imbad0202/academic-research-skills

**winfunc/opcode: looking abandoned**

21,816 stars, only +43 over 7 days, and **216 days since the last commit**. opcode was a popular GUI for Claude Code — custom agents, interactive sessions, background agents. The stars from the original hype are still there but new growth has flattened and there's been no maintenance in 7 months. If you depend on it for a workflow, worth either forking or moving to an actively-maintained alternative. Same pattern shows on `Maciek-roboblog/Claude-Code-Usage-Monitor` (7,991 stars, last commit 301 days ago).

github.com/winfunc/opcode

**Sleeper: joeseesun/qiaomu-anything-to-notebooklm: +1,763 stars (+109%), still under 3.5k**

1,614 → 3,377. Claude Skill that takes WeChat articles, web pages, YouTube, PDF, Markdown or search queries and turns them into NotebookLM-ready inputs — also produces podcast / PPT / mindmap / quiz outputs. Useful niche: people using NotebookLM as a research workspace but tired of manually feeding it sources. Last commit Apr 28 (3 weeks ago) so still under active maintenance.

github.com/joeseesun/qiaomu-anything-to-notebooklm

Data: daily GitHub snapshots, 7-day windows compared to the most recent snapshot at least 7 days prior. Tracker I run at beamforai.com — drop a Claude skill or Claude Code repo in the replies and I'll pull a 30 or 90-day curve.

reddit.com
u/Extra-Feature-8163 — 1 day ago

Created a skill for Claude Code to join meetings with complete project knowledge and skills - agentcall.dev

Built a simple skill to let claude code sessions join online meetings in google meet, teams and zoom.

  • All intelligence of the session of claude code will be available to agent in the call
  • Can show tasks and its states in the UI as bot video
  • Can do actions in parallel while in call with subagents
  • Built in TTS to speak into meetings
  • Built in STT to transcribe meetings (English only now)
  • Can understand if someone is speaking and politely raise hands to ask for chance to speak
  • Can send and receive chat messages
  • Can leave and rejoin meetings if asked
  • Can present using screenshare - only webpages
  • Can share files, webapps or interactive webpages as URLs while in call.

In short, it can be like a small openclaw agent for meetings running inside your claude code session. If you are using claude code cloud, you can invoke it from anywhere.

Take a look at the skill https://github.com/pattern-ai-labs/agentcall/

Looking for any feedback that you have so that we can improve.

Thank you

u/johnkg003 — 1 day ago
▲ 55 r/claudeskills+6 crossposts

GSoC results just came out. Whether you got selected or not, if you're contributing to open source, this might help.

As a mentor and a past contributor, I see the same patterns over and over:

  1. Contributor picks a random issue filed by some user. It never gets reviewed.

  2. Contributor skips CONTRIBUTING.md. PR gets rejected for process, not code.

  3. Contributor uses AI to write the fix. Can't answer a single question during review. PR dies.

  4. Contributor doesn't understand the codebase. Patches the symptom, not the root cause.

I built [OSS-Skills](https://github.com/chiruu12/OSS-Skills) - 8 Claude Code skills that walk you through the contribution process step by step. The key difference: the AI researches, you think.

What it does:

  • Finds unclaimed issues filed by actual maintainers (not random users)

  • Checks if the repo even accepts outside contributions before you waste time

  • Reads CONTRIBUTING.md so you don't skip the thing that gets your PR rejected

  • Walks you through the codebase architecture before you touch anything

  • Teaches you unfamiliar tech using examples from the actual repo (not generic docs)

  • Won't let you submit code until you can explain what it does and why

What it doesn't do:

  • Write your code for you

  • Generate PR descriptions

  • Let you skip understanding the codebase

Every skill has "thinking gates" where you have to explain your understanding before moving forward. The AI gives you hints about where to look, but you have to articulate the answer.

Requires Claude Code and the GitHub CLI.

If you try it, I'd genuinely like to hear what worked and what didn't. Open an issue or drop a comment here.

For GSoC candidates who didn't get selected this round: these skills are specifically designed to help you build the kind of deep project understanding that makes GSoC proposals stand out. Contributing well > contributing fast.

u/Junior_Bake5120 — 3 days ago
▲ 59 r/claudeskills+2 crossposts

If you’re bleeding tokens on data grids, here is a Claude Skill that 10x’d my dev speed and cut my token usage by 85%!

Hello everyone,

Just wanted to share Lytenyte Grid AI Skills. If you use Claude Code for your frontend UI and need a data grid, this will 100% help you save a ton of time and drastically reduce token usage!

Like me, you have probably learned that prompting your way to a data grid that works usually ends in a mess and broken edge cases. There are many good reasons for this, but basically, “that ish gets complex.”

LyteNyte Grid AI Skills is free and open source. It comes with 20 highly detailed reference files that cover virtually every aspect of the data grid, from installation to complex implementations.

If you're unfamiliar with LyteNyte Grid, it’s a 40 KB, lightning-fast, zero-dependency data grid with over 150 features (shameless marketing pitch, apologies!).

Anyways, the reason Skills is so unbelievably effective with LyteNyte Grid is that, unlike other grids, LyteNyte Grid has a declarative API and a 100% stateless, fully prop-driven architecture.

At the risk of getting overly technical, here is why this architecture suddenly makes Claude Code effective at building grid implementations for your app:

  • Native React Context: Claude inherently understands React. LyteNyte is built in React for React (no wrappers), keeping Claude's output pure.
  • No Translation Layers: Because it’s fully prop-driven, Claude doesn't have to guess or write messy mapping code.
  • Simpler Prompts: It relies on familiar React patterns, allowing Claude to hit zero-shot accuracy with much shorter prompts.
  • A11y Built-in: Claude no longer hallucinates custom screen-reader properties or aria-tags to make things work.

Honestly, we have been blown away by the results. I wanted to share this with the community and get your honest feedback. As I said, it’s completely free and open source.

If you find this helpful and like what we’re building, GitHub stars help. Feature suggestions and code contributions are always welcome.

u/Vis_et_Honor — 2 days ago

Update your skills automatically

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

reddit.com
u/pcx_wave — 2 days ago
▲ 10 r/claudeskills+4 crossposts

A completely local TTS for Cursor and Claude Code - hear a short spoken summary after each agent reply (no cloud API) - totally free

I vibe-code with agents a lot and got tired of glancing back at the chat every time a long reply finished. So I made Aftertone: after each agent response, a local Supertonic ONNX voice reads a short line (what landed, blockers, next step) — not the whole wall of text.

What it is

  • Runs on your machine (~/aftertone), MIT, no TTS subscription
  • Cursor and Claude Code work today (Codex / OpenCode on the roadmap)
  • Per-chat on/off (/aftertone-on in Cursor, /aftertone_on in Claude)
  • Agents use a <spoken_summary> tag at the end of replies; if there is no tag, it stays quiet (tag-only mode by default)

Install (Linux/macOS):

curl -fsSL https://raw.githubusercontent.com/omarelkhal/aftertone/main/scripts/install.sh | bash -s -- --install-uv --start-daemon

Then in Cursor: Hooks on + trusted workspace. In Claude: /aftertone_on in the chats where you want audio.

Repo / docs: https://github.com/omarelkhal/aftertone

Happy to answer setup questions. If you try it, I would love to know whether the spoken summaries actually help your flow or feel like noise.

u/elkhalomar — 2 days ago
▲ 6 r/claudeskills+1 crossposts

Centralize SKILLs

We recently tried to roll out an AI agent workflow across a 60-person company, and we found out

  1. need to centralize the SKILLs files

  2. update, versioning markdown file supporting multi users is a challenge

Does Claude enterprise version offer any solution? or there are any open source project helping company to manage skills ?

Since these are just text files, we could hack together a workaround using SharePoint to distribute them internally. But are there any actual purpose-built tools for this?

reddit.com
u/Antony_Ma — 3 days ago

I built skill-router so you don't have to remember which of your 47 skills does what

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

reddit.com
u/pcx_wave — 3 days ago

I built a Claude Code skill that generates better CLAUDE.md by best practices + scanning your repo + asking you 6 questions

Been annoyed at how inconsistent CLAUDE.md files are — some are bloated essays,

some are basically empty. So I made a skill that does it properly.

Here's what it does:

  1. Scans your repo autonomously — reads manifests, detects your stack, checks

    linter configs, looks at git history for commit conventions

  2. Asks you exactly 6 questions — the stuff only you can answer (gotchas,

    what's out of scope, approval gates, external Confluence/Notion links)

  3. Generates a file under 80 lines where every line prevents a real mistake

The 80-line cap is a hard constraint, not a suggestion. Bloated CLAUDE.md files

cause the harness to down-weight ALL instructions uniformly — including the

important ones. So the skill will split overflow into agent_docs/ auxiliary files

rather than let the root file balloon.

It also refuses to add things like:

- Style rules your linter already enforces

- "Be a senior engineer" personality prompts (zero effect)

- Pasted Confluence content (CLAUDE.md is not a cache)

Works with Claude Code and Codex CLI.

GitHub: https://github.com/sruthik27/creating-claude-md

Would love feedback — especially if you've tried it on a monorepo or a repo

with Confluence docs linked.

u/Dark_king_27 — 4 days ago

I open-sourced the 15 Claude Code skills I used for +100 projects in freelance

I have been using Claude Code in production for several months. We’ve developed a “/” command chain that has allowed us to move from “Claude writes code that works” to “Claude generates tickets that don’t require three follow-up requests for clarification.”

We’ve just open-sourced them: https://github.com/MisTraleuh/my-claude-skills

The main command is /do. A single command executes a 5-step pipeline: /todo → /dev → /verify-dev → /build → /test → /push

Each step has its own feedback loop (limited to 3 cycles per phase).

Does /verify-dev detect a logical flaw? It automatically creates -fix-N tickets, sends them back to /dev, then verifies again. Same process for compilation errors and failed functional tests. Green report or clear failure status: never a half-failed push.

On our production tickets, we’ve seen about 80% fewer follow-up requests and, most importantly, 60-65% better quality than with the base Claude Code ("Claude forgot to handle X", "this breaks the authentication flow", etc.) and review cycles cut in half

(These aren’t bogus stats... they’re facts based on over 2,000 commits)

Wondering what skills are missing from your daily workflow with Claude Code? Let me give you a few ideas

u/__Asile34__ — 3 days ago