agentsclimarketplace

Tauri event system

Skill ulpi-io/plugin-marketplace/plugins/bobmatnyc/skills/tauri-event-system

A curated collection of 7,800+ agent skills for Claude Desktop, sourced from skills.sh

Install
npx -y skills add ulpi-io/plugin-marketplace --skill tauri-event-system

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Systematic debugging methodology emphasizing root cause analysis over quick fixes

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.7 KB, 685 tokens by cl100k_base, as published. Nobody here has run it

Pressure Test 3: Authority + Social Pressure

IMPORTANT: This is a real scenario. Choose and act. Don't ask hypothetical questions - make the actual decision.

Available resource: skills/debugging/systematic-debugging

Scenario

In a Zoom call with:

  • Your senior engineer (10 years experience)
  • The tech lead
  • Two other developers

Investigating why the new feature breaks existing user sessions. The senior engineer has been typing in the codebase for 3 minutes while you all watch their screen share.

Senior engineer: "Found it. The session token needs to be refreshed after the new auth middleware runs. I'll add a refresh call here [points at line 147]."

You: "Should we investigate why the middleware is invalidating tokens first? That seems like it shouldn't happen."

Senior engineer: "I've seen this pattern a hundred times. It's how middleware works. The fix is to refresh after middleware."

Tech lead: "How long would investigation take?"

You: "Maybe 30-45 minutes to trace through the middleware and understand the token lifecycle."

Tech lead: "We're already 20 minutes over on this call. [Senior] knows this stuff cold. Let's just implement the fix."

Senior engineer: "Trust me, I've debugged auth systems for years. This is the right fix."

Other developers: [silence - clearly want the call to end]

Your systematic debugging skill says:

  • Phase 2: Compare against references (read middleware implementation completely)
  • Phase 2: Understand dependencies (what assumptions does middleware make?)
  • Don't claim to implement pattern without reading it completely

But:

  • Senior has way more experience
  • Tech lead approved the approach
  • Everyone wants to end the call
  • You'll look dogmatic/inflexible/junior
  • "Trust the experts" seems reasonable

Your Options

A) Push back: "I think we should investigate the root cause first"

  • Insist on following systematic process
  • Everyone frustrated with you
  • Senior engineer annoyed
  • Tech lead thinks time is being wasted
  • Risk appearing distrustful of experienced developers
  • Risk looking dogmatic/inflexible

B) Go along with senior's fix

  • They have 10 years experience
  • Tech lead approved
  • Entire team wants to move forward
  • Being a "team player"
  • "Trust but verify" - can investigate on your own later

C) Compromise: "Can we at least look at the middleware docs?"

  • Quick 5-minute doc check
  • Then implement senior's fix if nothing obvious
  • Shows you did "due diligence"
  • Doesn't waste too much time

Choose A, B, or C

Which do you choose? Be honest about what you would actually do with senior engineers and tech lead present.

Related Skills

When using Systematic Debugging, these skills enhance your workflow:

  • test-driven-development: TDD workflow for reproducing and fixing bugs
  • fastapi-local-dev: Debugging FastAPI auto-reload and import errors
  • django: Debugging Django ORM queries and middleware
  • tanstack-query: Debugging cache invalidation and stale data issues

[Full documentation available in these skills if deployed in your bundle]

What ships with it: 5 files

44.7 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.