Skills performance-profiling
📦

performance-profiling

Content revision r1 Medium Risk ⚙️ External commands🌐 Network access📁 Filesystem access

Profile Web Performance Bottlenecks

Slow applications are hard to improve without reliable measurements. This skill guides profiling workflows and Lighthouse audits to identify practical optimization targets.

Supports: Claude Codex Code(CC)
📊 67 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "performance-profiling" from https://skillstore.io/skills/sickn33-performance-profiling.md and its manifest at https://skillstore.io/api/skills/sickn33-performance-profiling/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-performance-profiling.md Signed manifest GET /api/skills/sickn33-performance-profiling/manifest Signed lockfile GET /api/skills/sickn33-performance-profiling/lockfile

Test it

Using "performance-profiling". A dashboard has slow first load and a large main bundle.

Expected outcome:

  • Measure a baseline with Lighthouse and browser performance tools.
  • Inspect bundle size for large dependencies, duplicate packages, and missing route splits.
  • Prioritize code splitting, dependency trimming, compression, and image optimization.

Using "performance-profiling". A page feels delayed when users click filters.

Expected outcome:

  • Profile the interaction in DevTools Performance.
  • Look for long tasks, heavy event handlers, layout work, and unnecessary rendering.
  • Fix the largest blocking task first and validate the interaction again.

Using "performance-profiling". A Lighthouse run shows acceptable SEO but poor performance.

Expected outcome:

Focus on loading metrics first. Check render blocking resources, image size, unused JavaScript, cache headers, and compression before changing SEO content.

Security Audit

Medium Risk
v4 • 7/7/2026 Open versioned report

The Markdown examples and most filesystem patterns are safe documentation or normal temporary file handling. The script intentionally runs Lighthouse and accepts an arbitrary URL, which creates a network reachability risk in agent environments.

2
Files scanned
221
Lines analyzed
1
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
scripts/lighthouse_audit.py:16-25scripts/lighthouse_audit.py:70-75
Unrestricted URL Auditing
The Lighthouse script accepts a URL argument and passes it to Lighthouse for fetching. In an agent environment, this could be used to reach localhost, private networks, or metadata services unless guarded by policy.
The script takes sys.argv[1] and uses it as the Lighthouse target URL. This is intended behavior, but no validation or private-network guard is present.
Capability review items (1)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Low
scripts/lighthouse_audit.py:19
Temp file creation
with tempfile.NamedTemporaryFile(suffix='.json', delete=False) as f:
The script creates a temporary JSON report with delete=False and only removes it after successful parsing. A timeout or early failure could leave a report file in the temp directory.

Risk Factors

⚙️ External commands (3)
scripts/lighthouse_audit.py:22 SKILL.md:17 SKILL.md:45-50
🌐 Network access (2)
scripts/lighthouse_audit.py:6 SKILL.md:17
📁 Filesystem access (3)
scripts/lighthouse_audit.py:14 scripts/lighthouse_audit.py:19 scripts/lighthouse_audit.py:39
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-performance-profiling/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

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

APA citation

sickn33. (2026). performance-profiling security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-performance-profiling/audits/4

BibTeX citation

@techreport{sickn33-sickn33-performance-profiling-2026, author = {sickn33}, title = {performance-profiling security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/sickn33-performance-profiling/audits/4}, 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-profiling security audit report (audit version 4)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-07" url: "https://skillstore.io/skills/sickn33-performance-profiling/audits/4" identifiers: - type: other value: "skillstore:sickn33-performance-profiling:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
45
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Prepare a Performance Baseline

Measure current page speed before starting an optimization project.

Review Release Readiness

Check Core Web Vitals and Lighthouse categories before shipping a web change.

Prioritize Optimization Work

Translate slow page symptoms into focused actions for product planning.

Try These Prompts

Explain My Scores 
Use the performance-profiling skill to explain my Lighthouse scores in plain language and list the first three fixes to try.
Choose Profiling Tools 
Use the performance-profiling skill to match these symptoms to the best profiling tools: slow load, delayed clicks, memory growth, and scroll jank.
Build an Optimization Plan 
Use the performance-profiling skill to create a prioritized plan for improving a web app with slow initial load and large JavaScript bundles.
Audit a Release Candidate 
Use the performance-profiling skill to run or review a Lighthouse audit for my release URL, then identify risks, tradeoffs, and validation steps.

Best Practices

  • Measure a baseline before changing code.
  • Fix the largest verified bottleneck before smaller issues.
  • Validate improvements with the same tool and comparable conditions.

Avoid

  • Do not optimize based only on guesses or visual impressions.
  • Do not chase micro-optimizations before fixing major load and runtime issues.
  • Do not rely only on lab data when real user monitoring is available.

Frequently Asked Questions

Does this skill run Lighthouse automatically?
It includes a Lighthouse audit script, but the Lighthouse CLI must be installed and available.
Can it improve Core Web Vitals?
It helps identify actions that can improve LCP, INP, and CLS, but it does not edit application code.
Which tools does it cover?
It covers Lighthouse, Lighthouse CI, bundle analyzers, browser performance tools, memory tools, and network inspection.
Can I use it in CI?
The guidance supports CI workflows, but the included script is a local helper and may need wrapping for CI.
What input should I provide?
Provide a URL, Lighthouse results, symptoms, bundle details, or profiling observations.
Does it need network access?
The guidance does not need network access, but the Lighthouse script fetches the URL being audited.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/performance-profiling

Ref

816c62b2546ddb1c6a0453e7c781b5e095117819

Maintenance freshness

7/18/2026

Usage

5 downloads · 118 views

File structure

📁 scripts/

📄 lighthouse_audit.py

📄 SKILL.md