performance-fix SKILL.md skillA

performance-fix from pmatos/jsse is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add pmatos/jsse/performance-fix@v0.1.0

Pins v0.1.0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
pmatos/jsse
Path
.claude/skills/performance-fix/SKILL.md
Versions recorded
3
Latest version
v0.1.0, committed Mar 31, 2026
First version recorded
Mar 29, 2026
Size
4,700 bytes
Repository stars
73
License
MIT

This skill should be used when the user asks to "fix performance issues", "optimise the bottlenecks", "implement the performance fixes", "apply the performance report", "speed this up based on the report", or wants to act on a performance report produced by /performance-analyse. Reads a performance report and implements targeted fixes.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Performance Engineer

Fix exactly **one** performance bottleneck per invocation. If the target issue is unclear, interview the user before writing any code.

## Workflow

1. **Identify the target** — Determine which single bottleneck to fix:
   - If the user named a specific hotspot or issue number from the report, use that
   - If the user's request is vague ("fix performance", "speed this up"), load `perf-report.md` and **ask the user which hotspot to tackle** — list the hotspots with their severity and let them choose
   - If `perf-report.md` does not exist or does not contain the issue the user describes, **interview the user**: ask what is slow, how they observe it, what workload triggers it, and what "fast enough" means — then suggest running `/performance-analyse` first
   - Never guess which issue to fix. Always confirm the target with the user before writing code.
2. **Fix one bottleneck:**
   a. Understand the root cause from the report (or from the user interview)
   b. Implement a minimal, targeted fix
   c. Build in release mode
   d. Re-measure using the same benchmark from the report
   e. Record before/after numbers
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add pmatos/jsse/performance-fix@sha256:e6938ba43a73322e

The line at the top of this page pins the label v0.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_f6ym2wokvljycgqa.svg)](https://markdownregistry.com/a/art_f6ym2wokvljycgqa)

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 3 versions of this file, between Mar 29, 2026 and Mar 31, 2026, about one every day.

versioncommittedcommitsizeaudit
v0.1.0 latest2026-03-31 1e94505 4,700 BA view · diff
v0.1.02026-03-29 224da19 4,446 BA view · diff
v0.1.02026-03-29 abf0af0 4,011 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (4700 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

pmatos/jsse · 73 stars · license MIT · pushed 2026-10-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_f6ym2wokvljycgqa
GET https://markdownregistry.com/api/v1/resolve?ref=pmatos/jsse/performance-fix
GET https://markdownregistry.com/api/v1/blob/e6938ba43a73322ec48d4cd2893cdfb6760e631a9eeda9f3f8db0b165c576f90

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from pmatos/jsse

fuzzing SKILL.md skill
pmatos/jsse · .claude/skills/fuzzing/SKILL.md · This skill should be used when the user asks to "fuzz the parser", "run cargo fuzz", "fuzz jsse vs node", "check for…
v0.1.0 · audit A · 73 stars
performance-analyse SKILL.md skill
pmatos/jsse · .claude/skills/performance-analyse/SKILL.md · This skill should be used when the user asks to "profile the codebase", "analyse performance", "find bottlenecks"…
v0.1.0 · audit A · 73 stars
AGENTS.md AGENTS.md file
pmatos/jsse · AGENTS.md
git:20261019.d60f0ce · audit A · 73 stars

Every file in pmatos/jsse

Browse by kind, by grade A, or by owner.