r/claudeskills • • Jun 10 '26 Regret

Dude blew up on github for cutting token usage 60-95% right as Fable 5 lands. genius or luckiest man alive

Post image
2.7k Upvotes

Ok I keep seeing this repo everywhere and the timing is kind of hilarious.

It's called headroom. some dev (chopratejas) has been grinding on it for months. it's basically a compression layer that sits between your agent and the LLM and squeezes everything before it hits the model. tool outputs, logs, RAG chunks, whole files, conversation history. claims 60 to 95% fewer tokens with the same answers.

then Fable 5 ships. more capable, even hungrier for context. so everyone immediately wants to cram more into the window and the bill goes brrr. and this guy's tool has just been sitting there ready the whole time. man basically pre-built the cure and waited for the disease lol.

stars went vertical. couldn't have scripted it better.

not affiliated, just impressed someone shipped the right thing at the exact right moment. source : https://www.beamforai.com/tools/chopratejas/headroom

anyone run this in prod yet? curious if the savings hold up outside their benchmarks.


r/claudeskills • • Aug 29 '26 Bravo Heartwarming

Skill Share I turned 25+ years of corporate experience into an open-source “org in a box” for Claude

Post image
2.2k Upvotes

I’ve spent more than 25 years working inside corporate organizations, primarily in technology and leadership roles. Recently, I started turning some of the processes, frameworks, and lessons I’ve picked up into an open-source Claude skill set.

The idea is basically an “org in a box.” It’s meant to help Claude reason through things like organizational structure, roles and responsibilities, headcount planning, hiring, performance, compensation, succession, workforce risk, and the other moving parts involved in building and running a company.

I also built a dynamic HTML org chart so you can explore the structure visually instead of trying to decipher a spreadsheet or static diagram:

https://cbrock84.github.io/headcount/

The full project is MIT licensed and available here:

https://github.com/cbrock84/headcount

There’s no product or service behind this, and I’m not trying to sell anything. I built it for my own use and figured it might be helpful to other people dealing with organizational planning or leadership work.

It’s still evolving, so I’d genuinely appreciate feedback from anyone willing to try it. I’d especially like to hear what’s useful, what’s confusing, what’s missing, and where the output doesn’t reflect how organizations actually work in practice.


r/claudeskills • • 25d ago Bravo Mindblown

Skill Share How to make a scroll-driven ink painting website with sn-motion-html

2.0k Upvotes

It's a five-chapter journey through Shanghai, from a water town at dawn to the Pudong skyline at night and here's a compact workflow for recreating this kind of page.

  1. Give Claude a specific sequence

For this demo, the visual route is:

Zhujiajiao → Wukang Mansion → Yuyuan Garden → the Bund → Lujiazui.

Each chapter has one main composition: a stone bridge and boat, the wedge-shaped mansion beneath plane trees, a garden framed by a moon gate, waterfront buildings at dusk, and finally the towers across the river.

Ask for a storyboard with the subject, camera movement, text position, and transition into the next chapter.

2. Establish the painting style before animating

Make a few sample stills first. For this look, specify warm paper texture, gray-green ink washes, soft architectural edges, mist, and restrained color.

Keep that treatment consistent as the lighting changes. The Bund introduces gold reflections and a darker sky; the final skyline still needs to belong to the same painting.

Approve the visual samples and shot plan before generating the full set.

3. Describe the connecting shots

The transitions deserve their own prompts. In the recording, the camera rises past trees, moves through the garden composition, and crosses mist over the river.

A concrete instruction could be:

Move forward past the moon gate and across the garden pond. Let mist fill the frame, then reveal the Bund across the water. Keep the movement slow and preserve the ink-wash texture.

The skill's workflow generates scene clips first, then uses their actual boundary frames to build the connectors.

4. Place the text around the landmarks

Watch how the layout changes: text sits left of the water-town scene, right of Wukang Mansion and the Bund, and across the lower part of the final skyline.

Keep the text in HTML, leave the artwork visible beneath it, and fade the body copy out during transitions. Use one fixed full-screen stage with scroll progress controlling the media timeline.

A starting prompt:

Use sn-motion-html to build a five-chapter Shanghai ink-wash story. 

Route: Zhujiajiao at dawn, Wukang Mansion, Yuyuan Garden, the Bund at dusk, and Lujiazui at night. 

Use textured paper, gray-green ink, mist, serif typography, 
and small red seal-style chapter markers. 

Plan a continuous camera route between scenes.
Place text in each composition's empty space. 

First show me sample stills and a storyboard. Wait for approval before full production, and confirm the cost before paid video generation. 

Before sharing, check forward/backward scrolling, chapter jumps, and mobile cropping.

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

Brief about the skills: https://github.com/OpenSenseNova/SenseNova-Skills/blob/main/docs/sn-motion-html.md

You'll need image-generation access, a Seedance API account, Python, and FFmpeg


r/claudeskills • • 10d ago

Skill Share Claude quoted 50 days, subagents did it in 35h, and the slow part was me

Post image
1.2k Upvotes

My coworker and I asked Claude to estimate a SaaS roadmap. 50 days.

Then we gave the same plan to 6 Claude Code subagents: worktrees, tests first, reviewer agents on risky tasks. 106 tasks across 7 repos, done in 35 hours.

So yes, Claude was off by about 48 days about its own speed. But the interesting part is what slowed it down, because it wasn't the model:

- 6 agents ≠ 6× speed. Real throughput was 1.8 agents. Test slots, file conflicts and merge locks queued everything.

- Risk matters more than size. Billing/auth/migration tasks took 2.7× longer, and every real bug was in them.

- My laptop broke first. 55 leftover test DBs filled the disk, Docker froze, test runs blew past the 10-min tool timeout.

- The slowest part was us: review, decisions, local setup.

We turned the data into a plugin that makes Claude estimate agent work properly: agent wall-clock, human hours and waiting time, separately, plus usage budget.

Honest limits: it's one project (n = 1), and on a held-out test the raw model was 37% optimistic, so it pads its number until you calibrate it on your own transcripts.

Free and open source (MIT): https://github.com/MedAdemBHA/mythical-agent-month

Question for people running multi-agent builds: what real parallelism are you getting? I'd love a second data point.


r/claudeskills • • Aug 28 '26

Skill Share I Built Myself a Personal AI “CEO Office” to Run Different Parts of My Business

Post image
981 Upvotes

