Agent skill

Error Detective

by majiayu000 in majiayu000/claude-skill-registry

A skill your agent uses when user needs complex error pattern analysis, distributed system debugging, error correlation, root cause discovery, or predictive error prevention across microservices.

MITAuto-check passedDevelopment

Install Error Detective

skills CLI
$ npx skills add majiayu000/claude-skill-registry --skill error-detective -a claude-code

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

GitHub CLI
$ gh skill install majiayu000/claude-skill-registry error-detective --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/error-detective-skill-404kidwiz-claude-supercode-ski .claude/skills/error-detective && 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/

Facts

Skill name
error-detective
GitHub stars
666
Used in
1 other repo
Token cost
~3.7k tokens
SKILL.md length
1,663 words
Files
2
Skills in repo
971
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when user needs complex error pattern analysis, distributed system debugging, error correlation, root cause discovery, or predictive error prevention across microservices.

  • Works in 7 steps: Aggregate error logs from all affected… → Correlate errors temporally to identify… → Trace root cause through distributed… → …
  • User needs complex error pattern analysis
  • SKILL.md covers Purpose, When to Use, What This Skill Does and Core Capabilities, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Error Detective is an agent skill from majiayu000/claude-skill-registry. Use when user needs complex error pattern analysis, distributed system debugging, error correlation, root cause discovery, or predictive error prevention across microservices.

Its SKILL.md is about 3.7k 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 Development, covering Root cause analysis, Microservices and Forecasting and time series. 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

  • User needs complex error pattern analysis
  • Distributed system debugging
  • Error correlation
  • Root cause discovery

Example prompts

  • “/error-detective”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Aggregate error logs from all affected services
  2. Correlate errors temporally to identify propagation sequence
  3. Trace root cause through distributed tracing
  4. Map service dependencies and identify failure points
  5. Analyze cascade mechanisms (timeouts, retries, queues)
  6. Implement circuit breakers and monitoring improvements
  7. Prevent recurrence with predictive alerts

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.

    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

Error Detective loads about 3.7k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 1,663 words of instructions outside code blocks.

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

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). 1,663 words, ~3,677 tokens.

Download SKILL.mdSave it as .claude/skills/error-detective/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
error-detective
description
Use when user needs complex error pattern analysis, distributed system debugging, error correlation, root cause discovery, or predictive error prevention across microservices.

Error Detective

Purpose

Provides comprehensive error analysis and pattern detection expertise for distributed systems. Specializes in identifying complex error patterns, correlating failures across services, and discovering root causes through systematic investigation. Implements predictive error prevention and continuous monitoring improvement.

When to Use

  • Complex error patterns or cascading failures
  • Distributed system debugging across multiple services
  • Error correlation and root cause analysis
  • Anomaly detection or error prediction
  • Error trend analysis and forecasting
  • Monitoring improvement or alert optimization
  • Incident prevention or proactive error management
  • Knowledge management for error patterns

What This Skill Does

The error-detective skill delivers comprehensive error analysis capabilities through systematic phases of error landscape analysis, deep investigation, and detection excellence. It identifies hidden connections, prevents error cascades, and provides actionable prevention strategies.

Error Pattern Analysis

Performs frequency analysis of error occurrences, identifies time-based patterns (hourly, daily, weekly), correlates errors across services, maps user impact patterns, analyzes geographic and device variations, identifies version-specific patterns, and detects environmental differences (dev/staging/prod).

Log Correlation

Correlates errors across multiple services, performs temporal correlation to find sequences, analyzes causal chains of error propagation, sequences events chronologically, applies pattern matching for error signatures, detects anomalies in error patterns, performs statistical analysis of error distributions, and applies machine learning for insight discovery.

Distributed Tracing

Tracks request flow across service boundaries, maps service dependencies graphically, analyzes latency patterns and bottlenecks, tracks error propagation through the system, identifies performance correlations, correlates resource usage with errors, maps user journeys through the system, and identifies affected users.

Anomaly Detection

Establishes performance baselines, detects deviations from normal patterns, analyzes threshold violations, recognizes error patterns before they become critical, applies predictive modeling for forecasting, optimizes alert configurations for signal-to-noise, reduces false positives, and classifies error severity automatically.

Impact Analysis

Assesses user impact by counting affected users, calculates business impact in revenue or SLA terms, measures service degradation severity, evaluates data integrity impacts, assesses security implications, analyzes performance impact, estimates cost implications, and evaluates reputation impact.

Core Capabilities

Error Categorization
  • System errors (infrastructure, connectivity)
  • Application errors (code bugs, logic errors)
  • User errors (validation, authorization)
  • Integration errors (API failures, third-party)
  • Performance errors (slowdowns, timeouts)
  • Security errors (authentication, authorization)
  • Data errors (corruption, inconsistency)
  • Configuration errors (misconfigurations, conflicts)
Root Cause Techniques
  • Five whys analysis for deep understanding
  • Fishbone diagrams for systematic analysis
  • Fault tree analysis for failure modes
  • Event correlation across time and services
  • Timeline reconstruction for incident sequence
  • Hypothesis testing for cause validation
  • Elimination process for narrowing causes
  • Pattern synthesis for identifying commonalities
Prevention Strategies
  • Error prediction based on patterns
  • Proactive monitoring before errors occur
  • Circuit breaker implementation
  • Graceful degradation patterns
  • Error budget management
  • Chaos engineering for resilience testing
  • Load testing for capacity planning
  • Failure injection for preparation
Forensic Analysis
  • Collects evidence from logs and metrics
  • Constructs detailed timelines
  • Identifies actors and triggers
  • Reconstructs error sequences
  • Measures actual impact
  • Analyzes recovery effectiveness
  • Extracts lessons learned
  • Generates comprehensive reports
Visualization Techniques
  • Error heat maps for geographic or temporal visualization
  • Dependency graphs for service relationships
  • Time series charts for trends
  • Correlation matrices for error relationships
  • Flow diagrams for error propagation
  • Impact radius visualization
  • Trend analysis for forecasting
  • Predictive model visualization
Error Correlation Techniques
  • Time-based correlation (temporal proximity)
  • Service correlation (service dependencies)
  • User correlation (shared user sessions)
  • Geographic correlation (regional issues)
  • Version correlation (deployment-related)
  • Load correlation (traffic-related)
  • Change correlation (configuration or code changes)
  • External correlation (third-party dependencies)
Predictive Analysis
  • Trend detection for forecasting
  • Pattern prediction for anticipation
  • Anomaly forecasting for prevention
  • Capacity prediction for planning
  • Failure prediction for preparation
  • Impact estimation for prioritization
  • Risk scoring for triage
  • Alert optimization for early warning
Cascade Analysis
  • Failure propagation tracking
  • Service dependency mapping
  • Circuit breaker gap identification
  • Timeout chain analysis
  • Retry storm detection
  • Queue backup analysis
  • Resource exhaustion identification
  • Domino effect prevention

Tool Restrictions

The error-detective skill uses standard file operations for configuration and script generation. It requires log aggregation tools (ELK, Splunk, Loki), monitoring platforms (Prometheus, Grafana, CloudWatch), and tracing systems (Jaeger, Zipkin, Honeycomb). Does not perform application code fixes—coordinate with appropriate development skills for remediation.

Integration with Other Skills

  • Collaborates with debugger for specific issue investigation
  • Supports qa-expert for test scenario design
  • Works with performance-engineer for performance error analysis
  • Guides security-auditor for security pattern analysis
  • Helps devops-incident-responder for incident investigation
  • Assists sre-engineer for reliability improvements
  • Partners with monitoring specialists for tool integration
  • Coordinates with backend-developer for application errors

Example Interactions

Scenario 1: Cascading Failure Investigation

User: "We're seeing failures across multiple services"

Response:

  1. Aggregate error logs from all affected services
  2. Correlate errors temporally to identify propagation sequence
  3. Trace root cause through distributed tracing
  4. Map service dependencies and identify failure points
  5. Analyze cascade mechanisms (timeouts, retries, queues)
  6. Implement circuit breakers and monitoring improvements
  7. Prevent recurrence with predictive alerts
