Skills perf-fullstack-engineer

📦

perf-fullstack-engineer

Name: perf-fullstack-engineer
Author: zl2023github

Content revision r2 Safe ⚙️ External commands🌐 Network access🔑 Env variables

Diagnose and Improve Full-Stack Performance

Full-stack teams often lack a repeatable way to measure performance and locate bottlenecks. This skill provides testing workflows, diagnostic commands, optimization guidance, and report structures.

Supports: Claude Codex Code(CC)

🥉 77 Bronze

Install with my Agent

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

Agent request

Review the Skillstore skill "perf-fullstack-engineer" from https://skillstore.io/skills/zl2023github-perf-fullstack-engineer.md and its manifest at https://skillstore.io/api/skills/zl2023github-perf-fullstack-engineer/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/zl2023github-perf-fullstack-engineer.md Signed manifest GET /api/skills/zl2023github-perf-fullstack-engineer/manifest Signed lockfile GET /api/skills/zl2023github-perf-fullstack-engineer/lockfile

Test it

Using "perf-fullstack-engineer". Define a baseline for a checkout API expecting 200 requests per second.

Expected outcome:

Target 200 requests per second with P95 below 500 milliseconds and errors below 0.1 percent. Measure CPU, memory, database latency, and saturation.

Using "perf-fullstack-engineer". Diagnose rising P99 latency while CPU remains below 50 percent.

Expected outcome:

Primary hypotheses: database lock waits, connection pool saturation, external dependency latency, or garbage collection pauses.
Next checks: correlate traces, pool metrics, slow queries, lock activity, dependency timing, and runtime pause data.

Using "perf-fullstack-engineer". Outline a performance report after an optimization.

Expected outcome:

Compare the same workload before and after the change. Show latency percentiles, throughput, errors, resource use, remaining bottlenecks, and release recommendations.

Security Audit

Safe

v4 • 7/23/2026 Open versioned report

The skill is readable Markdown guidance with no executable package, prompt injection, credential collection, obfuscation, or covert data transfer. Static alerts primarily misread Markdown backticks, Chinese text, placeholders, localhost URLs, and documented developer commands as dangerous behavior.

Files scanned

329

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (45)

🌐 Network access (8)

SKILL.md:78 SKILL.md:78 SKILL.md:182 SKILL.md:183 SKILL.md:218 SKILL.md:224 SKILL.md:240 SKILL.md:317

🔑 Env variables (1)

SKILL.md:224

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

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

Copy report link

https://skillstore.io/skills/zl2023github-perf-fullstack-engineer/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/zl2023github-perf-fullstack-engineer/security.svg)](https://skillstore.io/skills/zl2023github-perf-fullstack-engineer?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/zl2023github-perf-fullstack-engineer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/zl2023github-perf-fullstack-engineer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/zl2023github-perf-fullstack-engineer.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

zl2023github. (2026). perf-fullstack-engineer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-perf-fullstack-engineer/audits/4

BibTeX citation

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

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Establish a Performance Baseline

Define service targets, select test scenarios, and produce a repeatable baseline before a release.

Diagnose a Slow Application

Correlate latency, resource, runtime, database, and application signals to prioritize likely bottlenecks.

Plan Capacity for Growth

Model peak traffic, identify system limits, and organize scaling recommendations with measurable acceptance criteria.

Try These Prompts

Define a Baseline

Create a performance baseline for [service]. Use [traffic profile], [latency target], [error target], and [environment]. List assumptions and required metrics.

Design a Load Test

Design a [tool] load test for [workflow]. Include stages, data preparation, checks, thresholds, monitoring, cleanup, and a safe execution sequence.

Analyze a Bottleneck

Analyze these performance results: [results]. Correlate application, host, database, runtime, and network evidence. Rank hypotheses and propose verification steps.

Build a Capacity Plan

Create a capacity plan for [system] at [forecast load]. Estimate limits, identify architecture risks, compare scaling options, and define regression gates.

Best Practices

Confirm target ownership, isolate the test environment, and obtain approval before generating load.
Warm the system, monitor every layer, increase load gradually, and repeat comparable tests.
Base conclusions on correlated metrics and document assumptions, environment differences, and data limitations.

Avoid

Do not run stress tests against production or third-party systems without explicit authorization.
Do not optimize from averages alone; inspect percentiles, errors, saturation, and resource trends.
Do not change multiple variables between baseline and comparison runs.

Frequently Asked Questions

Does this skill run performance tests automatically?

No. It provides workflows, examples, diagnostics, and report structures. Execution requires installed tools, adapted targets, and user authorization.

Which load-testing tools does it cover?

It covers k6, JMeter, Locust, wrk, Vegeta, and Apache Bench, with guidance for selecting tools by scenario.

Can it analyze database performance?

Yes. It covers query plans, slow queries, active sessions, locks, indexing, connection pools, and common MySQL and PostgreSQL diagnostics.

Does it support frontend performance work?

Yes. It covers Lighthouse, browser diagnostics, code splitting, lazy loading, virtual lists, image optimization, caching, and content delivery networks.

Can I use its thresholds without changes?

No. Example thresholds are starting points. Set targets from business requirements, service objectives, historical baselines, and environment constraints.

Is production load testing recommended?

No. Use an isolated representative environment unless your organization has an approved production testing process with safeguards and monitoring.

Developer Details

Author

zl2023github

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/zl2023github/software-engineer-skills/tree/main/software-engineering/perf-fullstack-engineer

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

3 downloads · 1 views

File structure

📄 SKILL.md