I’ve been experimenting with AI beyond just using it as a chatbot, and recently built a personalised CEO-style interface for my business using Claude.

The idea was simple: instead of having one generic AI conversation for everything, I wanted a central workspace where different AI “department heads” could handle specific areas of the business.

The current setup has 7 specialised departments:

  • 📣 Marketing

  • 📱 Social Media

  • 🎨 Design

  • 💰 Finance

  • ⚖️ Legal

  • 🏢 Operations

  • 💻 Engineering

Each department has its own context and purpose, so depending on what I need, I can go directly to that specific AI workspace instead of repeatedly explaining the background or switching between unrelated chats.

For example, I can use the Marketing department for campaign ideas and positioning, Social Media for content strategy, Design for creative direction, and so on.

The interface is designed like a small internal company dashboard, with me positioned as the central point of control and each AI department acting as a specialised resource when needed.

This is still very much an experiment and a work in progress, but I find this approach much more interesting than treating AI as just one all-purpose assistant. The bigger goal is to create a personalised AI operating system that actually adapts to the way I run my business.

Would love to hear what you think—have you built something similar, or how would you structure your own AI-powered team?


r/claudeskills • • Sep 24 '26 Bravo

Skill Share A free claude skill to de-ai your written content

920 Upvotes
---
name: de-ai-writing
description: Rewrite text so it has no signs of AI writing, using Wikipedia's "Signs of AI writing" field guide (em-dash overuse, "not just X, it's Y", "serves as", "delve/crucial/pivotal/tapestry", puffed-up significance, promotional tone, vague attributions, "it's important to note", "In conclusion", Title Case headings, bold-label bullet lists, chatbot leftovers). Use this whenever someone wants content de-AI'd, humanised, made to "sound less like ChatGPT/AI", "less robotic", cleaned of AI tells, or checked for signs of AI writing before publishing, including blog posts, web copy, FAQs, emails, essays, LinkedIn posts, product pages, docs and whole websites or repos of content. Also use it when polishing a draft the user says came from an AI.
---

# De-AI writing

Rewrite content so it reads as written by a knowledgeable person, by removing the patterns catalogued
in Wikipedia's *Signs of AI writing* (WikiProject AI Cleanup). The full catalogue, with words to
watch and a before/after fix for each sign, is in `references/signs.md`. Read it before the first
rewrite in a session; it is the source of truth for what counts as a sign.

## Why this works the way it does

The Wikipedia guide makes a point worth holding on to: the signs are symptoms. Language models
regress to the most statistically common phrasing, so specific facts get smoothed into generic,
important-sounding statements. Swapping a flagged word for a synonym, or an em dash for an en dash,
hides the symptom and keeps the problem. The aim is text that says specific things plainly. When you
fix a sentence, fix what it is doing (puffing up, hedging, correcting a misconception nobody raised),
not just the word that tripped the scanner.

## Workflow

1. **Get the text.** Pasted text, a file, a folder of files, or a built website. For a codebase or
   site, find where the copy actually lives (data files, CMS exports, templates) and edit there, not
   in generated output.

2. **Scan it.** If you can run code, use the bundled scanner for a baseline:
   ```bash
   python3 scripts/check_ai_signs.py <file(s)>      # .txt, .md or .html; "-" reads stdin
   python3 scripts/check_ai_signs.py <file> --summary
   ```
   It reports each matching sentence under its sign number. It catches pattern-matchable signs only.
   Rule of three, elegant variation, puffed-up structure and summary endings need your own read.
   Without code execution, do the same pass by hand using `references/signs.md`.

3. **Rewrite.** Go sentence by sentence through everything flagged, then read the whole piece once
   more for the judgement signs. Rules for the rewrite:
   - **Keep every fact, number, name, date, link and claim.** De-AI'ing changes how things are said,
     never what is said. If a sentence was only padding, delete it; if it carried a fact, keep the fact.
   - **Keep the author's voice and conventions**: person (I/we/you), spelling (UK/US), tone,
     formatting system (Markdown, HTML, JSX, plain text), and any length limits (SEO titles ~60
     characters, meta descriptions ~155, button labels).
   - **Never alter quotations** of real people or sources, titles of works, or legal text.
   - **Em dashes**: rewrite with commas, colons, parentheses or full stops. Don't substitute another
     dash. One or two in a long piece is fine.
   - **Contrasts** ("not X but Y", "rather than", "not just… it's"): state the positive claim on its
     own unless a reader genuinely would assume the opposite.
   - **Unknowns**: if the original says something isn't known, keep that honesty, but say it once,
     concretely, with what the reader should do ("Hours aren't posted; call ahead"). Don't pad it
     with speculation.
   - **Plain words**: is/has instead of serves as/boasts; used, tried, moved, to, before.
   - **Don't over-correct.** Perfect grammar, formal register, a single transition word or an
     unsourced claim are *not* signs (see section 7 of the reference). Leave clean sentences alone.

4. **Re-scan and re-read.** Run the scanner again and aim for zero hits. A hit you keep on purpose
   (a quotation, a proper noun like "Key Largo", a word used literally, such as "landscape" for a
   painting) is fine; note it in your report.

5. **Report briefly.** Give the rewritten text (or confirm files were edited), then a short note:
   sign counts before → after, two or three representative before/after examples, and anything
   left in deliberately. Keep the note short; the rewrite is the deliverable.

## Quick reference

The signs, in brief (details and fixes in `references/signs.md`):

| # | Sign | Typical tells |
|---|------|---------------|
| 1.1 | Undue significance / legacy | stands as, testament, pivotal role, reflects broader, enduring legacy |
| 1.2 | Canned notability | featured in, independent coverage, active social media presence |
| 1.3 | Superficial -ing analysis | "…, highlighting/ensuring/reflecting…", valuable insights |
| 1.4 | Promotional tone | vibrant, nestled, in the heart of, boasts, world-class, seamless |
| 1.5 | Vague attribution | experts say, observers note, studies show, widely regarded |
| 1.6 | Challenges formula | "Despite its…, faces challenges… Despite these challenges…" |
| 1.7 | Title-defining lead | "X refers to…" |
| 2.1 | AI vocabulary | additionally, crucial, delve, enhance, foster, key, landscape, robust, tapestry |
| 2.2 | Copula avoidance | serves as, functions as, represents, features/offers (for "has") |
| 2.3 | Vague association | associated with, in connection with |
| 2.4 | Negative parallelism | not only…but, it's not X it's Y, no X no Y just Z, rather than |
| 2.5 | Rule of three | stacked triplets used for rhythm |
| 2.6 | Elegant variation | synonym cycling for one noun |
| 3.1–3.8 | Formatting | Title Case headings, bold everywhere, **Label:** bullets, em dashes, emoji, tiny tables, mixed curly quotes, --- between sections |
| 4.1–4.3 | Chat leftovers | I hope this helps, let me know, "not widely documented", [Your Name] |
| 5.1–5.2 | Older habits | it's important to note, may vary, In conclusion, Overall |