Scenario 2: Error Pattern Discovery

User: "Find patterns in our error logs"

Response:

  1. Analyze 15,420 errors across system
  2. Identify 23 distinct error patterns
  3. Correlate patterns across services and time
  4. Determine 7 root causes for patterns
  5. Assess impact and severity for each pattern
  6. Design monitoring and alerting for key patterns
  7. Implement prevention strategies reducing errors by 67%
Scenario 3: Anomaly Detection Setup

User: "Set up predictive error monitoring"

Response:

  1. Establish performance baselines from historical data
  2. Configure anomaly detection for error rates
  3. Implement predictive modeling for error forecasting
  4. Set up alerts with optimized thresholds
  5. Reduce false positives through ML-based filtering
  6. Create dashboards for visualization
  7. Train team on anomaly interpretation and response

Best Practices

  • Always start with symptoms and follow error chains
  • Correlate errors across time and services before conclusions
  • Verify hypotheses with data and evidence
  • Document findings thoroughly for knowledge sharing
  • Implement monitoring improvements based on discovered patterns
  • Use predictive alerts for proactive prevention
  • Analyze cascades to prevent domino effects
  • Build knowledge base of patterns and solutions

Output Format

Delivers comprehensive error analysis reports, pattern libraries, root cause databases, monitoring improvements, predictive alerts, and knowledge management resources. Provides dashboards for visualization and actionable prevention strategies with measurable impact.

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

Included Automation Scripts

The error-detective skill includes comprehensive automation scripts located in scripts/:

  • error_detection_automation.py: Automates error detection and analysis by scanning logs for error patterns, correlating errors across services, detecting anomalies in error rates, and generating error reports and alerts

References

Reference Documentation (references/ directory)
  • troubleshooting.md: Troubleshooting guide for error detection patterns, distributed system debugging, and root cause analysis
  • best_practices.md: Best practices for error correlation, anomaly detection, predictive error prevention, and knowledge management

Examples

Example 1: Distributed System Failure Analysis

Scenario: A microservices architecture experiences intermittent failures where some requests timeout while others succeed.

Investigation Approach:

  1. Error Collection: Aggregated logs from all services during failure window
  2. Correlation Analysis: Identified temporal patterns using timestamp alignment
  3. Dependency Mapping: Traced request flow through all services
  4. Root Cause: Database connection pool exhaustion in one service

Resolution:

  • Increased connection pool size and added circuit breakers
  • Implemented exponential backoff for retries
  • Added connection pool monitoring alerts
Example 2: Performance Regression Detection

Scenario: User-reported application slowness after a deployment, but automated tests pass.

Detection Process:

  1. Baseline Comparison: Compared current performance against historical data
  2. Database Analysis: Identified new query patterns causing table scans
  3. Code Review: Found N+1 query pattern introduced in recent change
  4. Impact Assessment: Quantified latency increase and affected endpoints

Solution:

  • Optimized ORM queries with eager loading
  • Added query performance tests to CI pipeline
  • Implemented database query monitoring
Example 3: Security Vulnerability Pattern Discovery

Scenario: Unusual patterns in authentication logs suggest potential brute force attacks.

Analysis Steps:

  1. Pattern Recognition: Identified IP addresses with multiple failed attempts
  2. Rate Analysis: Detected timing patterns indicating automated attacks
  3. Impact Assessment: Mapped affected accounts and potential exposure
  4. Remediation: Implemented rate limiting and CAPTCHA challenges

Prevention Measures:

  • Added fail2ban-style automatic blocking
  • Enhanced monitoring for authentication anomalies
  • Implemented multi-factor authentication for sensitive operations

Best Practices

Investigation Methodology
  • Systematic Approach: Follow consistent process from symptoms to root cause
  • Evidence-Based: Base conclusions on data, not assumptions
  • Thorough Documentation: Record all findings, even negative results
  • Cross-Reference: Validate findings against multiple data sources
  • Collaborative Investigation: Involve relevant teams for diverse perspectives
Error Pattern Recognition
  • Baseline Establishment: Define normal behavior for comparison
  • Anomaly Detection: Use statistical methods to identify deviations
  • Trend Analysis: Track error patterns over time
  • Correlation: Connect errors across services and time periods
  • Prioritization: Focus on high-impact, frequent error patterns
Root Cause Analysis
  • 5 Whys Technique: Drill down to underlying causes
  • Fault Tree Analysis: Map causal relationships systematically
  • Contributing Factors: Identify systemic issues beyond immediate cause
  • Documentation: Create actionable findings with evidence
  • Verification: Confirm fix addresses root cause, not symptoms
Prevention Strategy
  • Automated Monitoring: Implement proactive error detection
  • Predictive Alerts: Use ML for early warning systems
  • Testing Integration: Add error scenarios to test suites
  • Knowledge Sharing: Document patterns and solutions
  • Continuous Improvement: Iterate on prevention based on learnings

Anti-Patterns

Investigation Anti-Patterns
  • Jumping to Conclusions: Fixing symptoms without root cause analysis - resist pressure to act before understanding
  • Blame Game: Focusing on who caused the error instead of why - use blameless postmortems
  • Over-Engineering Solutions: Implementing complex fixes for simple problems - prefer simple, proven solutions
  • Scope Creep: Expanding investigation beyond original symptoms - stay focused on the reported issue
Error Pattern Anti-Patterns
  • Noise Acceptance: Ignoring frequent low-severity errors - track all errors and their trends
  • Alert Fatigue: Ignoring alerts that trigger too often - optimize thresholds and reduce false positives
  • Pattern Blindness: Missing gradual degradation masked by normal variation - establish and monitor baselines
  • Siloed View: Analyzing errors in isolation - correlate errors across services and time
Root Cause Anti-Patterns
  • Single Point Failure Focus: Stopping at first identified cause - continue asking "why" until systemic issues found
  • Human Error Labeling: Blaming individuals without examining system design - human error is often system failure
  • Temporal Fallacy: Assuming temporal proximity indicates causation - validate causal relationships
  • Confirmation Bias: Seeking evidence for assumed causes - test alternative hypotheses
Prevention Anti-Patterns
  • False Confidence: Assuming fixed errors won't recur - implement monitoring and detection
  • Prevention Paralysis: Over-investing in prevention at expense of detection - balance prevention and detection
  • One-Shot Learning: Learning from incidents only once - build institutional knowledge and pattern recognition
  • Documentation Debt: Failing to document error patterns and solutions - maintain searchable knowledge base

© majiayu000, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/analysis/error-detective-skill-404kidwiz-claude-supercode-ski of majiayu000/claude-skill-registry.

  • SKILL.md
  • metadata.json

Open the folder on GitHubat commit 000116a

Used in 1 other repository

We found 2 copies 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.

Compare with similar skills

Error Detective 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.

Error Detective compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Error Detective this skillmajiayu000/claude-skill-registry6661 repos~3.7kAutomated safety check: PassMIT
Time Series Analytics Useropen-edge-platform/edge-ai-libraries168—~3.1kAutomated safety check: PassApache-2.0
QA Find Bugs MCPbex-co/beancount-io294—~3kAutomated safety check: PassMIT
Time Series Analytics Devopen-edge-platform/edge-ai-libraries168—~1.5kAutomated safety check: NotesApache-2.0
ML AIgrafana/skills278—~1.3kAutomated safety check: PassApache-2.0
Evolutionary Modular Architecturetech-leads-club/agent-skills7k—~3.7kAutomated safety check: PassCC-BY-4.0

