本文へ移動
cccskills
無料GitHub で公開

observability-baseline

Scaffold-time observability so a shipped product is not blind in prod from day one — error capture (Sentry), request-id structured logging, and /healthz + /readyz endpoints. stack-baseline pins Sentry but nothing wires it; this is the wiring. Loaded by app-scaffolder (bake into the scaffold), infra-provisioner (prod env + probes), and consumed by l3-support (traces) and devops (deploy gate).

avelikiy/great_cto
インストール方法を見る

含まれるファイル（1）

  • SKILL.md3.0 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

observability-baseline

stack-baseline names Sentry and wires it nowhere — so every shipped product's first prod incident is invisible, and l3-support triages blind. This skill makes three things exist at scaffold time. Defaults baked in; no founder question.

1. Error capture (Sentry)

  • instrumentation.ts (Next.js) / SDK init at process start; DSN from SENTRY_DSN env (never hardcoded).
  • CI uploads source maps on release so stack traces are readable (release = git sha).
  • Capture unhandled rejections + a global error boundary on the client.

2. Request-id structured logging

  • A logger that emits JSON (not console.log prose) with a per-request request_id (generate at the edge, propagate via header/async-local-storage).
  • Levels: error / warn / info / debug — diagnostics go to stderr, never mixed into user-facing stdout. (Same discipline as the CLI logging gap, DEEPEN d94.)
  • One log line per request with: request_id, method, path, status, latency_ms.

3. Health endpoints

  • GET /healthz — liveness (process up). GET /readyz — readiness (deps reachable: db, cache). Cheap, unauthenticated, no PII.
  • These are what infra-provisioner probes and what a load balancer checks.

Wiring (a skill is shelfware unless a consumer loads it)

ConsumerWhat it does with this skill
app-scaffolderbakes instrumentation.ts + the JSON logger + /healthz+/readyz into the generated app; adds SENTRY_DSN to .env.example
infra-provisionersets SENTRY_DSN in the prod env list; points the platform health probe at /readyz; records the Sentry project in PROVISION
l3-supportfirst triage step reads Sentry + the request-id logs (a trace now exists to read)
devopsdeploy gate fails if /readyz doesn't return 200 post-deploy

Output

A scaffolded app where the first prod error is captured, every request is traceable by id, and the platform can health-check it. Record the Sentry project + endpoints in docs/infra/PROVISION-{slug}.md. Done = the three pieces exist AND are wired into the prod env, not just present in code.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

aesthetic-instrument

無料

great_cto's own committed aesthetic — the instrument panel. Dark five-step surface ladder, exactly one accent, two faces divided by MEANING (Geist speaks, Geist Mono is machine-truth), tabular numerals, and a dash that is not a nought. Twelve checkable rules measured from packages/board and greatcto.systems, not designed for this file. Use when building or extending any great_cto surface — the board, the site, a report, a share page.

日本語の概要は準備中です。原文の説明を表示しています。

avelikiy/great_cto1032026年10月12日 更新

anti-patterns

無料

Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).

日本語の概要は準備中です。原文の説明を表示しています。

avelikiy/great_cto1032026年10月12日 更新

anydesign

無料

Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does this site use', 'how is this built'. Also for single elements: 'copy this navbar', 'recreate this illustration', 'give me a prompt to regenerate this graphic' — element mode outputs a focused element.md, with token-grounded image-model prompts when the element is visual art. If the user brings any visual source and wants to understand it at a design level — this skill should activate.

日本語の概要は準備中です。原文の説明を表示しています。

avelikiy/great_cto1032026年10月12日 更新

archetype-review-base

無料

Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.

日本語の概要は準備中です。原文の説明を表示しています。

avelikiy/great_cto1032026年10月12日 更新

brainstorming

無料

Structured idea generation + multi-LLM debate for the product-owner stage. Diverge (generate genuinely different bets), debate (a 4-persona panel on 4 models argues over 2 rounds), converge (synthesize a recommendation). Used by product-owner before architect; available to architect for design-space exploration.

日本語の概要は準備中です。原文の説明を表示しています。

avelikiy/great_cto1032026年10月12日 更新

codex-host

無料

Run the great_cto controlled Codex lifecycle with controller-owned writes, verifier evidence, human gates and optional artifact release.

日本語の概要は準備中です。原文の説明を表示しています。

avelikiy/great_cto1032026年10月12日 更新

avelikiy のスキルをすべて見る

このスキルの問題を報告する