All Skills

Comprehensive multi-dimensional pre-implementation quality gate. Combines coherence, gaps, errors, and cross-references in a single pass. Use before starting implementation or at phase boundaries.

Auto-update GitHub repo description, live site URL, and topics. Analyzes your codebase to generate a compelling description, detects deployment URLs, and adds relevant topics. Use when setting up a repo, after deploying, or to polish your GitHub presence. Use when the user says "update github about", "update repo about", "set repo description", "add topics", "update about section", "github about", or any reference to updating a GitHub repository's about/description/topics/homepage.

Complete integration with Atlassian products (Jira, Confluence, Bitbucket, Trello) for project management and documentation

Enable Claude Code to leverage its own CLI for unrestricted system access, bypassing VS Code extension permission limitations

# Catalyst Calendar description: Build and maintain a calendar of upcoming catalysts across a coverage universe — earnings dates, conferences, product launches, regulatory decisions, and macro events. Helps prioritize attention and position ahead of events. Triggers on "catalyst calendar", "upcomin

This skill should be used when the user asks "Chart.js plugins", "custom Chart.js plugin", "Chart.js plugin hooks", "beforeDraw plugin", "afterDraw plugin", "Chart.js plugin API", "register Chart.js plugin", "Chart.js plugin options", "Chart.js plugin lifecycle", "Chart.js plugin TypeScript", or needs help creating custom plugins for Chart.js v4.5.1.

Manage ML experiments, track results, and compare performance across different configurations. Use when setting up experiment tracking, creating experiment configs, comparing runs, or analyzing experiment results with W&B, TensorBoard, or MLflow.

Export trained PyTorch models to various formats (ONNX, TorchScript, TensorRT) and upload to model registries (Hugging Face Hub, MLflow). Use when deploying models, sharing trained weights, or preparing for production inference.

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

# GitHub Integration Skill - Completion Documentation **Skill Name:** github-integration **Created:** 2025-10-20 06:08:29 **IDE:** Claude Code (with Cursor compatibility) **Type:** Ad-hoc Skill (User Request) **Status:** ✅ Complete ## Purpose Complete GitHub integration skill for managing reposit

This skill should be used when the user asks to "generate audit logs", "create HIPAA audit trail", "log healthcare events", "configure audit logging", "track PHI access", "maintain compliance logs", "audit log format", "healthcare event logging", "access control logging", "authentication logging", "HIPAA logging requirements", or mentions HIPAA audit trails, healthcare event logging, compliance logging, PHI access tracking, authentication auditing, or §164.312(b) logging requirements.

--- name: responding-to-incidents description: Assist with production incident response, log analysis, timeline creation, and postmortem generation. Use when user mentions incident, outage, production issue, debugging production, service down, error spikes, or postmortem. --- # Incide

--- name: finding-stale-todos description: Find and analyze stale TODO, FIXME, HACK comments in codebases using git history. Use when user mentions stale TODOs, old comments, tech debt cleanup, forgotten TODOs, or code archaeology. run-in-subagent: true allowed-tools: - View - Bas

Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

--- name: codebase-onboarding description: Help developers understand unfamiliar codebases quickly. Use when user mentions onboarding, understanding code, architecture overview, codebase tour, project structure, or asks "how does this work" about a project. --- # Codebase Onboarding Skil

--- name: fullstack-feature-generator description: Generate complete full-stack features with database models, API routes, UI components, and tests in one workflow. Use when user asks to add a feature, create CRUD operations, scaffold endpoints, or build complete functionality across f

Best practices for building Stripe integrations. Use when implementing payment processing, checkout flows, subscriptions, webhooks, Connect platforms, or any Stripe API integration.

Production hardening checklist derived from the actual stack. HTTP headers, dependency scanning, secret management, input validation, error handling, CSP, CORS. Not a generic OWASP list — reasoned from the specific architecture. Use before deployment, after adding external integrations, or at phase boundaries.

--- name: finding-empty-catches description: Find empty catch blocks and silent error handlers that swallow exceptions. Use when user mentions silent failures, error swallowing, empty catch, ignored exceptions, or debugging mysterious production issues. allowed-tools: - View - Bash

# FastAPI Patterns Best practices and patterns for FastAPI projects with SQLAlchemy 2.0 and dependency-injector. ## Triggers Use this skill when the user: - Creates a new FastAPI project or module - Asks about FastAPI application structure - Works with SQLAlchemy models and repositories - Configu

Document ingestion and semantic search with RAG capabilities. Supports PDF, DOCX, MD, TXT, CSV, HTML, and JSON. Combines intelligent chunking, vector embeddings, and persistent storage for building searchable knowledge bases.

Orchestrate Google Play beta testing groups and distribution using gpd. Use when managing testers, internal testing, or beta rollouts.

Use when executing multi-step processes requiring state persistence and agent coordination - defines two-tier protocol where subagents report PASS/FAIL status and main agent handles dispatch, advancement, and failure troubleshooting

Create and manage Linear issues following Helioy ways of working. Use when creating issues, planning features, breaking down work, or organizing tasks in Linear. Enforces parent/sub-issue pattern, proper sizing, and metadata conventions.