## Example

**Input**
> Nestled in the heart of the city, our café stands as a testament to the town's rich cultural
> heritage — it's not just a coffee shop, it's a gathering place. Additionally, the menu boasts a
> diverse array of pastries, showcasing our commitment to quality. While specific details about
> opening hours are not widely documented, it's important to note that hours may vary.

**Output**
> Our café is on the main square, in a building that has been a bakery since 1911. People come for
> the coffee and stay for hours. We bake about twenty kinds of pastry each morning. Opening hours
> change with the seasons, so check our Instagram before you visit.

(The details "1911", "twenty kinds" and "Instagram" would come from the user. If the facts aren't
available, ask, or write the plain version without them: "Our café is on the main square. We bake
pastries every morning. Hours change with the seasons, so check before you visit." Never invent
facts to replace puffery.)

Signs.MD 

Signs of AI writing: full catalogue and fixes
Source: Wikipedia, Signs of AI writing (WikiProject AI Cleanup), September 2026 edition. The guide is a field guide for spotting machine-written text. Here it is turned around: each sign comes with what it looks like, the words to watch, and how a human writer would fix it. Signs that only apply to Wikipedia markup (wikitext, citation templates, categories, edit summaries) are left out.

The numbering matches scripts/check_ai_signs.py.

Contents
Content signs (1.1–1.8)
Language and grammar (2.1–2.6)
Style and formatting (3.1–3.8)
Text meant for the chat user (4.1–4.3)
Older-model habits (5.1–5.2)
What human writing does instead
Not signs: don't "fix" these
1. Content
1.1 Undue emphasis on significance, legacy and broader trends
Ordinary facts get a sentence about why they matter, how they "reflect broader" trends, or their "enduring legacy". Even mundane subjects (a railway station, a fish species) get puffed up.

Words to watch: stands/serves as, is a testament/reminder, a crucial/pivotal/vital/significant/key role or moment, underscores/highlights its importance, reflects broader, symbolising its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted, "has generated debate about…", "prompted broader reflection on…".

Fix: delete the significance sentence, or replace it with a specific fact that shows the point.

Before: "The institute was established in 1989, marking a pivotal moment in the evolution of regional statistics." After: "The institute was set up in 1989. It was Spain's first regional statistics office."

1.2 Canned emphasis on notability and media coverage
Proving importance by listing where something was covered, or describing the sources themselves.

Words to watch: independent coverage, local/national media outlets, trade publications, cited/featured/profiled in, written by a leading expert, maintains an active social media presence.

Fix: say what the thing is or did. Cite coverage only as a source for a specific claim.

1.3 Superficial analysis
A participle clause tacked onto the end of a factual sentence that interprets it without adding information: "…, highlighting its importance", "…, ensuring…", "…, reflecting…".

Words to watch: highlighting, underscoring, emphasising, ensuring, reflecting, symbolising, contributing to, cultivating, fostering, encompassing, enhancing, showcasing, valuable insights, align/resonate with.

Fix: cut the clause. If the interpretation matters, make it its own sentence with evidence.

Before: "The station has 8 tracks and 6 platforms, reflecting its continued relevance in the regional transportation landscape." After: "The station has 8 tracks and 6 platforms."

1.4 Promotional, advert or travel-brochure language
Neutral subjects written up like a hotel listing or a press release.

Words to watch: boasts a, vibrant, rich (culture/heritage/history), profound, enhancing, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking, renowned, featuring, diverse array, breathtaking, stunning, world-class, seamless, state-of-the-art.

Fix: replace the adjective with the fact that would earn it, or drop it.

Before: "Nestled in the heart of the old town, the café boasts a diverse array of pastries." After: "The café is on the main square and sells about twenty kinds of pastry."

1.5 Vague attributions and overgeneralised opinions
Opinions hung on unnamed authorities, or one source presented as many.

Words to watch: industry reports, observers have cited, experts argue, some critics argue, several sources (when there are one or two), studies show, widely regarded, "such as" before what is actually a complete list.

Fix: name the source, or state the claim as your own view, or cut it.

1.6 Formulaic "challenges and future prospects" endings
"Despite its [praise], X faces several challenges… Despite these challenges, X continues to thrive…", often in a closing "Challenges" or "Future outlook" section.

Fix: if a problem is real, state it plainly where it belongs. Drop the optimistic wrap-up.

1.7 Leads that define the title as a thing
"X refers to…" or "The List of Y is a curated compilation of…" for topics or lists.

Fix: start with the subject itself. "A catchment area is the area a hospital draws patients from."

1.8 "X and Y" headings, "Awards and recognition"
Paired headings built to sound complete. Keep a heading only if the section needs it.

2. Language and grammar
2.1 High density of "AI vocabulary"
One or two of these is normal. Several in one piece of text is one of the strongest tells.

2023–mid-2024 set: additionally (especially opening a sentence), boasts, bolstered, crucial, delve, emphasising, enduring, garner, intricate/intricacies, interplay, key (adjective), landscape (abstract), meticulous, pivotal, underscore, tapestry, testament, valuable, vibrant. Mid-2024–2025 set: align with, bolstered, crucial, emphasising, enhance, enduring, fostering, highlighting, pivotal, showcasing, underscore, vibrant. Newer models: emphasising, enhance, highlighting, showcasing.

Fix: use the ordinary word or cut. "Additionally" → start the sentence without it, or "Also". "Crucial" → "important", or explain why. "Landscape" → name the actual thing. Don't just swap in a synonym: the guide warns that the word is a symptom; the padding is the problem.

2.2 Avoiding "is", "are" and "has"
Dressing up a plain verb.

Words to watch: serves as, stands as, marks, functions as, operates as, represents, boasts / features / maintains / offers (meaning "has"), refers to, "ventured into politics as a candidate" (was a candidate), "began his career as" (was).

