payment-engineer
77Design Reliable Payment Systems
Payment teams need consistent designs for transactions, channels, reconciliation, security, and failure handling. This skill provides structured guidance, examples, and review checklists.
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.
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
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.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Usando "perf-fullstack-engineer". Define a baseline for a checkout API expecting 200 requests per second.
Resultado esperado:
Target 200 requests per second with P95 below 500 milliseconds and errors below 0.1 percent. Measure CPU, memory, database latency, and saturation.
Usando "perf-fullstack-engineer". Diagnose rising P99 latency while CPU remains below 50 percent.
Resultado esperado:
Usando "perf-fullstack-engineer". Outline a performance report after an optimization.
Resultado esperado:
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.
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
https://skillstore.io/skills/zl2023github-perf-fullstack-engineer/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/zl2023github-perf-fullstack-engineer?utm_source=security_passport_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><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>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@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}
}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"
Define service targets, select test scenarios, and produce a repeatable baseline before a release.
Correlate latency, resource, runtime, database, and application signals to prioritize likely bottlenecks.
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.
Autor
zl2023githubLicencia
MIT
Revisión de Skillstore
r2
Aviso de versión
El autor no declaró una versión.
Ref.
88a8e9a07f4c54ab105c1c41b6267c287146b07b
Actualidad del mantenimiento
26/7/2026
Uso
3 descargas · 1 vistas
Estructura de archivos
📄 SKILL.md
Design Reliable Payment Systems
Payment teams need consistent designs for transactions, channels, reconciliation, security, and failure handling. This skill provides structured guidance, examples, and review checklists.
Build and Optimize Search Systems
Search teams need reliable guidance across indexing, ranking, semantic retrieval, and evaluation. This skill provides practical workflows and examples for building and improving search systems.
Build Reliable Business Intelligence Analysis
Business teams often lack consistent metrics and repeatable analysis workflows. This skill guides SQL, Python, dashboards, experiments, and automated reporting from requirements to delivery.
Evaluate Technology Choices with Clear Tradeoffs
Technology choices often hide tradeoffs across performance, cost, reliability, operations, and team readiness. This skill compares candidates, recommends an option, and defines proof-of-concept checks.
Generate Clear Software Architecture Documents
Architecture decisions often remain scattered across requirements, discussions, and diagrams. This skill organizes them into consistent Markdown documents for implementation and review.
Build Reliable Data Pipelines and Warehouses
Data teams need dependable pipelines across fragmented platforms. This skill designs implementation-ready batch, streaming, modeling, orchestration, and quality workflows.
Crea API backend fiables
por davila7
Los equipos de backend necesitan una orientación coherente sobre arquitectura, bases de datos y seguridad en todos los servicios. Esta skill proporciona prompts específicos, referencias y scripts auxiliares para el diseño de API y la revisión del backend.
Diagnostica errores de producción más rápido
por sickn33
Depurar errores de producción es lento cuando los logs, las trazas y los releases están dispersos. Esta skill guía a Claude, Codex y Claude Code mediante un análisis estructurado de causa raíz y mejoras de observabilidad.
Depurar problemas de producción con evidencia
por sickn33
Los fallos complejos son difíciles de triar cuando los registros, trazas y evidencia del código están dispersos. Esta habilidad guía a Claude, Codex y Claude Code mediante un diagnóstico estructurado, planificación de correcciones y validación.
Diseña APIs de backend escalables
por sickn33
Las decisiones de arquitectura de backend pueden crear APIs frágiles y límites de servicio poco claros. Esta skill guía contratos de API, descomposición de servicios, resiliencia, observabilidad y planificación de despliegues.
Crear agentes LangChain de producción
por sickn33
Los agentes LangChain de producción necesitan una arquitectura clara, memoria, evaluación y observabilidad. Esta skill guía a Claude, Codex y Claude Code a través de patrones de LangGraph, herramientas asíncronas, RAG, pruebas y despliegue.
Diagnostica errores con depuración inteligente
por sickn33
Depurar fallos de producción es lento cuando la evidencia está dispersa entre logs, trazas y código. Esta habilidad guía la clasificación inicial, la priorización de hipótesis, la instrumentación segura, las correcciones y la validación.