Agent skill

Observability Analyzer

by majiayu000 in majiayu000/claude-skill-registry

Query and analyze Claude Code observability data (metrics, logs, traces).

Install Observability Analyzer

skills CLI

$ npx skills add majiayu000/claude-skill-registry --skill observability-analyzer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install majiayu000/claude-skill-registry observability-analyzer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/analysis/observability-analyzer .claude/skills/observability-analyzer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "observability-analyzer" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/observability-analyzer into .claude/skills/observability-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "observability-analyzer", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/observability-analyzer

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add majiayu000/claude-skill-registry --skill observability-analyzer -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install majiayu000/claude-skill-registry observability-analyzer --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/analysis/observability-analyzer .agents/skills/observability-analyzer && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "observability-analyzer" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/observability-analyzer into .agents/skills/observability-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "observability-analyzer", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add majiayu000/claude-skill-registry --skill observability-analyzer -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install majiayu000/claude-skill-registry observability-analyzer --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/analysis/observability-analyzer .cursor/skills/observability-analyzer && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "observability-analyzer" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/observability-analyzer into .cursor/skills/observability-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "observability-analyzer", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/majiayu000/claude-skill-registry.git --path skills/analysis/observability-analyzer

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add majiayu000/claude-skill-registry --skill observability-analyzer -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install majiayu000/claude-skill-registry observability-analyzer --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/analysis/observability-analyzer .gemini/skills/observability-analyzer && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "observability-analyzer" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/observability-analyzer into .gemini/skills/observability-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "observability-analyzer", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install majiayu000/claude-skill-registry observability-analyzer

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add majiayu000/claude-skill-registry --skill observability-analyzer -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/analysis/observability-analyzer .github/skills/observability-analyzer && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "observability-analyzer" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/observability-analyzer into .github/skills/observability-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "observability-analyzer", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add majiayu000/claude-skill-registry --skill observability-analyzer -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install majiayu000/claude-skill-registry observability-analyzer --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/analysis/observability-analyzer .opencode/skills/observability-analyzer && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "observability-analyzer" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/observability-analyzer into .opencode/skills/observability-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "observability-analyzer", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: observability-analyzer
GitHub stars: 666
Used in: 1 other repo
Token cost: ~1.6k tokens
SKILL.md length: 353 words
Files: 2
Skills in repo: 971
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Query and analyze Claude Code observability data (metrics, logs, traces).

Analyzing performance
SKILL.md covers Data Sources, Operations, Key Queries and Event Types Reference, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Tasks that involve Observability

What it does

Observability Analyzer is an agent skill from majiayu000/claude-skill-registry. Query and analyze Claude Code observability data (metrics, logs, traces). Use when analyzing performance, costs, errors, tool usage, sessions, conversations, or subagents.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `metadata.json`).

It sits in DevOps & Cloud, covering Observability, Subagents and Monitoring and alerting. It works with Prometheus and OpenTelemetry. The repository describes itself as: Searchable Claude Code skills catalog with source-linked guides and generated registry artifacts. The licence is MIT.

When your agent uses it

Analyzing performance
Tasks that involve Observability
Tasks that involve Subagents

Example prompts

“/observability-analyzer”

What it can do on your machine

Read from SKILL.md and the folder at commit 000116a. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are logql, bash and promql).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Observability Analyzer loads about 1.6k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 353 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~49
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from majiayu000/claude-skill-registry at commit 000116a, republished under its MIT licence (© majiayu000). 353 words, ~1,636 tokens.

Download SKILL.mdSave it as .claude/skills/observability-analyzer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: observability-analyzer
description: Query and analyze Claude Code observability data (metrics, logs, traces). Use when analyzing performance, costs, errors, tool usage, sessions, conversations, or subagents.

Observability Analyzer

Query Claude Code telemetry and generate insights from metrics, logs, and traces. Works with both default OTEL telemetry and enhanced hook-based telemetry.

Data Sources