Fix: use is/are/has. "Gallery 825 serves as LAAA's exhibition space. The gallery features four separate spaces" → "Gallery 825 is LAAA's exhibition space. It has four galleries."

2.3 Vague connection or association
"was associated with leadership of", "in connection with", "connected to" where a plain relationship is known. Fix: state the relationship. "In 2017 she was CEO of ExampleCorp."

2.4 Negative parallelisms
Correcting a misconception nobody raised.

"Not only … but also …", "It's not just X, it's Y", "This isn't A, it's B"
"Not X, but Y", "X is not a mirror but a portal"
"No X, no Y, just Z"
"Y rather than X" (overused; fine occasionally)
Fix: state the positive claim alone. "It's not just a coffee shop, it's a gathering place" → "People stay for hours." Keep a contrast only when a reader really would assume the opposite.

2.5 Rule of three
Triplets of adjectives or short phrases used to sound thorough: "fast, reliable, and secure"; "learn, connect, and grow". Fix: keep lists that are really lists of facts; otherwise pick the one item that matters, or two. Vary rhythm.

2.6 Elegant variation
Cycling through synonyms to avoid repeating a noun ("the artist… the painter… the creative… the visionary"). Fix: repeat the plain noun, or use a pronoun.

3. Style and formatting
3.1 Title Case headings
"Impact Of Technology And Digitalization". Fix: sentence case, unless house style says otherwise.

3.2 Overuse of boldface
Bolding key phrases throughout, "key takeaways" style. Fix: bold nothing in body prose, or at most a term at its definition.

3.3 Inline-header vertical lists
Bullets that start with a bold label and a colon: "Scalability: The system…". Fix: turn into prose, or a plain list without labels, or a real table if the data is tabular.

3.4 Overuse of em dashes
LLMs use em dashes where people use commas, colons, parentheses or full stops, often spaced " — " for punch. Claude in particular uses more than professional writers do. Fix: rewrite the sentence with ordinary punctuation. Don't swap in an en dash or hyphen; that keeps the pattern. One or two in a long piece is fine.

3.5 Emoji as formatting
Emoji in front of headings or bullets. Fix: remove.

3.6 Unusual small tables
Two- or three-row tables that would read better as one sentence.

3.7 Curly quotes and apostrophes
Mixed curly (“ ” ’) and straight quotes. Match the surrounding text's convention. (Word processors also produce curly quotes, so this alone proves nothing.)

3.8 Thematic breaks between every section
--- between every section. Remove unless the format needs them.

4. Text meant for the chat user
4.1 Collaborative communication left in
"I hope this helps", "Certainly!", "Great question", "Let me know if…", "Would you like me to…", "Here is a…", "In this section, we will discuss…". Fix: delete.

4.2 Knowledge-cutoff disclaimers and speculation about gaps
"As of my last update…", "While specific details are limited…", "not widely documented/disclosed", "based on available information", "maintains a low profile", followed by guesses about what the missing information "likely" is. Fix: if something genuinely is unknown, say so once, concretely, and tell the reader what to do: "Opening hours aren't posted; call ahead." Never pad the gap with speculation.

4.3 Placeholders
"[Your Name]", "[Describe the section]", "INSERT_URL", "2025-XX-XX". Fix: fill in or remove.

5. Older-model habits (still worth avoiding)
5.1 Didactic disclaimers
"It's important to note/remember/consider", "It is worth noting", "may vary", "keep in mind". Fix: state the thing. "Hours may vary" → "Hours change in winter."

5.2 Section summaries
Paragraphs that end by restating themselves; openers like "In summary", "In conclusion", "Overall", "Ultimately". Fix: end on the last new fact.

6. What human writing does instead
From the guide's "Signs of human writing":

Plain is/has sentences: "there is a", "it has a".
Plain words: wrote (not authored), moved (not relocated), used (not utilised), tried (not attempted), died (not passed away), before (not prior to), to (not in order to).
Definite statements where true: "is the only", "was the first", "one of the best".
Ordinary hedges and intensifiers: "very", "perhaps", "tends to".
Specific, unusual facts. AI text regresses to the generic ("a revolutionary titan of industry"); human text keeps the odd detail ("inventor of the first train-coupling device").
7. Not signs: don't "fix" these
The guide lists these as ineffective indicators. Changing them wastes effort and can make text worse:

Perfect grammar.
Mixing casual and formal registers.
"Bland" or formal prose in general, or long words in general.
A single transition word on its own.
Unsourced content.
Correct formatting. Quoted material (a real person's words, a title, a source) is never rewritten to remove signs.

r/claudeskills • • Jul 30 '26

Skill Share I made a skill that has Claude Code direct a whole Vox-style explainer video

864 Upvotes

I make short explainer videos, and the look I keep coming back to is the Vox paper-collage style, hand-cut paper, torn edges, halftone dots, big cut-out headlines. Doing it by hand is a full day: script, a poster per beat, animate each one, voice over, music that does not fight the narration, then the edit with captions. I basically wanted Claude Code to run that whole pipeline for me, so I built it as a skill.

Now I give it one line, like "the history of money, 60 seconds, English". Claude drafts a beat map and stops for me to approve it, runs a quick style bake-off so I pick the look by eye, then generates the collage keyframes, animates them, adds a narrator and music, and assembles the final mp4 with captions burned in. Generation goes through the Atlas Cloud API and the edit is local ffmpeg, so it never leaves the terminal.

It takes three kinds of input: a topic and it builds the whole video, a talking-head clip and it restyles that into collage while keeping the real face and lip sync, or one photo and it cuts the subject out as a paper sticker and builds each poster around it.

Install is a one-liner:

git clone https://github.com/Alisa0808/vox-director.git ~/.claude/skills/vox-director

Set your Atlas Cloud API key and ask. It is open source (MIT license), PRs welcome, and there are finished examples in the repo (a 30 second one on Chinese civilization, plus football, street food, and money). Repo: https://github.com/Alisa0808/vox-director

The bit I like most is the two approval gates. Claude does not run off and burn a hundred generations, it stops for me to sign off on the beats and the look first, so I stay the director instead of babysitting a slot machine.


r/claudeskills • • Aug 26 '26

Skill Share Top Agent Skills Repositories

Post image
779 Upvotes
  1. anthropics/skills (171.6k stars)

  2. obra/superpowers (277.7k stars)

  3. multica-ai/andrej-karpathy-skills (207.4k stars)

  4. mattpocock/skills (237.1k stars)

  5. nextlevelbuilder/ui-ux-pro-max-skill (121.0k stars)

  6. JuliusBrussee/caveman (101.0k stars)

  7. addyosmani/agent-skills (89.8k stars)

  8. Leonxlnx/taste-skill (80.7k stars)

  9. ComposioHQ/awesome-claude-skills (73.3k stars)

  10. ayghri/i-have-adhd (24.4k stars)


r/claudeskills • • 13d ago

Skill Share 9 Claude skills for motion design & animation

Post image
654 Upvotes

r/claudeskills • • Jul 09 '26

Skill Share Before Fable 5 gets deprecated, I had it write down how it thinks. We tested it until it broke. It's now a plugin, evals included.

Post image
607 Upvotes

Like a lot of you, I don't know if Fable will still be in my subscription tomorrow. So I spent its last sessions on something different: I had it distil its own problem-solving approach into skills any model can run, and then we tested that distillation adversarially instead of trusting it.

The honest journey: v1 of the method failed its own trap test (0/4). v2 failed too (1/4). v3 passed (4/4). Every failure is committed in the repo as raw judge transcripts, including the null results where the method did nothing.

What it is. three skills. fable-method (a problem-solving loop with hard thresholds), fable-loop (runs whole tasks with adversarial verification agents), fable-judge (treats any "done, all tests pass" as claims and re-runs everything itself).

What ~180 test runs showed: Haiku went 0/4 to 4/4 on catching a wrong test before "fixing" correct code. Sonnet + method matched Fable itself 10/10 on a five-part research task. The judge took Haiku from 3/5 to 5/5 on catching planted frauds in a lying completion report.

What it won't do, honestly: on ordinary tasks with capable models, it adds nothing. We measured that too, and the README says so. The value concentrates at traps: wrong tests, false completion claims, weak models, unattended runs. It supplies discipline, not knowledge.

One more thing that felt right: the flowcharts of the method weren't written from Fable's self-description. We spawned bare Fable agents, recorded every tool call, and corrected the method where its self-description disagreed with its actual observed behavior. Observation won three times.

Install: /plugin marketplace add Sahir619/fable-method then /plugin install fable@fable-method

Repo (MIT, all eval transcripts committed): https://github.com/Sahir619/fable-method

If you want to contribute, the repo has one law: no rule ships without a failing test first. I'd genuinely love people to try to break it.

Edit: New post about new version - https://www.reddit.com/r/claudeskills/s/vbN1EQuPli


r/claudeskills • • Sep 19 '26

Skill Share after 2+ years using Claude professionally this is the skill i use the most (by far)

Thumbnail
github.com
597 Upvotes

Every time i post this as a comment gets crazy upvotes. which is awesome but it's so simple it suprises me.

The problem: i was tired of reading, more that tired tbh. it was exhausting. Code reviews, Opus 5, even fable and the other models. It was just too much

The solution: make faster summaries a) in chat b) in html files

Quick win:

"ELI5 succinct" thinking mode: low

... is the simplest and best thing you can do rn. Idk why it work so well, but it does and i hope it does for you too

Here's the others as a skill you can copy, adapt or use directly

Edit: the repo is now split into two main skills 1. ELI5-succinct - in chat summary 2. summary - html summaries with routing for simple, accessible or artistic styles


r/claudeskills • • 4d ago Bravo

Skill Share Sketchy: a skill that lets Claude draw anything while it explains, not just boxes and arrows anymore (free, open source)

578 Upvotes

Last week I shared Sketchy, the skill that lets Claude explain with hand-drawn, interactive diagrams instead of walls of text. You all asked if it can draw more than flowcharts. Now it can!

- Ask "what's in my coffee?" → the actual caffeine molecule
- "Berlin to Paris by train?" → a map with the route
- "Explain Pythagoras" → the triangle with angles and measurements
- Timelines, cycles, mind maps, Venn diagrams, ready to go

What makes it work: Claude never draws coordinates itself. It just says what should be in the picture, and Sketchy handles the layout. So no overlapping boxes, no broken SVG, and you can click through every drawing step by step.

Free, open source, works in the phone app too. Upload the zip once and just ask questions.

https://github.com/ddkbs/sketchy & https://sketchy.davidkubus.dev

Feel free to try it out and leave your feedback!


r/claudeskills • • Aug 27 '26 Heartwarming

Skill Share my agent skills stack in 2026, actually copy-pasteable

Post image
557 Upvotes

I've seen a bunch of "must-have agent skills" lists lately. Half of them link to dead repos, outdated skills, or commands that don't work anymore.

So here's the stack I'm actually using.

I went through the repos and install paths before putting this together

engineering

catches bugs before your code gets merged

npx skills add addyosmani/agent-skills --skill code-review-and-quality

Runs a structured review across correctness, readability, architecture, security and performance

tells you where your eval setup is actually failing

npx skills add https://github.com/ai-evals-course/evals-skills

Audits an existing eval pipeline, helps discover failure modes from traces and gives you workflows for building better product-specific evals.

builds MCP servers without starting from a blank repo

npx skills add https://github.com/anthropics/skills --skill mcp-builder

Guides the agent through building MCP servers and the surrounding implementation work.

fixes the prompt before you start rewriting the code

npx skills add CodeAlive-AI/ai-driven-development --skill prompt-engineering -g -y

Helps diagnose prompting problems, choose the right prompting technique and avoid common failure modes like hallucinations, bad structure and security mistakes.

stops the agent from "fixing" five files when you asked about one

/plugin marketplace add obra/superpowers-marketplace
/plugin install superpowers@superpowers-marketplace

Adds a more disciplined development workflow with planning, TDD, debugging and task-execution patterns.

tests the app in a real browser instead of guessing from the code

npx skills add https://github.com/anthropics/skills --skill webapp-testing

Uses Playwright to interact with local web apps, verify frontend behavior, capture screenshots and inspect browser logs.

design

makes static graphics that don't look like AI-generated templates

npx skills add https://github.com/anthropics/skills --skill canvas-design

Turns a design brief into original PNG/PDF artwork with a deliberate visual direction, composition, typography and spacing.

stops every UI from looking like the same AI-generated SaaS

npx skills add https://github.com/anthropics/skills --skill frontend-design

Pushes the agent toward production-quality frontend design instead of generic layouts and default-looking components.

comms

gives your agent its own email inbox

npx --package=@atomicmail/agent-skill-github atomicmail register --username "myagent" --watch scheduled

