메뉴
Query Better Stack Telemetry logs — errors, warnings, full-text search, request traces, tail, stats. Use whenever JP wants to look at logs or investigate the context around a failure (what happened around an error, logs for a request id, recent errors, etc.).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
How to invoke the Codex CLI (`codex`) from the shell. Read this BEFORE shelling out to `codex` for any nontrivial task — it covers calling the real binary (not the Superconductor wrapper, which hangs) and capturing output with `-o` so the answer doesn't get buried in the agent-session stream.
Interact with Google Docs & Drive — read, edit, search, comment, share, create docs, list/pull/push content. Use whenever JP wants to read or modify a Google Doc or Drive file (fetch a doc's text, leave a comment, find a file, etc.).
Batch-process Asana tickets — bugs and small / well-specified features — tagged jpa-bugfixes-today into PRs. Spawns a subagent per ticket in parallel worktrees with Codex plan-review and diff-review.
Interact with Asana — tasks, My Tasks, projects, sections, tags, users, workspaces. Use whenever JP wants to read or modify Asana data (look up or edit a task, list My Tasks, comment, find a project, etc.).
Interact with Sentry — issues, errors, events, traces, releases, projects, dashboards. Use whenever JP wants to read or modify Sentry data (triage an issue, look up an error, inspect a trace, manage a release, etc.).
Run parallel local + remote PR reviews, then synthesize all findings
| name | betterheap |
| description | Query Better Stack Telemetry logs — errors, warnings, full-text search, request traces, tail, stats. Use whenever JP wants to look at logs or investigate the context around a failure (what happened around an error, logs for a request id, recent errors, etc.). |
Use the betterheap CLI — it queries Better Stack Telemetry logs as one continuous window across the live hot buffer and the S3 archive, so the time range you ask for is the time range you get.
Run betterheap -h for the top-level commands, then betterheap <command> --help to drill in. Add --format json (or ndjson) for machine-readable output, and betterheap schema dumps the field map and output fields. Useful starting points: betterheap errors --since 7d, betterheap search "<text>" --since 14d, betterheap trace <request-id> (all logs for one request, merged by time).
When investigating a Sentry failure, reach for this to pull the surrounding logs.
