Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
golang-testing
GoLang testing guidelines
majiayu000/claude-skill-registry 163
-
python-test-strategy
Python unit testing patterns for pytest, including test file structure, fixtures, mocks, and coverage strategy. Use when asked to write tests (unit/integration) for any Python module, function, class, or method.
majiayu000/claude-skill-registry 163
-
mechinterp-validation-suite
Run credibility checks on feature interpretations including split-half stability and shuffle null tests
majiayu000/claude-skill-registry 163
-
generate-schema
Generate the conclaude-schema.json configuration schema file using src/bin/generate-schema.rs.
USE WHEN the configuration format changes, new config fields are added, or the schema needs to be updated for release or testing.
majiayu000/claude-skill-registry 163
-
throughput-calculator
Throughput Calculator - Auto-activating skill for Performance Testing.
Triggers on: throughput calculator, throughput calculator
Part of the Performance Testing skill category.
majiayu000/claude-skill-registry 163
-
designing-claude-skills
majiayu000/claude-skill-registry 163
-
mexican-cuisine-specialist
Authentic Mexican cooking expert covering moles, salsas, tacos, and regional Mexican dishes
majiayu000/claude-skill-registry 163
-
mocha-configuration
Use when mocha configuration including reporters, config files, plugins, and CI integration.
majiayu000/claude-skill-registry 163
-
rapid-prototyper
Creates minimal working prototypes for quick idea validation. Single-file when possible, includes test data, ready to demo immediately. Use when user says "prototype", "MVP", "proof of concept", "quick demo".
majiayu000/claude-skill-registry 163
-
ghe-report
Generate DETAILED reports with metrics, health checks, or epic-specific analysis. More comprehensive than quick status overview.
USE THIS SKILL WHEN:
- User asks for "metrics" or "statistics" or "performance report"
- User asks for "health check" or "workflow health" or "compliance check"
- User asks for "epic report" or "epic status for X"
- User asks for "detailed report" or "comprehensive report"
- User asks "how are we performing" or "what's our throughput"
- User asks about "cycle times" or "demotion rates"
- User wants analysis, not just current state
REPORT TYPES:
- metrics: Throughput, cycle times, first-pass rates, demotion rates
- health: Compliance status, stale threads, violation history, memory bank status
- epic: Single epic details with thread history, progress, decisions
DO NOT USE THIS SKILL WHEN:
- User just wants QUICK status overview (use ghe-status)
- User wants to CLAIM an issue (use ghe-claim)
- User wants to POST a checkpoint (use ghe-checkpoint)
- User wants to TRANSITION phases (use ghe-transition)
KEY DIFFERENCE FROM ghe-status:
- ghe-status = quick overview, current state, what's active
- ghe-report = detailed analysis, metrics, trends, health assessment
EXAMPLES:
<example>
Context: User wants performance metrics
user: "Show me the workflow metrics"
assistant: "I'll use ghe-report with type 'metrics' for detailed performance analysis"
</example>
<example>
Context: User wants to check workflow compliance
user: "Run a health check on the workflow"
assistant: "I'll use ghe-report with type 'health' to assess workflow compliance"
</example>
<example>
Context: User wants details on specific epic
user: "Give me a report on the jwt-auth epic"
assistant: "I'll use ghe-report with type 'epic' for jwt-auth"
</example>
<example>
Context: User asks about performance trends
user: "What's our first-pass review rate?"
assistant: "I'll use ghe-report with type 'metrics' to get performance statistics"
</example>
majiayu000/claude-skill-registry 163
-
rust-crate-creator-wcygan-sql-database
majiayu000/claude-skill-registry 163
-
jest-react-testing
Comprehensive React component testing with Jest and React Testing Library covering configuration, mocking strategies, async testing patterns, hooks testing, and integration testing best practices
majiayu000/claude-skill-registry 163
-
bdd-patterns
Use when applying Behavior-Driven Development patterns including Given-When-Then structure, feature files, and acceptance criteria. Use when writing BDD-style tests and specifications.
majiayu000/claude-skill-registry 163
-
moai-baas-firebase-ext
Enterprise Firebase Platform with AI-powered Google Cloud integration, Context7 integration, and intelligent Firebase orchestration for scalable mobile and web applications
majiayu000/claude-skill-registry 163
-
vault-field-values
Get all unique values for a specific frontmatter field. Triggers on "field values", "unique values for", "what X values exist", "list all X".
majiayu000/claude-skill-registry 163
-
dependency-security-scanning
依存関係の脆弱性スキャン、CVE評価、レポート作成を体系化するスキル。
SCAの運用と修正計画の整理を支援する。
Anchors:
• OWASP Dependency-Check / 適用: 依存スキャン / 目的: 検出の標準化
• CVSS v3.1 Specification / 適用: 重大度評価 / 目的: 優先度の整合性
• Web Application Security / 適用: 脅威評価 / 目的: リスク判定の一貫性
Trigger:
Use when scanning dependencies for vulnerabilities, evaluating CVE reports, producing audit reports, or planning remediation.
dependency scan, CVE, CVSS, SCA, supply chain security, audit report
majiayu000/claude-skill-registry 163
-
run-integration-tests
Run integration tests validating cross-component requirements and system behavior. Executes BDD scenarios, API tests, and end-to-end tests. Use to validate integrated system or as pre-deployment quality gate.
majiayu000/claude-skill-registry 163
-
bdd-scenarios
Use when writing effective BDD scenarios including acceptance criteria, edge cases, and scenario organization. Use when defining behavior specifications.
majiayu000/claude-skill-registry 163
-
submit-issue
Handle user questions, feature requests, and bug reports for connectrpc-axum. This skill should be used when users ask questions about the library, request new features, or report bugs. It first attempts to answer using project documentation, verifies bugs with integration tests, and submits GitHub issues when needed.
majiayu000/claude-skill-registry 163
-
reviewing-testability
TypeScript/Reactアプリケーション向けテスト可能なコード設計パターン。 トリガー: テスタビリティ, testability, テスト可能, テストしやすい, モック, mock, 純粋関数, pure function, 依存性注入, dependency injection, DI, 副作用, side effect, 副作用分離, テスト困難, hard to test.
majiayu000/claude-skill-registry 163
-
profiling
Profile code performance using callgrind and valgrind with nextest integration for analyzing instruction counts, cache behavior, and identifying bottlenecks
majiayu000/claude-skill-registry 163
-
extract-formulas
Extract mathematical formulas (F-*) from requirements - calculations, algorithms, conversions. Enables autogeneration of calculation functions with tests. Use when requirements involve math, dates, percentages, or algorithms.
majiayu000/claude-skill-registry 163
-
golang-code-review
Comprehensive Go code review skill for PR reviews, architecture assessment, and test quality analysis. Use when reviewing Go code to ensure adherence to Go best practices, security standards, and project-specific patterns. Applies to full PR reviews, single file/function reviews, architecture evaluation, and test code quality checks.
majiayu000/claude-skill-registry 163
-
experiment-retrospective
Turn experiment reports and notes into summaries and new/updated result skills.
majiayu000/claude-skill-registry 163