Lets an agent read, send and react to email autonomously instead of stopping every time something hits the inbox.

turns "write a status update" into something you can actually send

npx skills add https://github.com/anthropics/skills --skill internal-comms

Covers status reports, leadership updates, project updates, incident reports, FAQs, newsletters and other internal communication formats.

memory

lets your agent actually work with an Obsidian vault

npx skills add https://github.com/kepano/obsidian-skills

Adds Obsidian-specific knowledge for Markdown, Bases, JSON Canvas, CLI workflows and other vault operations.

keeps the plan alive after /clear

npx skills add OthmanAdi/planning-with-files --skill planning-with-files

Stores the plan, findings and progress in files so the agent can recover after context loss, crashes, compaction or /clear.

automation

actually operates websites instead of just telling you how to operate them

npx skills add vercel-labs/agent-browser

Gives the agent real browser automation for navigation, forms, screenshots, data extraction, authentication and even systematic exploratory testing.

growth

turns "check the site for SEO issues" into a real audit

npx skills add https://github.com/kostja94/marketing-skills --skill seo-audit

Checks technical SEO, indexing, on-page issues, content, and off-page factors in a defined order instead of dumping a random list of recommendations.

discovery

turns a one-off workflow into a reusable skill and lets you test whether it actually works

npx skills add https://github.com/anthropics/skills --skill skill-creator

Helps create new skills, improve existing ones, run evaluations, benchmark changes and optimize skill descriptions so they trigger more reliably.

That's my current stack

What am I missing?

Especially interested in skills that are actually useful in day-to-day agent work


r/claudeskills • • May 02 '26

Skill Share I built a Claude skill that turns any technical book PDF into a skill you can query while working

534 Upvotes

you buy a great technical book. you read it once. three months later you can't remember what chapter 7 was even about.

the usual workarounds don't work:

  • "let me search the PDF" → you get page numbers, not answers

  • "i'll ask Claude about this book" → it either hallucinates or says it doesn't have the content

  • "i'll take notes as I read" → you end up with a 200-line doc you never open again

so I built /book-to-skill.

