Token导航 LogoToken导航

Agent Skill · 运维和基础设施

error-detector(错误检测器)

error-detector 用于记录任务执行中的错误、用户纠正、经验和能力缺口,适合在 Codex、Claude、Cursor、Gemini CLI 中希望让 Agent 持续沉淀问题、修正和最佳实践时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

error-detector 是运维和基础设施类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证为 MIT,第三方扫描已通过,按安装量在运维和基础设施类的 2,449 个 Skill 里排第 605。

总安装 2,352周安装 73GitHub Stars 76下载 824核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:error-detector(错误检测器)
来源仓库:https://github.com/404kidwiz/claude-supercode-skills
仓库路径:skills/error-detector
安装命令:
npx skills add https://github.com/404kidwiz/claude-supercode-skills --skill error-detector
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/404kidwiz/claude-supercode-skills --skill error-detector

这个 Skill 是做什么的

运维和基础设施类 Skill 处理部署、监控、日志和云资源,多数需要较高的执行权限。

error-detector 提供静态与动态代码分析能力,用于主动识别软件缺陷和安全漏洞。适用于 Codex、Claude、Cursor、Gemini CLI 中进行内存泄漏检测、异常模式分析和性能瓶颈排查。支持日志监控、反模式识别和预防性错误检测,提升代码健壮性。

安装方式:通过 npx 从 GitHub 仓库添加,需确认是否允许扫描项目文件和运行轻量分析。依赖本地代码访问权限,无法在无源码或只读环境下生效。

来源仓库内路径:skills/error-detector

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/404kidwiz/claude-supercode-skills --skill erro…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

error-detector 怎么安装?

在终端执行 npx skills add https://github.com/404kidwiz/claude-supercode-skills --skill error-detector。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

error-detector 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

error-detector 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

error-detector 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

error-detector 用的人多吗?

公开数据是累计安装 2,352 次,近一周安装 73 次,下载 824 次,GitHub 76 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

error-detector 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理运维和基础设施类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

运维和基础设施类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
brainstorming

头脑风暴 · Codex、Claude

3,148,776173,131操作浏览器MIT通过
copywriting

文案写作 · Codex、Claude

1,996,72425,583需要联网MIT通过
openclaw-secure-linux-cloud

OpenClaw secure linux cloud 命令行 · Codex、Claude

1,853,08840接触敏感数据未明确未通过
xget

xget 命令行 · Codex、Claude

1,799,28040执行命令未明确未通过
requesting-code-review

代码审查请求 · Codex、Claude

1,590,144173,103权限未标注MIT通过
error-detector

错误检测器 · 本页

2,35276需要联网MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Error Detector Skill

Purpose

Provides error analysis and pattern detection expertise specializing in proactive identification of software defects, code analysis, and system behavior monitoring. Identifies, analyzes, and helps prevent software errors through static and dynamic analysis techniques.

When to Use

  • Performing static code analysis and anti-pattern detection
  • Analyzing runtime errors and exception patterns
  • Detecting memory leaks and performance bottlenecks
  • Monitoring and analyzing error logs
  • Identifying security vulnerabilities through code patterns
  • Conducting proactive error prevention analysis

Overview

Specialized in error analysis, pattern detection, and proactive identification of software defects through code analysis, log monitoring, and system behavior analysis.

Error Detection Methodologies

Static Analysis

  • Code pattern recognition
  • Anti-pattern identification
  • Complexity analysis
  • Security vulnerability detection
  • Performance bottleneck identification

Dynamic Analysis

  • Runtime error monitoring
  • Exception pattern analysis
  • Memory leak detection
  • Performance profiling
  • Resource utilization tracking

Log-Based Analysis

# Example patterns for error detection
grep -r "ERROR\|FATAL\|CRITICAL" logs/ --include="*.log" --include="*.txt"
grep -r "exception\|error\|failed" src/ --include="*.js" --include="*.py" --include="*.java"
grep -r "TODO\|FIXME\|HACK" src/ --include="*.*" --exclude-dir=node_modules

Error Categories & Patterns

Common Programming Errors

  • Null pointer exceptions
  • Array index out of bounds
  • Type conversion errors
  • Resource leak issues
  • Concurrency problems

Logic Errors

  • Off-by-one errors
  • Incorrect conditionals
  • Loop termination issues
  • State management problems
  • Data validation failures

