perf-fullstack-engineer
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.
使用我的智能体安装
将此请求复制给你的智能体,其中包含权威 Skill 页面和清单。
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.你的智能体仍应展示其计划,并按安全策略请求必要确认。
Agent 可读资源
当 AI Agent、爬虫或脚本需要干净上下文,而不是读取完整页面时,请使用这些链接。
测试它
正在使用“perf-fullstack-engineer”。 Define a baseline for a checkout API expecting 200 requests per second.
预期结果:
Target 200 requests per second with P95 below 500 milliseconds and errors below 0.1 percent. Measure CPU, memory, database latency, and saturation.
正在使用“perf-fullstack-engineer”。 Diagnose rising P99 latency while CPU remains below 50 percent.
预期结果:
- 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.
正在使用“perf-fullstack-engineer”。 Outline a performance report after an optimization.
预期结果:
Compare the same workload before and after the change. Show latency percentiles, throughput, errors, resource use, remaining bottlenecks, and release recommendations.
安全审计
安全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.
风险因素
⚙️ 外部命令 (45)
🌐 网络访问 (8)
🔑 环境变量 (1)
分享与引用此报告
分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据,不判断该 Skill 是否安全。
复制报告链接
https://skillstore.io/skills/zl2023github-perf-fullstack-engineer/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/zl2023github-perf-fullstack-engineer?utm_source=security_passport_badge)HTML 徽章
<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>嵌入卡片
<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>学术引用 (APA · BibTeX · CFF)
APA 引用
zl2023github. (2026). perf-fullstack-engineer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-perf-fullstack-engineer/audits/4BibTeX 引用
@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 评分
评分依据 证据置信度: 中你能构建什么
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.
试试这些提示
Create a performance baseline for [service]. Use [traffic profile], [latency target], [error target], and [environment]. List assumptions and required metrics.
Design a [tool] load test for [workflow]. Include stages, data preparation, checks, thresholds, monitoring, cleanup, and a safe execution sequence.
Analyze these performance results: [results]. Correlate application, host, database, runtime, and network evidence. Rank hypotheses and propose verification steps.
Create a capacity plan for [system] at [forecast load]. Estimate limits, identify architecture risks, compare scaling options, and define regression gates.
最佳实践
- 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.
避免
- 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.
常见问题
Does this skill run performance tests automatically?
Which load-testing tools does it cover?
Can it analyze database performance?
Does it support frontend performance work?
Can I use its thresholds without changes?
Is production load testing recommended?
开发者详情
作者
zl2023github许可证
MIT
Skillstore 修订
r2
版本提示
作者未声明版本。
引用
88a8e9a07f4c54ab105c1c41b6267c287146b07b
维护新鲜度
2026/7/26
使用量
3 次下载 · 1 次浏览
文件结构
📄 SKILL.md