Source	Job Name	Contains
Default OTEL	`claude_code`	API metrics, token usage, costs
Enhanced Hooks	`claude_code_enhanced`	Sessions, conversations, tools, subagents

Operations

`query-metrics <promql>`

Execute PromQL query against Prometheus.

bash

query-metrics 'sum(claude_code_token_usage)[7d]'

`query-logs <logql>`

Execute LogQL query against Loki.

bash

query-logs '{job="claude_code_enhanced", event_type="tool_call"} | json' --since 24h

`analyze-errors`

Detect and group error patterns from enhanced telemetry.

logql

{job="claude_code_enhanced", event_type="tool_result", status="error"} | json

Output: Error types, frequencies, affected tools, recommendations.

`analyze-performance`

Identify slow operations and response sizes.

logql

{job="claude_code_enhanced", event_type="tool_result"} | json | response_length > 50000

Output: Large responses, estimated token costs, slow patterns.

`analyze-costs`

Calculate token usage from content size estimates.

logql

sum by (repo) (sum_over_time({job="claude_code_enhanced", event_type="context_utilization"} | json | unwrap estimated_session_tokens [24h]))

Output: Token estimates by repo, session costs, projections.

`analyze-tools`

Tool usage statistics and sequences.

logql

sum by (tool) (count_over_time({job="claude_code_enhanced", event_type="tool_call"} | json [24h]))

Output: Call frequency, success rates, tool sequences, common patterns.

`analyze-sessions`

Session lifecycle and duration analytics.

logql

{job="claude_code_enhanced", event_type="session_end"} | json

Output: Session durations, turn counts, tools per session, termination reasons.

`analyze-conversations`

Conversation and prompt analytics.

logql

sum by (pattern) (count_over_time({job="claude_code_enhanced", event_type="user_prompt"} | json [24h]))

Output: Prompt patterns (question/debugging/creation/ultrathink), turn distribution.

`analyze-subagents`

Subagent/Task tool usage.

logql

{job="claude_code_enhanced", event_type="tool_call", tool="Task"} | json

Output: Subagent types used, completion rates, parallel execution patterns.

`analyze-skills`

Skill invocation analytics.

logql

sum by (skill_name) (count_over_time({job="claude_code_enhanced", event_type="skill_usage"} | json [24h]))

Output: Most used skills, skill usage by repo, trends.

`analyze-context`

Context window utilization.

logql

{job="claude_code_enhanced", event_type="context_utilization"} | json | context_percentage > 50

Output: High utilization sessions, compaction events, token efficiency.

`analyze-repos`

Repository/project activity.

logql

sum by (repo, tool) (count_over_time({job="claude_code_enhanced", event_type="tool_call"} | json [24h]))

Output: Activity per repo, tool usage by project, branch patterns.

`generate-report`

Comprehensive analysis report (all dimensions). Output: Markdown report with errors, performance, costs, sessions, conversations, tools.

Show full SKILL.md (137 more words)Show less

Key Queries

Enhanced Telemetry (Loki)

logql

# All events (last hour)
{job="claude_code_enhanced"} | json

# Session analytics
{job="claude_code_enhanced", event_type="session_end"} | json | duration_seconds > 300

# Tool errors
{job="claude_code_enhanced", event_type="tool_result", status="error"} | json

# High context usage
{job="claude_code_enhanced", event_type="context_utilization"} | json | context_percentage > 75

# Subagent spawns
{job="claude_code_enhanced", event_type="tool_call", tool="Task"} | json

# Skill invocations
{job="claude_code_enhanced", event_type="skill_usage"} | json

# Prompt patterns
{job="claude_code_enhanced", event_type="user_prompt"} | json | pattern="ultrathink"

# Tool sequences
{job="claude_code_enhanced", event_type="tool_call"} | json | line_format "{{.tool_name}} → {{.previous_tool}}"

# Context compaction
{job="claude_code_enhanced", event_type="context_compact"} | json

# Permission requests
{job="claude_code_enhanced", event_type="permission_request"} | json

Default OTEL (Prometheus)