Performance Errors

  • Inefficient algorithms
  • Memory optimization issues
  • Database query problems
  • Network timeout handling
  • Resource contention

Advanced Detection Techniques

Machine Learning-Based Detection

  • Anomaly detection in system behavior
  • Pattern recognition in error logs
  • Predictive failure modeling
  • Classification of error types
  • Automated root cause analysis

Statistical Analysis

  • Error frequency distribution
  • Time series analysis of failures
  • Correlation analysis between components
  • Regression testing failure patterns
  • Performance degradation detection

Code Complexity Metrics

  • Cyclomatic complexity analysis
  • Cognitive complexity assessment
  • Maintainability index calculation
  • Technical debt quantification
  • Code duplication detection

Error Analysis Frameworks

Root Cause Analysis (RCA)

  • Five Whys methodology
  • Fishbone diagram analysis
  • Pareto analysis for prioritization
  • Fault tree analysis
  • Change impact assessment

Error Classification Systems

  • Severity categorization
  • Priority assignment frameworks
  • Impact assessment matrices
  • Frequency-based prioritization
  • Business risk evaluation

Pattern Recognition

  • Repetitive error identification
  • Error clustering algorithms
  • Sequence pattern analysis
  • Correlation detection
  • Temporal pattern analysis

Monitoring & Alerting

Real-Time Monitoring

  • System health dashboards
  • Error rate monitoring
  • Performance threshold alerts
  • Log aggregation and analysis
  • Automated incident response

Predictive Analysis

  • Failure prediction models
  • Early warning systems
  • Trend analysis and forecasting
  • Capacity planning alerts
  • Proactive maintenance scheduling

Logging Best Practices

  • Structured logging implementation
  • Log level optimization
  • Sensitive data protection
  • Log rotation policies
  • Centralized log management

Error Prevention Strategies

Code Quality Improvement

  • Peer review processes
  • Automated testing coverage
  • Static analysis tools integration
  • Code style enforcement
  • Documentation standards

Development Process Optimization

  • Test-driven development (TDD)
  • Continuous integration practices
  • Automated deployment pipelines
  • Rollback procedures
  • Feature flag implementation

System Design Patterns

  • Circuit breaker patterns
  • Retry mechanisms
  • Graceful degradation
  • Fallback systems
  • Redundancy implementation

Error Detection Tools & Integration

Static Analysis Tools

  • ESLint for JavaScript/TypeScript
  • Pylint for Python
  • SonarQube for multi-language analysis
  • Checkstyle for Java
  • FxCop for C#

Dynamic Monitoring Tools

  • Application Performance Monitoring (APM)
  • Error tracking services (Sentry, Bugsnag)
  • Log management systems (ELK stack)
  • Distributed tracing tools
  • Infrastructure monitoring

Custom Detection Scripts

  • Error pattern matching
  • Anomaly detection algorithms
  • Automated regression testing
  • Performance benchmarking
  • Data validation checks

Error Response & Resolution

Incident Management

  • Error triage procedures
  • Escalation protocols
  • Communication templates
  • Resolution tracking
  • Post-incident reviews

Automated Recovery

  • Self-healing mechanisms
  • Automatic restart procedures
  • Failover systems
  • Data recovery processes
  • Service restoration workflows

Knowledge Management

  • Error documentation databases
  • Solution repositories
  • Best practice libraries
  • Training materials
  • Lessons learned archives

Specific Domain Expertise

Web Application Errors

  • HTTP error code analysis
  • JavaScript runtime errors
  • API failure patterns
  • Database connection issues
  • Frontend performance problems

Mobile Application Errors

  • Device-specific issues
  • Network connectivity problems
  • App store rejection patterns
  • Battery usage optimization
  • Memory management issues

Backend System Errors

  • Database transaction failures
  • Message queue processing errors
  • Authentication and authorization issues
  • Microservices communication problems
  • Resource exhaustion scenarios

Reporting & Analytics

Error Metrics

  • Mean Time To Detection (MTTD)
  • Mean Time To Resolution (MTTR)
  • Error frequency trends
  • Resolution effectiveness
  • Preventive action impact

Quality Dashboards

  • Real-time error monitoring
  • Historical trend analysis
  • Team performance metrics
  • System health indicators
  • Compliance status tracking

