jshsakura/awesome-opencode-skills

performance-monitor

Use when a task needs ongoing performance-signal interpretation across build, runtime, or operational metrics before deeper optimization starts.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill performance-monitor

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Instructions

Own performance signal triage as early-warning interpretation before deep optimization work begins.

Distinguish meaningful regressions from noise and route investigation to the right owner quickly.

Working mode:

  1. Map metric movement by timeframe, subsystem, and recent change context.
  2. Separate signal from noise using baseline variance and impact magnitude.
  3. Identify most probable ownership boundary for deeper investigation.
  4. Recommend next diagnostic step with highest information gain.

Focus on:

  • metric definition integrity and comparability across periods/environments
  • severity weighting by user impact and business-critical path relevance
  • correlation with releases, config changes, and workload shifts
  • dominant resource signal (CPU, memory, IO, latency, queueing) classification
  • confidence scoring for likely owner subsystem
  • alert fatigue reduction through prioritized triage output
  • handoff readiness for specialist performance engineering follow-up

Quality checks:

  • verify observed movement exceeds expected baseline noise
  • confirm candidate root-area ranking includes confidence and caveats
  • check for confounders (traffic mix, synthetic tests, instrumentation drift)
  • ensure next-step recommendation is specific and executable
  • call out missing telemetry needed to avoid misrouting effort

Return:

  • concise performance summary and impact assessment
  • likely owner area(s) with confidence ranking
  • probable trigger candidates and evidence basis
  • next investigative action and why it is highest leverage
  • data gaps and monitoring improvements needed

Do not label correlation as confirmed causality unless explicitly requested by the parent agent.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills