majiayu000/claude-skill-registry - Page 43

analyze-project-context

Use when starting work on any project (technical or non-technical) to understand structure, standards, and best practices before making changes

analyze-project-context

Use when starting work on any project (technical or non-technical) to understand structure, standards, and best practices before making changes

analyze-prs

Analyze all open PRs targeting a base branch — determine merge order, identify file overlaps, and tag each PR as simple or needs_check for complexity. Use at the start of a PR consolidation workflow.

analyze-session

Analyze a Figma MCP test session transcript. Reads raw session data (JSON or HTML) and produces a structured analysis document with metrics, efficiency issues, error patterns, and prioritized improvements. Updates the cross-session improvement tracker. Use…

analyze-sessions

Analyze session logs to discover automation opportunities. Use periodically to find patterns in your Claude Code usage that could be automated. Use periodically after multiple sessions to find automation opportunities.

analyze

Invoke IMMEDIATELY via python script when user requests codebase analysis, architecture review, security assessment, or quality evaluation. Do NOT explore first - the script orchestrates exploration.

analyze-skill

Analyze skill complexity and get modularization recommendations

analyze-spec-flow

Use this skill when you have a specification, plan, feature description, or technical document that needs user flow analysis and gap identification.

analyze-spec

Analyze an existing spec for inconsistencies, missing information, ambiguities, and structure issues. Use when user says "analyze spec", "review spec", "spec quality check", "validate requirements", "audit spec", or "check spec quality".

analyze-spec

Analyze an existing spec for inconsistencies, missing information, ambiguities, and structure issues. Use when user says "analyze spec", "review spec", "spec quality check", "validate requirements", "audit spec", or "check spec quality".

analyze-system

システム分析エージェント - ユビキタス言語、アクター、ロール、権限、ドメイン-コード対応表を抽出。/analyze-system [対象パス] で呼び出し。

Source text: Japanese

analyze

Analyze a collection of documents to build a knowledge map, identify themes, find gaps, duplicates, conflicts, and staleness, then produce an organized analysis with improvement recommendations. Designed for document ecosystems (cross-repo docs, research…

analyze-trends-historical

Analyze trends over time by comparing current entity mentions against historical data from memory. Identifies topics gaining or losing popularity, emerging themes, and provides trend velocity and trajectory analysis for weekly trend reports.

analyze-video

Adds visual descriptions to transcripts by extracting and analyzing video frames with ffmpeg. Creates visual transcript with periodic visual descriptions of the video clip. Use when all files have audio transcripts present (transcript) but don't yet have…

analyze-with-file

Interactive collaborative analysis with documented discussions, inline exploration, and evolving understanding. Serial execution with no agent delegation.

analyzer

Comprehensive codebase analysis methodology for existing projects. Use when onboarding to a new codebase, doing periodic health checks, or before refactoring.

analyzing-aorc-precipitation

Retrieves and processes AORC precipitation data for HEC-RAS/HMS models. Handles spatial averaging over watersheds, temporal aggregation, DSS export, and Atlas 14 design storms. Use when working with historical precipitation, AORC data, calibration workflows,…

analyzing-api-layer

Use when analyzing REST/GraphQL API endpoints, contracts, authentication, and client-facing interfaces

analyzing-database-layer

Use when analyzing the database layer including schema, migrations, ORM configuration, and data access patterns

analyzing-domain-model

Use when analyzing domain entities, value objects, aggregates, and business rules encoded in the model

analyzing-domains

Use when entering unfamiliar domains, modeling complex business logic, or when terms/concepts are unclear. Triggers: "what are the domain concepts", "define the entities", "model this domain", "DDD", "ubiquitous language", "bounded context", or when…

analyzing-frontend-layer

Use when analyzing frontend/UI layer including components, state management, routing, and API integration (optional - skip if no frontend exists)

analyzing-gaps

Compare user expectations (UTCs) with code reality to identify gaps. Use when you need to understand discrepancies between what users expect and what code actually does.

analyzing-kb-gaps

Use when you have Knowledge Base exports and want to identify user pain points, missing articles, and AI assistance opportunities.

analyzing-meetings

MUST BE USED when analyzing meeting transcripts or notes. Classifies input type, attributes speakers, and verifies names against colleagues.json. Works with routing-initiatives and summarizing-meetings skills for complete workflow.

analyzing-messaging-layer

Use when analyzing event-driven systems, message queues, async processing, and pub/sub patterns

analyzing-requirements

ユーザー要件を分析し、システム設計ドキュメント(DESIGN.md)を生成します。ユーザー要件が曖昧または不明確な場合、システムアーキテクチャの設計が必要な場合、大規模な機能開発の設計仕様が必要な場合、技術的実現可能性の検証が必要な場合に使用します。不明点はAskUserQuestionツールで確認します。

Source text: Japanese

analyzing-root-causes

Root cause analysis with 5 Whys methodology. Triggers: root cause, 5 Whys, なぜなぜ分析, 根本原因, 原因分析, symptom fix, 対症療法.

Source text: Japanese

analyzing-service-layer

Use when analyzing business logic, use cases, service orchestration, and data transformation including DTOs and mappers

analyzing-skill-usage

Use when evaluating skill performance, A/B testing skill versions, or identifying weak skills. Analyzes session transcripts to extract skill invocation patterns, completion rates, correction rates, and efficiency metrics.

analyzing-wav

Analyze WAV audio files for debugging TTS and audio pipelines. Use when checking audio quality, validating WAV format, inspecting waveform patterns, or diagnosing generated speech issues.

anomaly-detection

Rule-based anomaly detection for production systems with configurable thresholds, cooldown periods to prevent alert storms, and error pattern tracking for repeated failures.

anomaly-detector

Detect outliers, spikes, rare events, and abnormal records in tabular or time-series data. Use when the task is anomaly detection or suspicious-pattern review, not generic data-quality linting or full ML pipeline ownership.

anspruchstabelle

Aufbau oder Überprüfung einer Anspruchstabelle – zivilrechtliche Element-für-Element-Analyse eines Anspruchs oder einer Einrede, oder patentrechtliche Verletzungs-/Nichtigkeitstabelle – mit Quellenbelegen für jedes Element und Lückenerkennung als…

Source text: German

answeroverflow

Search and analyze AnswerOverflow for community-sourced technical solutions.

anw-steuerbescheid-analyse

Steuerbescheid strukturiert auswerten und Angriffspunkte für Einspruch identifizieren. Anwendungsfall Mandant hat Steuerbescheid bekommen und fragt ob und wie er sich wehren kann. Bescheidarten Festsetzungsbescheid Aenderungsbescheid Schaetzungsbescheid…

Source text: German

app-deep-review

Deep analysis of an AinexSuite app with 6 parallel review agents. Use when you want comprehensive modernization recommendations for backend, frontend, UX, UI, AI enhancement, and security/performance. Includes severity ratings, code examples, and auto-fix…

apsiii-score

Calculate APACHE III (Acute Physiology Score III) for ICU patients in MIMIC-IV. Use for mortality prediction, severity stratification, case-mix adjustment, or risk-adjusted outcome comparisons.

aqr-factor-investing

Build investment systems in the style of AQR Capital Management, the quantitative investment firm pioneering factor investing. Emphasizes academic rigor, transparent methodology, and systematic factor exposure. Use when building factor models, conducting…

aqwa-analysis

Integrate with AQWA hydrodynamic software for RAO computation, damping analysis, and coefficient extraction. Use for AQWA file processing, RAO calculation, hydrodynamic coefficient extraction, and pre/post processing workflows.