Deliverables

Analysis Reports

  • Comprehensive error analysis
  • Root cause identification
  • Impact assessment documentation
  • Resolution recommendations
  • Prevention strategies

Implementation Plans

  • Error detection system design
  • Monitoring setup procedures
  • Alerting configuration guides
  • Automated testing frameworks
  • Process improvement recommendations

Training Materials

  • Error handling best practices
  • Troubleshooting guides
  • Tool usage documentation
  • Process workflow diagrams
  • Knowledge base articles

Examples

Example 1: E-Commerce Platform Error Monitoring

Scenario: Implementing comprehensive error tracking for a high-traffic e-commerce site.

Implementation:

  1. Error Tracking: Sentry integration across all services
  2. Log Aggregation: ELK stack for centralized log management
  3. Alerting: PagerDuty integration for critical errors
  4. Dashboard: Custom Grafana dashboards for error metrics

Results:

  • MTTD reduced from hours to minutes
  • 40% reduction in time-to-resolution
  • Proactive identification of emerging issues

Example 2: Mobile App Crash Reporting

Scenario: Setting up crash reporting for iOS and Android applications.

Approach:

  1. Crash Reporting: Firebase Crashlytics integration
  2. Symbolication: Automated dSYM upload for readable stack traces
  3. Breadcrumbs: User action tracking for context
  4. Release Tracking: Correlation of crashes with app versions

Key Metrics Tracked:

  • Crash-free users rate (target: 99.5%)
  • Top crashers by device and OS version
  • Session data with crash-free rate trends
  • User feedback correlation with crashes

Example 3: API Gateway Error Analysis

Scenario: Monitoring and analyzing errors at API gateway level for a SaaS platform.

Monitoring Setup:

  1. Request Logging: All API requests logged with status codes
  2. Rate Tracking: Monitoring for 429 Too Many Requests patterns
  3. Latency Analysis: P95, P99 latency tracking by endpoint
  4. Authentication Errors: Tracking failed auth attempts for security

Alert Configuration:

  • Error rate spikes (> 5% for 5 minutes)
  • Latency degradation (> 1s for P95)
  • Authentication failures (> 100/min from single IP)
  • Circuit breaker state changes

Best Practices

Error Detection Configuration

  • Comprehensive Coverage: Instrument all code paths, not just critical functions
  • Context-Rich Data: Include user IDs, request IDs, environment details
  • Sensitive Data Handling: Scrub PII and secrets before error reporting
  • Sampling Strategy: Balance detail collection with performance impact
  • Tagging: Use consistent tagging for filtering and aggregation

Alert Management

  • Threshold Tuning: Adjust sensitivity to reduce alert fatigue
  • Escalation Paths: Clear procedures for different severity levels
  • Business Hours: Different expectations for on-call vs. business hours
  • Alert Fatigue Prevention: Consolidate related alerts, avoid duplicates
  • On-Call Rotation: Sustainable schedules with clear responsibilities

Metrics and Reporting

  • Key Metrics: Track MTTD, MTTR, error rate, resolution rate
  • Trend Analysis: Weekly/monthly comparisons to identify patterns
  • SLA Reporting: Error impact on service level agreements
  • Team Dashboards: Custom views for different teams and roles
  • Executive Reporting: High-level summaries for leadership

Error Handling Best Practices

  • Defensive Programming: Validate inputs, handle edge cases
  • Graceful Degradation: Fallback mechanisms when dependencies fail
  • Error Recovery: Automatic retry with exponential backoff
  • User Communication: Meaningful error messages for end users
  • Logging: Comprehensive logs for debugging and audit trails

Continuous Improvement

  • Post-Incident Reviews: Learn from every significant error
  • Pattern Analysis: Identify recurring issues for systemic fixes
  • Knowledge Base: Document errors and solutions for future reference
  • Tool Evolution: Regularly evaluate and update detection tools
  • Team Training: Ensure consistent error handling practices

平台分布

Claude Code

30.74%
按下载量换算253

OpenCode

22.73%
按下载量换算187

Codex

16.62%
按下载量换算137

Gemini CLI

12.98%
按下载量换算107

Cursor

8.56%
按下载量换算71

windsurf

3.54%
按下载量换算29

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills