AGENT SKILL

ow-observability

Error tracking, traces, and dependency or image scans inside a product repo that is actually deployed. Not a global Sentry install. Not a scan of a site you do not own.

License 许可
MIT
最近更新
2026-11-13
Stars
★ 1
Forks
0

01 前言 Front Matter

name
ow-observability
description
Error tracking, traces, and dependency or image scans inside a product repo that is actually deployed. Not a global Sentry install. Not a scan of a site you do not own.

03 SKILL.md 正文

Observability

Load with ow-ship-safe when a real app is going out. Source methods: Sentry, OpenTelemetry, Renovate, and Trivy. They are steps in that product repo, not global MCPs and not skills in this method repo.

In the product repo

  1. Sentry, or the tracker that repo already uses, for product errors. One tracker.
  2. OpenTelemetry only when traces must stay vendor-neutral. It does not replace the product tracker.
  3. Renovate or the existing update bot for dependencies. Trivy, or the existing scanner, for images and lockfiles when the repo ships a container or a deployed service.
  4. Secrets stay in the host's secret store. Do not commit a DSN that is a credential. A public client key still follows that product's docs.

Do not

  • Add these packages to the Orchestra method repo.
  • Scan a URL the operator does not own.
  • Claim the tracker is receiving events until a test event was observed.

Preconditions

  • The product repo is the one being deployed, and it already has an owner.

Procedure

  1. The task's paths and acceptance line win.
  2. Use the tracker that repo already has. Add a second tracker only when the contract names it.
  3. Keep secrets in the host store. Send one test event before saying the tracker works.

Output

The config path and the observed test event.

Verify

The test event was seen in the tracker, or the result says it was not.

Skip

Skip for the Orchestra method repo, for a URL the operator does not own, and for a global install.

04 同仓库更多 Skills

mahik504
mahik504/orchestra-workflow

writing-skills

Use when creating new skills, editing existing skills, or verifying skills work before deployment

★ 1
mahik504
mahik504/orchestra-workflow

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

★ 1
mahik504
mahik504/orchestra-workflow

web-design-guidelines

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". Do not load on Plan-only or backend-only jobs.

★ 1
mahik504
mahik504/orchestra-workflow

verification-before-completion

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

★ 1
mahik504
mahik504/orchestra-workflow

using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

★ 1
mahik504
mahik504/orchestra-workflow

unslop

Turns vibecoded, AI-looking UI into a designed interface with its own character. Finds a direction from the product itself, then fixes spacing, color, icons, copy, type, layout, details, visuals and motion in that order, and can generate a real hero visual with an image tool when one is available. Use when the user asks to unslop, polish, clean up or redesign a screen so it stops looking AI-generated, or when a UI shows the usual tells like purple gradients, glows, gradient text, emoji labels, "New ✨" badges, glossy blobs, uppercase tracked labels, pulsing elements or uneven spacing. Works on React, Tailwind, HTML and CSS, for dashboards, apps and landing pages.

★ 1