Loading...
Loading...
Found 373 Skills
Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability
Build, plan, review, and document pyRevit extensions. Use when Codex needs the pyRevit development workflow, templates, prompts, checklists, or scripts for creating or updating pyRevit commands in this repo. Pair with a version-specific Revit skill (e.g., 2023/2024/2025) for API constraints.
Individualized development plans by weakness. Skill assessments, call reviews, ride-along checklists, certification tracking.
Check or verify whether a Skill complies with best practice specifications, covering naming conventions, directory structure, metadata integrity, temporary file cleanup, and dependency format validation. It provides detailed checklists, automatic repair suggestions, and report templates, and also supports integrity checks and automatic repair of skill library documentation. It is suitable for quality verification after creating or modifying a Skill
Guides Android code reviews with type-specific checklists and MVVM/Compose pattern validation. Use when reviewing Android PRs, pull requests, diffs, or local changes involving Kotlin, ViewModel, Composable, Repository, or Gradle files. Triggered by "review PR", "review changes", "check this code", "Android review", or code review requests mentioning bitwarden/android. Loads specialized checklists for feature additions, bug fixes, UI refinements, refactoring, dependency updates, and infrastructure changes.
Guidelines for Micro-SaaS architecture, Stripe integration, and launch checklists.
Complete ClickHouse operations guide for DevOps and SRE teams managing production deployments. Provides practical guidance on monitoring essential metrics (query latency, throughput, memory, disk), introspecting system tables, performance analysis, scaling strategies (vertical and horizontal), backup/disaster recovery, tuning at query/server/table levels, and troubleshooting common issues. Use when diagnosing ClickHouse problems, optimizing performance, planning capacity, setting up monitoring, implementing backups, or managing production clusters. Includes resource management strategies for disk space, connections, and background operations plus production checklists.
Diagnoses what makes code complex and why, using the three-symptom two-root-cause framework. Use when code feels harder to work with than it should but the specific problem is unclear. This skill identifies WHETHER complexity exists and WHERE it comes from. Not for scanning a checklist of known design smells (use red-flags) or evaluating a specific module's depth (use deep-modules).
App Store review preparation and rejection prevention. Covers App Store review guidelines, app rejection reasons, PrivacyInfo.xcprivacy privacy manifest requirements, required API reason codes, in-app purchase IAP and StoreKit rules, App Store Guidelines compliance, ATT App Tracking Transparency, EU DMA Digital Markets Act, HIG compliance checklist, app submission preparation, review preparation, metadata requirements, entitlements, widgets, and Live Activities review rules. Use when preparing for App Store submission, fixing rejection reasons, auditing privacy manifests, implementing ATT consent flow, configuring StoreKit IAP, or checking HIG compliance.
Creates structured development plans with phased task breakdowns, requirements, and QA checklists. Use when the user explicitly asks to create a dev plan, development plan, or document development requirements.
Use when structuring, formatting, evaluating, or reviewing a Technology Innovation Management (TIM) project report for Carleton University — provides report rules, chapter guidance, literature review expectations, research method templates, and a compliance-audit checklist.
Critical analysis of research papers, academic manuscripts, preprints, and technical studies — evaluating methodology, claims-evidence alignment, contribution significance, and intellectual honesty. Produces coherent analytical responses (not checklists) that distinguish genuine weaknesses from standard field limitations. Governs intellectual posture: collegial reader, not adversarial reviewer. Triggers on: "critique this paper", "review this research", "what do you think of this paper", "analyze this study", "evaluate the methodology", "is this paper sound", "assess this research", "strengths and weaknesses of this paper", "does the evidence support the claims". Use this skill when the user provides a research paper, preprint, or technical study and asks for critical evaluation of its scientific merit, methodology, or contribution — not formatting, citation hygiene, or submission readiness (use manuscript-review for those).