r/claudeskills • • 2h ago

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

58 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 • • 10h ago

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

48 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 • • 11h ago

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

24 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 • • 10h ago

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

Post image
16 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 • • 10h 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
9 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 • • 9h ago

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

6 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 • • 1h ago

Skill Share Narrowing down issues and their fixes

Post image
• 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 • • 1h ago

Question Alternative to Claude in Chrome

Thumbnail
• Upvotes

r/claudeskills • • 1h ago

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

• 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 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 • • 10h 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 • • 11h ago

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

Thumbnail
leaddev.com
3 Upvotes

Everyone’s a software engineer now.


r/claudeskills • • 5h ago

Skill Share 151 suggested lessons from my agents' mistakes. I've accepted 17.

1 Upvotes

I wanted to stop correcting the same mistakes in Claude Code and Codex. This skill reads their sessions and proposes one-line lessons or changes to their skills. Nothing changes until I accept it. I can reject suggestions too.

On my machine today: 17 accepted, 47 rejected, 87 waiting. It's set up for daily reviews, but I've got the schedule off right now.

One evening I was annoyed about two things. By the next morning, after I accepted the changes, both were rules in the live skills.

But I've still got 87 suggestions I haven't decided on. Finding another mistake doesn't clear that pile.

Privacy matters here. At full sharing, session text and installed skills go to the service's cloud. Local-first sends nothing there, but a few sessions a night still go to their own agent accounts to ask for lessons. Uploading can be turned off with sno station consent off.

I wrote it. Free and open source, Apache-2.0: https://github.com/sno-ai/sno-station-skills/blob/main/skills/R-recursive-self-improvement/rem-reflect/skill/SKILL.md

How do you decide which suggested rules are worth keeping?


r/claudeskills • • 14h ago

Skill Share I built Measured Humanizer with Claude Code - an open-source style gate for Claude that measures why AI writing feels robotic (and fixes it)

Thumbnail
3 Upvotes

r/claudeskills • • 12h ago

Skill Share I built RLM Agent Skills: a VS Code extension that installs structured agent workflows across Copilot, Claude Code, Cursor, Codex, Gemini CLI & Windsurf (with a 3D pipeline visualizer)

2 Upvotes

Hey everyone — I built RLM Agent Skills, an open-source VS Code extension that drops structured, repeatable engineering skills directly into your project's agent folders, plus an interactive 3D web guide so you can see how each skill actually processes your codebase before installing it.

Processing gif tja6x9r89l2i1...

What it does

Instead of rewriting complex multi-step prompts for audits, postmortems, or compliance checks, the extension installs pre-built `rlm-*` skills (14+ enabled by default, plus optional ones like `rlm-security-audit`, `stack-auditor`, `incident-postmortem`, `release-notes`, `trust-layer-validator`, and compliance workflows) straight into the right directories for whichever coding agents you use:

* GitHub Copilot: `.github/skills/`

* Claude Code: `.claude/skills/`

* Cursor: `.cursor/skills/`

* OpenAI Codex: `.agents/skills/`

* Gemini CLI: `.gemini/skills/`

* Windsurf: `.windsurf/skills/`

### Key highlights

* **3D Visual Guide:** On the demo site, every skill is visualized as a 3D data-flow pipeline—you can step through what goes in, how chunks/memory are handled, and what comes out, along with pros/cons.

* **No API keys or lock-in:** The extension makes zero external model calls—it simply sets up the skill files and local helper scripts (Python, Node.js, or instructions-only), and your existing agent/subscription does the work.

* **Non-destructive updates:** Re-running the installer updates skills while leaving any files you’ve customized untouched. Local graph memory is stored cleanly in `.agent-memory/graph.json`.

### How to try it

  1. Grab `skill-pack-1.0.0.vsix` from the [GitHub repo](https://github.com/kamalsoft/skill-pack) and install it via `code --install-extension skill-pack-1.0.0.vsix` (or *Install from VSIX…* in VS Code).
  2. Open a project folder and run **RLM: Install Agent Skills** from the Command Palette.
  3. Ask your agent in plain English, e.g.:`Use the rlm-security-audit skill on src/. Report findings with file and line.`

MIT licensed. Would love any feedback on the skill workflows, the 3D visualizer, or what other engineering skills you'd want added!


r/claudeskills • • 18h ago

Showcase so i made two random lines, got r=0.91 p<0.001. built a claude skill that catches this

5 Upvotes

i generated two random walks and labeled them “signups” and “avocado prices”. no connection at all. pearson gave me r = 0.91, p < 0.001 lol

asked claude code if it was real. the skill i made (skeptic) basically just runs your exact test on a few hundred fake datasets with no effect in them and counts how often it still says significant. it was 79%. should be ~5%. it also told me not to put it in the board deck which, fair

it’s just monte carlo calibration, nothing new, i just got tired of doing it by hand. free/MIT, not selling anything. video’s the real session sped up

github.com/Par-python/skeptic

roast it, especially if you know stats better than me


r/claudeskills • • 11h ago

News deadweight: a Rust CLI that measures what your Claude Code setup sends on every request

Thumbnail
1 Upvotes

r/claudeskills • • 1d ago

Skill Share if you run an agency, consultancy or coaching biz, this one’s for you. 60+ agency skills built by operators.

54 Upvotes

if you run an agency, consultancy or coaching biz, this one’s for you. if you don’t, probably skip lol

most skill packs out there are built for devs or generic marketing. i wanted ones built around how agencies actually run: winning work, scoping, delivering, keeping clients, protecting margin

so i asked a bunch of agency founders, consultants and coaches to share the skills they actually use, cleaned them up, and put them in one place. 60+ so far, plus a few we wrote ourselves

some examples:

  • proposal generator (call notes in, first draft out)
  • JTBD segmentation, from a PMM firm
  • network mapping for referrals
  • delivery ops stuff like scope checks and client reporting
  • Upsell opportunity finder

they’re grouped into collections like win the work, deliver and keep clients, price and protect margin, and run the firm

free and open source (MIT). works in claude, and also chatgpt or whatever else you use. you can grab them one at a time or install the whole library through the MCP connector (free, it just asks for an email)

agency-skills.com

if you’ve got a skill your agency swears by, send it my way. contributors get their own page with a link back to their firm

and if you try any of them, tell me what’s broken or missing


r/claudeskills • • 13h ago

Skill Share build: a skill that writes the spec first, then the code

0 Upvotes

Getting a first version running with Claude Code is quick. The trouble starts months later, when something has to change and nobody, the agent included, knows what the code was meant to do

build is an answer to that: a free, open-source skillset (MIT). Concept documents are the specification and the code is derived from them. My test is whether a second agent could rebuild the product from the documents alone.

You type "start", then "next", "redo" or "stop". A director skill runs four stage skills:

Intake: takes a brief or problem statement, asks only for what is missing.
Concept: numbered requirements, ADRs, architecture in slices, consistency check.
Synthesis: red-green-refactor per slice. Commits cite the requirement IDs.
Rescue: on demand, removes entropy and reports drift between docs and code.

A human decides at three gates: requirements, consistency findings, and a gap analysis before release.

Also built in: STPA-light (losses, hazards, constraints, each traced to a requirement and a test) and secret protection before the first line of code (hook, gitleaks pre-commit).

Plain markdown, nothing to install. Open the folder in Claude Code, Codex or Cowork and type "start", or symlink skills/build* into ~/.claude/skills/. Customer-specific rules go into a profile/ folder instead of a fork.

Repo: https://github.com/ditomax/build

The skill is developed for two projects, a medical app and another skill for diagnostics of electrical faults in industrial plants.

For those maintaining agent-written code longer than a few weeks: where does drift show up first for you? Does spec-first hold up, or does it just move the problem into the docs?


r/claudeskills • • 14h ago

Discussion I run a company-data service as one person plus a few Claude Code sessions with separate jobs

0 Upvotes

What I built: Leadgen (https://leadgen.adrianhomelab.com/en), which puts Romania's official company data on one page for any of 4.2M firms: trade register status, VAT and tax-inactivity status, the latest balance sheet and public contracts. Checking a company is free and needs no account; there are paid tiers for heavier use. It also has a remote MCP server, so Claude can run the same check inside a chat.

How Claude helped, in detail. I don't use one long session; I use several Claude Code sessions, each with one job:

  • An orchestrator session writes briefs for helper sessions, merges their work through a reviewer step, cuts release candidates and keeps a handoff file so the next session knows what was decided and why.
  • A QA session only tests. Before each release it runs Playwright on staging (sign in with an e-mailed code, follow a company, check the alert e-mails in a test mailbox) and posts pass/fail with screenshots. It never fixes anything itself.
  • An SEO and growth session reads Search Console and the web server logs. It found that Google had almost stopped crawling the company pages (from a few hundred fetches a day to one) and drafted the fixes: a smaller sitemap and letting AI search crawlers through.
  • The sessions talk through plain markdown mailbox files on a shared server. I read those, decide, and nothing that goes outside (releases, e-mails, listings) happens without my "go".

What I learned:

  • Narrow roles plus a written handoff worked better for me than one long session that does everything.
  • A session whose only job is testing, with screenshots as evidence, makes releases boring in a good way.
  • Give every outward action a human gate. The sessions draft, I send.

Free to try: https://leadgen.adrianhomelab.com/en MCP endpoint (no sign-in, 30 calls a day): https://leadgen-mcp.adrianhomelab.com/mcp


r/claudeskills • • 1d ago

Showcase WebCraft Pro – 43 Reusable AI Agent Skills for Better Web Engineering

10 Upvotes

Hey everyone!

I've been using AI coding agents like Codex, Claude Code, and GitHub Copilot to speed up web development. But I noticed a recurring problem: generating code is easy; consistently following engineering standards is harder.

Agents can produce generic interfaces, overlook keyboard accessibility, introduce unsafe code patterns, and miss performance considerations.

That's why I built WebCraft Pro.

It's an open-source, framework-agnostic engineering toolkit designed to help developers and AI agents follow a structured web development process.

What's included:

- 43 reusable Agent Skills covering web engineering.

- An eight-stage development lifecycle, from design through browser QA and release.

- 13 engineering templates for structured implementation and reviews.

- GitHub Actions for repository validation and automated checks.

- Playwright keyboard and focus tests.

- An on-demand browser accessibility checker using axe-core.

- A Node.js static security-pattern audit for code examples in repository Markdown files.

It supports OpenAI Codex, Claude Code, and GitHub Copilot.

I also want to be clear about the limitations: these automated checks are engineering guardrails, not a complete application security scanner or a guarantee of accessibility. Manual review and project-specific testing are still essential.

Project: WebCraft-Pro

I built this because I wanted something more structured than relying on prompts alone.

I'd appreciate honest feedback:

  1. What engineering checks do you expect AI coding agents to run before opening a pull request?

  2. Which skills or workflows would you add?

  3. Would this fit into your existing development workflow?

Thanks for taking a look!


r/claudeskills • • 1d ago

News Golden Thread 0.23, a free Claude Code plugin: run everything on local models, hosted engines or Claude, and control it from your phone

Post image
11 Upvotes

I built Golden Thread, a free, open-source (MIT) plugin for Claude Code, and I built it with Claude Code: Claude wrote the plugin, its hooks and its tests, in a separate git worktree per release. The next release, 0.23, adds the nine things in the image: the workflow builder, then four about engines and four about control.

What it does:

  1. Workflow builder. Describe what you want in plain words and it drafts the steps and suggests a model for each. A discovery agent first lists everything your connected systems can do (GitHub, Jira, Microsoft 365, MCP servers, local engines), so you choose from what exists. Or use a guided form with no model at all. You see the whole workflow as a flowchart, see which engine runs each step and what it costs, run it at set times or on an event, call one workflow from another, and review every effect before you enable it.

  2. Workflow engine. A saved chain of steps you can read: run a script, hand a task to another engine, loop, ask Claude, or wait for you. A workflow names roles (planner, coder, reviewer), never a model. Loops are counted, and a step that keeps failing moves up one engine, then reaches your phone as a question.

  3. Environments. One file says which engines fill each role, cheapest capable first. Switch environment and the same workflow runs on other models. Private text goes only to local engines.

  4. Wizards. Add a local model, add a hosted engine such as Gemini (the key never enters the chat), or connect GitHub, Jira, Microsoft 365 or any MCP by URL. Anything that spends money or widens access needs user security.

  5. Local models do the first pass. Drafts and reviews go to a free engine first, and a different engine checks the result in a read-only copy. Each task type is compared against Claude before it goes live.

  6. Phone remote control. Pair your phone using security gates, then answer question cards, approve or reject an edit from a diff card, or stop a run. A remote run needs a timed, capped window that you open with user security.

  7. Mission Control. A plan splits work into units with budgets, and a small local model dispatches worker sessions whose scope comes only from the signed plan.

  8. A workflow for releases. A 15-stage protocol with four gates a person signs, a release gate that runs tests and a secrets scan, and release notes that carry test counts per platform.

  9. Safety you can audit. Every command gt runs goes into a hash-chained journal, tools get a vetting score before you adopt them, and engine-written code runs in a sandbox.

Free to try: https://github.com/shaven/golden-thread

Clone it, then run: bash golden-thread/golden-thread-plugin/install.sh --vault ~/MyVault

and restart Claude Code.

Which local engines do you run, and what would you want a wizard to set up for you?


r/claudeskills • • 16h ago

Showcase Heredocs keep getting mangled in claude code, so i built a plugin for it.

1 Upvotes

heredocs were a big problem in claude code - opus typing out thousands of tokens in a single command only for the heredocs to get mangled and opus resending the entire thing all at once. unnecessary token burn

so i built unheredoc. it saves the file temporarily and so each fix is just a 20-token rewrite of a single line rather than the entire command rewrite.

built by claude code, for claude code. try it here - IronManRox228228/unheredoc: Claude Code plugin: saves heredoc commands to a script so failed ones get fixed with a small edit, not a full resend.

install it in claude code here:

/plugin marketplace add IronManRox228228/unheredoc

/plugin install unheredoc@unheredoc

PS: mods this acc is new becuz my old acc got banned for some reason, please don't remove this post, i don't have enough karma but i promise i'll try to gain it pls


r/claudeskills • • 1d ago

Skill Share I made a Claude Code skill for exploring research papers

Thumbnail
gallery
82 Upvotes

I'm working on Danseo, a skill for exploring research papers with Claude Code.

It makes an interactive map you can click through. Pick a paper to see related work, or a connection to check the explanation and the page it points to. AI-suggested connections are labeled separately.

The screenshots show a few papers around the Transformer. You can save the map locally and pick it up again later.

Free and open source: https://github.com/OstenHun/danseo

Update: The map now shows citation counts and conference/journal rankings, with links to the sources. Bigger nodes mean more citations; the badges show the venue's rank.


r/claudeskills • • 17h ago

Skill Share How I built a Search Console skill that won't rank your queries below 500 non-brand impressions (and the other rules in it)

1 Upvotes

Disclosure: this is a paid skill I sell, details and price at the bottom. The rules are the useful part, and you can paste them into your own prompt for free.

The problem I built it for: hand Claude a Search Console export and it will happily give you advice. That advice tends to go wrong in four ways. Brand searches get counted as SEO progress. A handful of clicks becomes a trend. Someone else's CTR curve becomes your benchmark. And a "potential" turns into a promise.

So the skill is a SKILL.md plus a Python script, with a strict split. The script (Python 3.9+, standard library, runs offline) does every calculation and writes a report and CSVs. Claude only does the judgment: confirming brand terms, opening the live results page before recommending anything, and writing the reading.

The rules it enforces:

  1. Brand first. It asks for your brand terms, and the script flags likely brand terms you forgot (position 3 or better, 15% CTR or more, at least 4% of clicks). Everything after that is read on non-brand queries.
  2. A sample gate. Under 500 non-brand impressions or 20 clicks, the sample is "tiny": no query ranking at all, just what to collect and when to look again. Under 5,000 impressions or 100 clicks it's "small": cheap, reversible actions only. Any row under 100 impressions is labelled thin.
  3. Striking distance has a window. Non-brand queries at average position 8 to 20, with at least 30 impressions. The lever depends on the band: 8 to 10 with a weak CTR points at the title and snippet, 11 to 15 at missing sections and 3 to 5 internal links, 16 to 20 starts with an intent check.
  4. Your own CTR curve, not an industry one. Queries are grouped by position and compared with the rest of their group, leaving the query itself out. A group only counts with 10 clicks and 200 impressions. If none qualifies, which is normal for a young site, it says "not computable yet" instead of borrowing a generic curve.
  5. Five actions at most, each with an effect range, the assumptions behind it and a date to re-check. No ranking promises.

On a young site, rule 2 means the honest output is often: not enough data yet, here is what to check that doesn't need it.

The skill is Click Radar, one of 14 in SEO Skills by PENRA. It's paid and not open source: €25 (Christmas price until 25 December, then €99), delivered by email. https://seoskills.click/?utm_source=reddit&utm_medium=post&utm_campaign=jv-8yp2ou

What would you add or change? I keep going back and forth on whether 30 impressions is enough for the striking-distance floor.