Similar skills

  • Time Series Analytics User

    open-edge-platform/edge-ai-libraries

    Build a new time-series analytics use case on top of the deployed Time Series Analytics microservice — bring it up with Docker Compose (from a repo clone, or by fetching the compose files from…

    168 GitHub stars~3.1k tokensUpdated today
    Data & AnalyticsAuto-check passed
  • QA Find Bugs MCP

    bex-co/beancount-io

    Hunt bugs in the Beancount.io remote MCP server by driving the real POST /api-gateway/mcp endpoint with JSON-RPC and real MCP clients, checking transport, discovery, credential boundaries, tool and…

    294 GitHub stars~3k tokensUpdated today
    Backend & APIsAuto-check passed
  • Time Series Analytics Dev

    open-edge-platform/edge-ai-libraries

    Develop the Time Series Analytics microservice itself (FastAPI + Kapacitor) — build and deploy it locally via Docker Compose or Helm, run the mocked unit test suite (tests/runtests.sh) and the…

    168 GitHub stars~1.5k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • ML AI

    grafana/skills

    Official

    Turn on AI + ML features in Grafana Cloud — Grafana Assistant (NL → PromQL/LogQL/TraceQL, dashboard build, incident investigation, MCP integration), Dynamic Alerting (Prophet forecasting + DBSCAN…

    278 GitHub stars~1.3k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Evolutionary Modular Architecture

    tech-leads-club/agent-skills

    Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.

    7k GitHub stars~3.7k tokensUpdated 17 days ago
    DevelopmentAuto-check passed
  • Designing Architecture

    CloudAI-X/claude-workflow-v2

    Designs software architecture and selects appropriate patterns for projects.

    1.4k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

More from majiayu000/claude-skill-registry

All 971 skills in this repo
  • Deep Research

    majiayu000/claude-skill-registry

    Multi-source deep research using firecrawl and exa MCPs. An agent skill from majiayu000/claude-skill-registry.

    666 GitHub starsUsed in 6 repos~1.1k tokens
    Auto-check passed
  • Exa Search

    majiayu000/claude-skill-registry

    Neural search via Exa MCP for web, code, and company research.

    666 GitHub starsUsed in 5 repos~856 tokens
    Auto-check passed
  • Fal AI Media

    majiayu000/claude-skill-registry

    Unified media generation via fal.ai MCP — image, video, and audio.

    666 GitHub starsUsed in 5 repos~1.7k tokens
    Auto-check passed
  • Bgpt Paper Search

    majiayu000/claude-skill-registry

    Search scientific papers and retrieve structured experimental data extracted from full-text studies via the BGPT MCP server.

    666 GitHub starsUsed in 4 repos~619 tokens
    Auto-check: notes
  • Bio Alignment Pairwise

    majiayu000/claude-skill-registry

    Perform pairwise sequence alignment using Biopython Bio.Align.PairwiseAligner.

    666 GitHub starsUsed in 4 repos~1.7k tokens
    Auto-check passed
  • Open Notebook

    majiayu000/claude-skill-registry

    Self-hosted, open-source alternative to Google NotebookLM for AI-powered research and document analysis.

    666 GitHub starsUsed in 4 repos~2.4k tokens
    Auto-check passed

Questions about Error Detective

What does Error Detective do?

A skill your agent uses when user needs complex error pattern analysis, distributed system debugging, error correlation, root cause discovery, or predictive error prevention across microservices. Error Detective is an agent skill from majiayu000/claude-skill-registry. Use when user needs complex error pattern analysis, distributed system debugging, error correlation, root cause discovery, or predictive error prevention across microservices.

When should I use Error Detective?

Error Detective fits situations like: user needs complex error pattern analysis; distributed system debugging; error correlation; root cause discovery.

How do I install Error Detective in Claude Code?

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

How do I install Error Detective in Codex?

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

Can I use Error Detective 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 error-detective -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/error-detective, .gemini/skills/error-detective, .github/skills/error-detective and .opencode/skills/error-detective in your project.

What does Error Detective need to run?

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

Does Error Detective 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 Error Detective 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 Error Detective use?

Error Detective 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 Error Detective use?

About 3.7k tokens (SKILL.md is roughly 15k 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 Error Detective?

Skills that share tags, products or a category with Error Detective: Time Series Analytics User (open-edge-platform/edge-ai-libraries, 168 stars), QA Find Bugs MCP (bex-co/beancount-io, 294 stars), Time Series Analytics Dev (open-edge-platform/edge-ai-libraries, 168 stars) and ML AI (grafana/skills, 278 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Error Detective?

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.