promql

# Total token usage (7 days)
sum(increase(claude_code_token_usage[7d]))

# Error rate by tool
sum by (tool_name) (rate(claude_code_tool_result{status="failure"}[1h]))

# P95 tool latency
histogram_quantile(0.95, claude_code_tool_duration_bucket)

# Daily costs
sum(increase(claude_code_cost_usage[24h]))

Event Types Reference

Event Type	Description	Key Fields
`session_start`	Session initialization	source, permission_mode
`session_end`	Session termination	duration_seconds, turn_count, tools_used
`user_prompt`	User message submitted	pattern, prompt_length, estimated_tokens
`tool_call`	Tool invocation	tool_name, tool_details, sequence_position
`tool_result`	Tool completion	status, response_length, is_error
`skill_usage`	Skill invoked	skill_name
`context_utilization`	Token estimate	estimated_session_tokens, context_percentage
`context_compact`	Compaction event	trigger (manual/auto)
`subagent_complete`	Task agent finished	total_subagents
`permission_request`	Permission dialog	notification_type
`notification`	System notification	notification_type

Grafana Dashboards

Claude Code Overview - High-level metrics
Tool Performance - Tool latencies and success rates
Cost Analysis - Token usage and costs
Error Tracking - Error patterns and trends
Session Analytics - Session-level insights
Enhanced Analytics - Model/skill/context/repo tracking
Deep Analytics - Comprehensive conversation and tool analysis

Access: http://localhost:3000 (admin/admin)

Scripts

scripts/query-prometheus.sh - PromQL query helper
scripts/query-loki.sh - LogQL query helper
scripts/analyze-errors.sh - Error analysis automation
scripts/analyze-sessions.sh - Session analytics
scripts/generate-report.sh - Full analysis report

Files

SKILL.md and 1 other file in skills/analysis/observability-analyzer of majiayu000/claude-skill-registry.

SKILL.md
metadata.json

Open the folder on GitHubat commit 000116a

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in majiayu000/claude-skill-registry, which our catalogue first saw on October 7, 2026.

NeverSight/learn-skills.devdata/skills-md/adaptationio/skrillz/observability-analyzer

Compare with similar skills

Observability Analyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Observability Analyzer compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Observability Analyzer this skillmajiayu000/claude-skill-registry	666	1 repos	~1.6k	Automated safety check: Pass	MIT	today
Developing Funboost Mixinydf0509/funboost	892	—	~2.1k	Automated safety check: Pass	None	1 mo ago
Archestra Dev Observabilityarchestra-ai/archestra	4.3k	—	~1.2k	Automated safety check: Pass	Custom licence	today
Frontmcp Observabilityagentfront/frontmcp	146	—	~4.6k	Automated safety check: Pass	Apache-2.0	today
Monitoring Observabilityahmedasmar/devops-claude-skills	203	—	~3.9k	Automated safety check: Pass	None	5 mo ago
Observability Architecturemajiayu000/litellm-rs	116	—	~1.3k	Automated safety check: Pass	MIT	today

Similar skills

Developing Funboost Mixin
ydf0509/funboost
当需要为 funboost 创建 Consumer 或 Publisher 的 Mixin 扩展类时使用。触发场景：添加监控、熔断、限流、链路追踪等横切关注点，编写自定义前置/后置处理钩子。关键词：mixin, consumeroverridecls, publisheroverridecls, ConsumerMixin, 自定义消费者, hook, 拦截器, 熔断器, 监控…
892 GitHub stars~2.1k tokensUpdated 1 mo ago
DevOps & CloudAuto-check passed
Archestra Dev Observability
archestra-ai/archestra
A skill your agent uses when changing Archestra tracing, metrics, OpenTelemetry, Tempo, Grafana, Prometheus, LLM/MCP spans, observability labels, or local observability setup.
4.3k GitHub stars~1.2k tokensUpdated today
DevOps & CloudAuto-check passed
Frontmcp Observability
agentfront/frontmcp
A skill your agent uses when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server.
146 GitHub stars~4.6k tokensUpdated today
DevOps & CloudAuto-check passed
Monitoring Observability
ahmedasmar/devops-claude-skills
Monitoring and observability strategy, implementation, and troubleshooting.
203 GitHub stars~3.9k tokensUpdated 5 mo ago
DevOps & CloudAuto-check passed
Observability Architecture
majiayu000/litellm-rs
LiteLLM-RS Observability Architecture. An agent skill from majiayu000/litellm-rs.
116 GitHub stars~1.3k tokensUpdated today
DevOps & CloudAuto-check passed
Monitoring Expert
Jeffallan/claude-skills
Sets up application monitoring: structured logs, Prometheus metrics, OpenTelemetry tracing, Grafana dashboards, alert rules and load tests with k6 or Artillery.
12k GitHub stars~1.6k tokensUpdated 3 days ago
DevOps & CloudAuto-check passed

Questions about Observability Analyzer

What does Observability Analyzer do?

Query and analyze Claude Code observability data (metrics, logs, traces). Observability Analyzer is an agent skill from majiayu000/claude-skill-registry. Query and analyze Claude Code observability data (metrics, logs, traces).

When should I use Observability Analyzer?

Observability Analyzer fits situations like: analyzing performance; tasks that involve Observability; tasks that involve Subagents.

How do I install Observability Analyzer in Claude Code?

Run `npx skills add majiayu000/claude-skill-registry --skill observability-analyzer -a claude-code`. Or copy the skill folder (skills/analysis/observability-analyzer in majiayu000/claude-skill-registry) into .claude/skills/observability-analyzer in your project. Claude Code loads it when a task matches its description.

How do I install Observability Analyzer in Codex?

Run `npx skills add majiayu000/claude-skill-registry --skill observability-analyzer -a codex`. Or copy the skill folder (skills/analysis/observability-analyzer in majiayu000/claude-skill-registry) into .agents/skills/observability-analyzer in your project. Codex loads it when a task matches its description.

Can I use Observability Analyzer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add majiayu000/claude-skill-registry --skill observability-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/observability-analyzer, .gemini/skills/observability-analyzer, .github/skills/observability-analyzer and .opencode/skills/observability-analyzer in your project.

What does Observability Analyzer need to run?

SKILL.md names no scripts, command-line tools or credentials: Observability Analyzer is instructions for the agent only.

Does Observability Analyzer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Observability Analyzer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Observability Analyzer use?

Observability Analyzer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Observability Analyzer use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Observability Analyzer?

Skills that share tags, products or a category with Observability Analyzer: Developing Funboost Mixin (ydf0509/funboost, 892 stars), Archestra Dev Observability (archestra-ai/archestra, 4.3k stars), Frontmcp Observability (agentfront/frontmcp, 146 stars) and Monitoring Observability (ahmedasmar/devops-claude-skills, 203 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Observability Analyzer?

majiayu000 (a GitHub user) maintains it in majiayu000/claude-skill-registry, which has 666 GitHub stars. The repository holds 971 skills in this directory. The repository was last updated on October 7, 2026.

Source: majiayu000/claude-skill-registry on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Observability Analyzer

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Observability Analyzer

Data Sources

Operations

query-metrics <promql>

query-logs <logql>

analyze-errors

analyze-performance

analyze-costs

analyze-tools

analyze-sessions

analyze-conversations

analyze-subagents

analyze-skills

analyze-context

analyze-repos

generate-report

Key Queries

Enhanced Telemetry (Loki)

Default OTEL (Prometheus)

Event Types Reference

Grafana Dashboards

Scripts

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from majiayu000/claude-skill-registry

Related

Questions about Observability Analyzer

`query-metrics <promql>`

`query-logs <logql>`

`analyze-errors`

`analyze-performance`

`analyze-costs`

`analyze-tools`

`analyze-sessions`

`analyze-conversations`

`analyze-subagents`

`analyze-skills`

`analyze-context`

`analyze-repos`

`generate-report`