axiom-sre 是做什么的？
专家级 SRE 调查员，用于事件排查和调试。采用假设驱动方法和系统化分类。可在可用时查询 Axiom 可观测性数据。适用于事件响应、根因分析、生产调试或日志调查。
专家级 SRE 调查员，用于事件排查和调试。采用假设驱动方法和系统化分类。可在可用时查询 Axiom 可观测性数据。适用于事件响应、根因分析、生产调试或日志调查。
axiomhq/axiom-sre 是一个专为站点可靠性工程师（SRE）设计的 AI 技能，专注于事件处理和调试场景。它采用假设驱动的方法论和系统化的故障分类流程，帮助用户快速定位和解决问题。该技能的一个关键优势是能够与 Axiom 可观测性平台集成，当 Axiom 数据可用时，可以直接查询日志、指标和事件数据，从而加速根因分析。它适用于多种任务，包括事件响应、根因分析、生产环境调试以及日志调查。该技能在 Claude Code、Cursor 和 Codex 等 AI 代理平台上运行，通过结构化的分析步骤和智能查询建议，显著提升 SRE 的故障排查效率和准确性。
npx skills add https://github.com/axiomhq/skills/tree/main/skills/axiom-sreInstalled? Explore more 研究与数据分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
专家级 SRE 调查员，用于事件排查和调试。采用假设驱动方法和系统化分类。可在可用时查询 Axiom 可观测性数据。适用于事件响应、根因分析、生产调试或日志调查。
This repo contains 2 individual skills — each has its own dedicated page.
Designs and builds Axiom dashboards via API. Covers chart types, APL and metrics/MPL query patterns, SmartFilters, layout, and configuration options. Use when creating dashboards, migrating from Splunk, or configuring chart options.
Runs metrics queries against Axiom MetricsDB via scripts. Discovers available metrics, tags, and tag values. Use when asked to query metrics, explore metric datasets, check metric values, or investigate OTel metrics data.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.