you give it a PDF path. it extracts the text, analyzes the chapter structure, generates dense chapter summaries (800–1200 tokens each, loaded on-demand so they don't bloat your context), a glossary, a patterns file, and a master SKILL.md with the author's core frameworks.

after that, the book becomes a skill you just use:

/designing-data-intensive-apps replication     ← explains replication from the actual book
/clean-code ch07                               ← dives into chapter 7
/cialdini-influence scarcity principle         ← applies the framework to what you're working on

it's not a summary. the goal is to extract structure — named frameworks, exact formulations, anti-patterns, mental models. the kind of stuff that took the author years to crystallize. once it's a skill, Claude can reason with it while you work, not just recite it.

the skill itself handles everything: validates the PDF, runs extraction with three fallbacks (pdftotext → PyPDF2 → pdfminer), gives you a token cost estimate before doing anything, and asks what you want to use the skill for before generating.

install (one command in any Claude Code session):

Install book-to-skill: https://raw.githubusercontent.com/virgiliojr94/book-to-skill/master/SKILL.md

then:

/book-to-skill ~/Downloads/your-book.pdf

repo: https://github.com/virgiliojr94/book-to-skill


caveats:

  • works best on digital PDFs (scanned/image PDFs need OCR first)

  • heavy skill — takes a few minutes on a long book

  • each chapter file is on-demand so the base skill stays under 4K tokens


r/claudeskills • • Oct 09 '26

Guide I passed Anthropic's Claude Architect Foundations CCA-F on the 1st try (no coding background) & helped 20 others too

526 Upvotes

If you had no idea about the official Anthropic Certifications there are 4 now. The first one is the one I passed in August Claude Architect Foundations CCA-F.

We did this as a small community of women in AI who wanted to validate our knowledge of AI to the source and get best practices on how to work with it, especially for client implementations.

If you are into AI consulting, services, agents and education/strategy, and have no coding background, this is a huge knowledge booster in my opinion. I have been a product and project manager before but this really clarified where AI fits in business implementations.

The pod

I didn't do this alone. I led a study pod of about 20 women, most of them non-technical, through the same prep. Most of those who have taken the exam so far passed on their first try. I passed first to make sure that I can actually help them.

What the exam is

The basics:

  • 2 hours, 60 questions, proctored online

  • Closed book, and you can't use Claude during it (yes, the irony)

  • You get 4 scenarios, picked at random from 6, with 15 questions on each from the exam guide

  • 5 technical domains covered with a big emphasis on Agentic AI

The six scenarios are a customer support agent, code generation with Claude Code, a multi-agent research system, structured data extraction, developer productivity, and Claude Code in continuous integration.

What surprised me

"Foundations" is misleading. It doesn't ask for definitions. It drops you into a situation where something is broken or misbehaving and asks how you'd fix it using best practice. The official practice exam is easier than the real thing.

If you don't write code for a living, half of those scenario names sound like they're not for you. That was my first reaction too.

What worked

  • Learn the vocabulary first. Most of the difficulty was language, not logic. Once I knew what the terms meant, the questions became judgment calls I could reason through.

  • Study by scenario, not by topic. The exam is organized around situations, so I prepared that way.

  • Learn the specifics. Which files exist and where they live, what each built-in tool can and can't do, and when to use which pattern. This part is memorization plus practice, and there's no way around it.

  • Get hands-on. Non-technical doesn't mean hands-off. You don't need to be an engineer, but you do need to have used the tools. I created a Claude Code project and used it to study.

  • Know the Exam Traps They tend to be wrong in the same few ways and be repeated. Learning how to spot those patterns quickly helped me most.

  • Flag and move on. I marked the questions I wasn't sure about and came back at the end. but don't go back too much and second guess yourself - difference between passing and failing.

The biggest lesson was that explaining a scenario out loud to someone else showed us quickly what we didn't understand yet.

What I got at the end: a badge by Anthropic and a whole lot of knowledge on where AI actually fits in a business workflow and implementation best practices.

Happy to answer questions about the exam or the prep in the comments.

If you're curious

We're hosting a free one-hour webinar on Tuesday, October 20 at 5 p.m. Eastern. It covers what the certification is, who it's for, and how we prepared as non-technical people.

Comment CCAF for the link


r/claudeskills • • 3d ago

Skill Share Chisle - a skill which saves more tokens than caveman and ponytail without loosing accuracy

Thumbnail
gallery
511 Upvotes

Caveman and ponytail teach Claude to write terser output. That's one axis. Chisle does that too, then adds the two axes they skip:

Tool-output compressor: a hook that shrinks tool results before they enter context (strip ANSI, keep head/tail + error lines, dedupe). Tool output is the majority of a session and gets re-billed every later turn. Runs behind a safety allowlist so it never touches Read/Edit/Write.

Context Diet: grep-then-read-the-slice instead of whole files, don't re-read files already in context. Prevention over cleanup.

It's a descendant of caveman and ponytail: both credited in the README, directly above the benchmarks where it bills less and backfires less often than either.

Repo + install: https://github.com/JayPokale/Chisle
NPM: https://www.npmjs.com/package/chisle
Docs: https://chisle.jaypokale.me


r/claudeskills • • Oct 14 '26

Skill Share Forget Udemy - I have Claudemy

Post image
506 Upvotes

Announcement: This repo was published on XDA devs https://www.xda-developers.com/i-found-a-claude-skill-that-turns-ai-into-my-personal-tutor-for-anything/

Edit #2: The repo now has 508 stars - in 2 weeks! Thanks all

Edit: Video Drop
I made a short video for the tool itself - enjoy https://www.reddit.com/r/claudeskills/comments/1x6vtbu/follow_up_on_claudemy_forget_udemy_and_coursera_i/

I wanted to learn about consulting but I wanted the information to come from actual experts.

But I didn't want to read - I learn best by listening to short audio lessons. So I made a skill for it.

You give it a topic, it finds experts in the field, scrapes their open blogs, books, research on the topic. Then creates bite sized audio lessons. It uses notebooklm to make the lessons so they are in podcast style.

https://github.com/assafkip/claudemy


r/claudeskills • • Sep 09 '26

Discussion Which single skill has been the biggest game changer for you recently?

479 Upvotes

Which single skill has been the biggest game changer for you recently?

AI moves pretty fast and what really helps changes pretty often. So I thought I'd create a regular space (as a mod) in which we can talk about which skills are helping us the most.


r/claudeskills • • 12d ago Mindblown Bravo

Guide I got tired of endless Claude Code tutorials, so I built a free game to learn it by actually using it

Thumbnail
gallery
475 Upvotes

I got tired of going through endless tutorials and GitHub repos just to learn Claude Code, so I built a little game to make the process more fun.

It's called Claude Code Quest. You learn by completing hands-on challenges, with three levels from beginner to advanced. It covers everything from the basics to skills, hooks, subagents, MCP, and more.

The game is free, though you'll need access to Claude Code for the exercises.

Here's the repo:
https://github.com/wesammustafa/Claude-Code-Everything-You-Need-to-Know

Still improving it, so I'd love to hear what you think or what you'd change.


r/claudeskills • • Jun 19 '26

Showcase unslop-ui: a Claude skill that flags and removes the design patterns that make a website look AI-generated.

Post image
470 Upvotes

It is based on a Reddit analysis (from this post I made) of about 3.2 million posts across 47 AI and SaaS subreddits from 2020 to 2026, plus 3,033 comments pulled from 125 threads specifically about AI-built sites looking the same. Every pattern it checks is weighted by how often people actually name it in that data, so the highest-priority items are the ones that come up most. The top ones are the default shadcn/Tailwind look, purple and indigo as the primary color, purple-to-blue gradients and gradient heading text, unprompted neon glow, emoji used as icons, the Inter/Geist default font, and the centered hero plus three feature cards layout. Patterns the data does not support get left alone (mesh and aurora backgrounds, bento grids, glassmorphism), so it does not nag about things people do not mind.

The skill runs two ways. In build mode it steers Claude away from those defaults while it writes the UI. In audit mode it runs a scanner over an existing codebase. Each finding shows the file and line and how to fix it, and the scanner gives the whole project a "vibe score."

How to use it:

  • Import the skill into Claude Code or claude.ai, then ask Claude to build or clean up a site and it applies on its own.

  • Or run the scanner by itself, no install past Python: python3 devibe_scan.py ./src. Add --severity high for only the strongest signals, or --json for CI. The exit code is the count of high-severity findings, so a build can fail on it.

The full dataset, the analysis scripts, and the charts behind the rankings are public: https://github.com/JCarterJohnson/vibecoded-design-tells

================

Edit: reworked this after the feedback. Updated version is in a new post here: https://www.reddit.com/r/claudeskills/comments/1ubc2ps/unslopui_v2_a_claude_skill_that_flags_and_removes/


r/claudeskills • • Oct 17 '26 Mindblown

Skill Share How I ship faster with Claude Code

Post image
453 Upvotes

As I was using Conductor (an agentic IDE) and working on multiple features, I noticed that I I kept having to make many different worktrees for each feature and I thought to myself "Why can't I just have one main thread for everything?".

I realized that the main bottleneck is that more often not Claude just does the work in it's main thread + opens a lot of background dev servers so I'm afraid of sending a new message while it's working cause I'm concerned it will just f*uck up everything.

So I built a skill to fix this, whenever I open a new session in whichever prompt I just run "[...prompt] /orchestrator" and this forces Claude Code to run any task as a subagent and to never block the main thread. Essentially Claude becomes an Orchestra conductor of subagents.

Every task goes to a background agent. There is no endlessly waiting, polling, sleeping, etc. When an agent finishes, a notification starts the next turn. Anything shell-side over 10 seconds (tests, builds, installs) also runs in the background.

For each task it:

  1. splits my message into independent tasks

  2. sends follow-ups to an agent already on that topic (SendMessage keeps its context) or starts a new one

  3. dispatches all new agents in one message, in parallel

  4. replies in 3 lines: what started, under which name, what I can do next

It keeps a ledger in .context/orchestrator.md where each agent has one line with a description of what it's working on.

I code for my startup so I have to be extremely productive and I already have 3 different Claude Code subscriptions and I try to make most of them. So I added a line in the skill to force it to select the best model for each subagent based on the difficulty of the task. For simple frontend tasks you don't really need Opus 5.5. And this goes a long way towards increasing the usage of my Claude plan.

If you have suggestions on how to improve it further, please comment below or submit a PR!

https://github.com/olivieropinotti/orchestrator-skill


r/claudeskills • • 17d ago

News higgsfield wants to kill comfyUI.

Post image
436 Upvotes

Higgsfields trynna kill Comfy UI.

So here’s what’s happening. Comfy launched an “Open Source Higgsfield” challenge for open-source rebuilds of Higgsfield-style apps. Their pitch is that Higgsfield promised to open source its platform and never did.

Now Comfy’s co-founder says Higgsfield sent them a cease and desist, demanding the challenge come down within 48 hours.

A company that sells access to other people’s models is lecturing ComfyUI about using someone else’s stuff. The irony is insane!!

And Comfy said: hell no.

Let’s be honest about what these prompt wrappers are. They take models someone else built, slap on a UI and a credit system, and charge you for the privilege. If you want Kling, go to Kling. If you want Seedance, go to Dreamina. If you want open source, run it yourself. There’s no reason to pay a middleman.

I support open source 100%. If your business can’t survive people rebuilding your apps for free in two weeks, maybe you never had much of a business.

Never using a wrapper again.

Who do you support? whats yall take


r/claudeskills • • Jul 05 '26 All Seeing Upvote Heartwarming

Skill Share I used the rest of my Fable 5 quota to build Engram, a Claude Code plugin for learning anything (and actually keeping it)

424 Upvotes

Why I built this

Agents build faster than I can understand what they built. That's the uncomfortable part of this era for me. Claude ships a feature in twenty minutes, and I'm still the one responsible when it breaks, still the one who has to reason about it in review, still the one who's supposed to know what's going on under the hood. The bottleneck quietly moved from "how fast can we build" to "how fast can we genuinely learn." We got a 10x tool for building. I wanted one for understanding.

So I burned the rest of my Fable 5 quota building Engram. An engram is the physical trace a memory leaves in your brain, which is literally what the plugin is supposed to produce.

How it works

Three commands: /learn, /review, /coach. Under the hood it implements the boring learning science that actually replicates, and deliberately skips the fun stuff that doesn't:

- retrieval practice: it tests you constantly because testing IS the treatment, not the measurement (Roediger & Karpicke 2006)
- real spaced repetition: FSRS, the same modern scheduler Anki uses, fitted to your own review history over time
- generation first: it makes you predict or attempt before it explains. It will not just hand you the answer (unless you explicitly say "just tell me", in which case it complies and quietly schedules that concept for earlier review, because told-not-derived decays faster)
- every topic becomes a first-principles concept graph, "why must this be true given that", instead of textbook chapter order
- threshold concepts get generated interactive HTML explorables with sliders and prediction gates, because some things you need to see and poke
- explicitly no "learning styles". That theory never survived testing. It adapts from your measured retention instead.

The design decision I'm happiest with: the tutor never grades you. A separate assessor agent grades your answers blind, rubric in hand, without ever seeing the lesson, and writes a receipt to disk. In my first real session the tutor was convinced things went great and the assessor came back with 1 recalled, 4 partial, 1 lapsed. It was right. It also turned out the tutor had been logging confidence scores I never actually stated, so "never invent the learner's confidence" is now a hard rule in the code. A system that pushes back on its own optimism ended up being the whole point.

Does it work

Honest answer: the science underneath is some of the most replicated stuff in psychology, but the plugin itself currently has an n of 1, me, and my first week of retention data is still cooking. What I can report: I used it to learn transformer FFN internals yesterday and derived about half the concepts myself before being shown anything. That basically never happens when I just read about something.

Day to day it's tiny on purpose. You run /learn <anything> once (it works for non-code topics too, history or music theory or whatever). Then it pings you at session start when reviews are due, /review takes 2-4 minutes of free recall, and /coach shows retention stats and a local HTML dashboard. Everything is plain JSON in ~/.claude/learning. Nothing leaves your machine.

Install

claude plugin marketplace add nagisanzenin/engram
claude plugin install engram@engram

Needs python3, no pip installs, MIT licensed. Repo: https://github.com/nagisanzenin/engram

If you try it, tell me where it feels annoying. The failure mode of every learning tool ever made is that you stop showing up, so friction reports are worth more to me than praise.


r/claudeskills • • Sep 22 '26

Skill Share Library with 40+ design skills

Post image
423 Upvotes

I think most people designing their UI's with claude don't give it enough details about the design they're going for, they just give it some reference screenshots and then hope it gets it right. Ever since I started making actual skill files and detailed design guidelines docs I started getting much better results.

I put together Skills UI which is a library of different Claude skills for certain design styles and animation effects. There's also a design extractor that lets you upload screenshots and it gives you the design guidelines to give Claude to replicate it.

I'm wondering what type of other ones I should add? if you have some suggestions please let me know.


r/claudeskills • • Sep 05 '26

Skill Share I built a Claude Code plugin for my ADHD brain — it remembers the things I forget mid-conversation

Post image
413 Upvotes

I have ADHD, and my biggest problem with Claude Code isn't the coding. It's that I forget everything. Tasks I said I'd do "later", ideas I floated last week, questions Claude asked me that I never answered, sessions that died mid-decision. All gone the moment I close the terminal.

So I built a plugin called claude-adhd that acts as external memory.

When I open a session it quietly surfaces my 1-3 most stale forgotten threads, and flags anything that's been sitting there over 2 weeks. If I commit to a task mid-chat, Claude silently records it and marks it done when it's actually finished. No todo app to maintain, which is important because I have never once maintained a todo app for more than 3 days.

You can also set reminders by just saying them. "Remind me tomorrow at 3pm to check the deploy" or "every session remind me to run tests first" — they show up naturally in the conversation when they're due. There's a focus mode too, /focus 25 ship-the-release, and if the chat drifts off task it pulls you back. When time's up you get a little wrap-up of what got done.

The part I'm most careful about is not making it annoying. Random nudges are capped at 2 per session with a 3-day cooldown per item, and the model only brings things up when it actually fits the conversation. If it feels like nagging, people will uninstall it in a day.

There's also "I'm fried" mode — tasks get energy tags, and when you have no energy it only offers the low-effort ones. And a local dashboard with stats and streaks, though honestly the streak counter is just dopamine bait and I love it.

Everything stays on your machine. No telemetry, no API keys, no dependencies beyond Node.

It's in test mode and I've mostly just been dogfooding it myself, so I'd genuinely love feedback from other ADHD brains. What would actually help you? What would be too annoying?

Install if you want to try:

/plugin marketplace add shaheer-00/claude-adhd

/plugin install claude-adhd@claude-adhd

Repo: https://github.com/shaheer-00/claude-adhd

Feedbacks are most welcome