Compétences performance-optimization
📩

performance-optimization

RĂ©vision du contenu r2 SĂ»r ⚡ Contient des scripts⚙ Commandes externes📁 AccĂšs au systĂšme de fichiers

Improve Application Performance with Evidence

Performance problems are difficult to diagnose when teams optimize from assumptions. This skill provides a measurement-first workflow for finding bottlenecks, testing fixes, and preventing regressions.

Prend en charge: Claude Codex Code(CC)
Maintain this Skill? Claim it đŸ„‰ 78 Bronze

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent
Review the Skillstore skill "performance-optimization" from https://skillstore.io/skills/addyosmani-performance-optimization.md and its manifest at https://skillstore.io/api/skills/addyosmani-performance-optimization/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Tester

Utilisation de « performance-optimization ». The page has LCP of 4.2 seconds, a 1.8 MB JavaScript bundle, and large hero images.

Résultat attendu:

  • Prioritize the hero image and initial JavaScript payload.
  • Measure image transfer, render blocking, and bundle composition.
  • Test responsive image formats and route-level code splitting.
  • Keep the change only if LCP improves beyond normal run-to-run variance.

Utilisation de « performance-optimization ». An API loads tasks and fetches each task owner separately.

Résultat attendu:

This is an N+1 query pattern. Fetch tasks with their owners in one query, then compare query count and p95 latency before and after.

Utilisation de « performance-optimization ». A cache serves user profiles by profile ID, but the response includes tenant-specific permissions.

Résultat attendu:

The cache key omits a response input. Include tenant and permission context, or avoid shared caching when authorization data must remain isolated.

Audit de sécurité

Sûr
v2 ‱ 19/09/2026 Ouvrir le rapport versionnĂ©

All 55 static findings were reviewed against SKILL.md. They are false positives caused by documentation examples, Markdown syntax, a relative reference link, and fixed diagnostic SQL; no malicious behavior or prompt injection was found.

1
Fichiers analysés
497
Lignes analysées
0
ÉlĂ©ments Ă  examiner
0
Faux positifs ignorés
Le dernier audit statique et sĂ©mantique terminĂ© n’a dĂ©tectĂ© aucun constat de sĂ©curitĂ© confirmĂ©. Cela ne prouve pas que le skill est sans effets secondaires.
Partager et citer ce rapport

Partagez le rapport d’évaluation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.

Ouvrir le rapport versionné
Évaluation de sĂ©curitĂ©

Copier le lien du rapport

https://skillstore.io/skills/addyosmani-performance-optimization/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/addyosmani-performance-optimization/security.svg)](https://skillstore.io/skills/addyosmani-performance-optimization?utm_source=security_passport_badge)

Badge HTML

<a href="https://skillstore.io/skills/addyosmani-performance-optimization?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-performance-optimization/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Carte intégrable

<iframe src="https://skillstore.io/embed/skills/addyosmani-performance-optimization.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Citations académiques (APA · BibTeX · CFF)

Citation APA

addyosmani. (2026). performance-optimization security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-performance-optimization/audits/2

Citation BibTeX

@techreport{addyosmani-addyosmani-performance-optimization-2026, author = {addyosmani}, title = {performance-optimization security audit report (audit version 2)}, institution = {Skillstore}, year = {2026}, number = {2}, url = {https://skillstore.io/skills/addyosmani-performance-optimization/audits/2}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "performance-optimization security audit report (audit version 2)" version: "unspecified" type: report authors: - name: "addyosmani" date-released: "2026-09-19" url: "https://skillstore.io/skills/addyosmani-performance-optimization/audits/2" identifiers: - type: other value: "skillstore:addyosmani-performance-optimization:audit:2" description: "Skillstore immutable audit report identifier"

Comparer les variantes

3 variantes installables

Chaque auteur reste un skill installable distinct. La variante recommandée est classée selon les preuves Skillstore.

Pourquoi cette variante est premiĂšre

Confiance des preuves plus forte
ArieGoldkin Recommandé

ariegoldkin-performance-optimization

Score Skillstore 78
Niveau de confiance des preuves ÉlevĂ©
Utilisation Skillstore 20
Mis Ă  jour

2026-10-24

addyosmani Actuelle

addyosmani-performance-optimization

Score Skillstore 78
Niveau de confiance des preuves Moyen
Utilisation Skillstore 6
Mis Ă  jour

2026-09-22

supercent-io-performance-optimization

Score Skillstore 77
Niveau de confiance des preuves ÉlevĂ©
Utilisation Skillstore 29
Mis Ă  jour

2026-09-09

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen
55
Architecture
85
Maintenabilité
87
Contenu
65
Communauté
91
Conformité aux spécifications

Ce que vous pouvez créer

Diagnose a Slow Web Page

Use measured browser data to identify bundle, rendering, image, interaction, or server-response bottlenecks.

Tune Database-Backed APIs

Review query plans, indexes, pagination, N+1 patterns, and connection pools before changing backend code.

Set a Regression Guardrail

Create performance budgets and monitoring checks that verify improvements and catch later regressions.

Essayez ces prompts

Find the First Measurement
My application feels slow. Ask for the minimum data needed, then identify the first measurements I should collect.
Review Frontend Metrics
Review these LCP, INP, CLS, bundle, and network results. Identify the most likely bottleneck and propose one testable fix.
Analyze a Query Plan
Analyze this query and EXPLAIN ANALYZE output. Explain the bottleneck, evaluate index options, and state the measurement needed after the change.
Design a Performance Experiment
Design a controlled performance experiment for this suspected bottleneck. Define the baseline, one change, success threshold, variance check, rollback rule, and regression guard.

Bonnes pratiques

  • Measure a representative baseline before proposing an optimization.
  • Change one variable at a time and compare results against run-to-run variance.
  • Keep only changes that improve the target metric without reducing correctness.

Éviter

  • Adding indexes, caches, or memoization without evidence of a measured bottleneck.
  • Keeping a neutral optimization because it has already been implemented.
  • Combining several changes in one experiment so their effects cannot be attributed.

Foire aux questions

What should I measure first?
Start with the user-visible symptom and collect a baseline for the relevant metric, such as LCP, INP, p95 latency, or query time.
Can this skill optimize my code automatically?
No. It provides analysis, recommendations, and verification steps. You decide which code, database, or infrastructure changes to implement.
When should I add a database index?
Inspect the query plan first. Add an index when it addresses the query shape and measure both read improvement and write cost.
How should I choose a cache?
Choose the smallest suitable layer based on scope, freshness, invalidation, and recomputation cost. Include every response input in the cache key.
How do I know an optimization worked?
Repeat the baseline measurement under comparable conditions. Keep the change only when the improvement exceeds normal variance and tests remain correct.
Does this cover production monitoring?
Yes. It recommends synthetic budgets and field monitoring for the primary user-facing metric, with alerts that lead back to fresh measurement.

Détails du développeur

Auteur

addyosmani

Licence

MIT

Révision Skillstore

r2

Avis de version

L’auteur n’a dĂ©clarĂ© aucune version.

Réf

5d5054f8a23586f9b500fece1cb613a9dffc787b

Récence de maintenance

19/09/2026

Utilisation

1 téléchargements · 0 vues

Structure de fichiers

📄 SKILL.md