無料GitHub で公開

observal-ops

Inspects Observal traces, sessions, rankings, feedback, telemetry health, logs, and Agent insight reports. Use when the user wants operational evidence, current activity, telemetry diagnosis, ratings, report generation, regression analysis, or recommendations grounded in Agent usage.

Observal/Observal

インストール方法を見る

含まれるファイル（3）

SKILL.md2.6 KB
references/insight-reports.md3.4 KB
references/operational-workflows.md2.2 KB

SKILL.md（原文）

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

Observing Observal

Execution contract

Execute commands with a 60 second timeout. Use a longer timeout only for report generation or an intentional stream.
Use machine output by default: add --output json whenever supported. Parse list envelopes, finite objects, and JSON Lines separately.
Run --help before acting when a path or flag is uncertain.
Start with the narrowest read that answers the question. Do not generate a new report when a completed report already suffices.
Ground every conclusion in returned fields, report period, and sample size. Distinguish missing data from healthy data.
Verify rating mutations and report generation results.
Never repeat secrets or sensitive trace and log content unless the user explicitly requests the specific data and is authorized.
After an uncertain rating or report-generation failure, read current state before retrying.

Choose the workflow

User intent	Read
Sessions, traces, rankings, ratings, telemetry, or logs	Operational workflows
Agent health, friction, costs, versions, regressions, or suggestions	Insight reports

Read the selected reference completely before executing.

Analysis rules

A zero exit status from telemetry diagnosis can still contain issues or warnings. Read the JSON health fields.
No events is not automatically a hook problem. Check authentication, server reachability, local outbox, and hook state in that order.
Quote report evidence accurately and say when session count is thin.
Only component_ref proves an insight suggestion maps to a Registry component. Never reconstruct a component identity from prose.
Lead with reuse suggestions before create-new suggestions.
For logs and traces, summarize the minimum sensitive content needed to answer the question.

Completion

Report the time range, filters, counts, health state, strongest evidence, uncertainty, and concrete next action. Do not present popularity fallback or sparse reports as personalized certainty.

レビュー

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

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

同じリポジトリのスキル

概要と使いどころ

observal

無料

Use when starting any task the organization may already have an approved skill, prompt, MCP server, or Agent for: reviewing code, a commit, a diff, or a pull request; writing tests or documentation; querying a database, API, or service; automating a browser or web page; running untrusted code; connecting to a SaaS tool; drafting, researching, or any other substantive work. The user will not mention Observal: the task type is the trigger. Check what is already installed, then run observal discover search as the first action, before reading the repository or working from scratch. Also use when the user wants to log in, configure Observal, inspect local harness setup, share or open a repository Agent share, manage a teamspace or invitation, process inbox items, check installed registry items, or call an endpoint without a dedicated command.

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