Loading...
Loading...
Found 586 Skills
Claude Code CLI commands, flags, headless mode, and automation patterns
ABC Jenkins Project Deployment Skill. Supports intelligent parameter inference and interactive triggering of Jenkins builds, automatically retrieves Git branch and tag information. This skill is triggered when users request "Deploy Jenkins", "Trigger Build", "Deploy Project", "Jenkins Deployment" or similar operations. Requires environment variables JENKINS_USER and JENKINS_TOKEN.
Validates agent skill definitions against agentskills.io and AGENTS.md rules. Use when creating or modifying skills to ensure they are machine-readable and documentation-complete.
Comprehensive toolkit for generating best practice GitHub Actions workflows, custom local actions, and configurations following current standards and conventions. Use this skill when creating new GitHub Actions resources, implementing CI/CD workflows, or building reusable actions.
ShellCheck validation as non-negotiable 2025 workflow practice
Use when establishing tests, monitoring, and incident response for analytics models.
Use Slopwatch to detect LLM reward hacking in .NET code changes. Run after every code modification to catch disabled tests, suppressed warnings, empty catch blocks, and other shortcuts that mask real problems.
Show infrastructure standards compliance status (read-only)
Deploy Customer.io integrations to production. Use when deploying to cloud platforms, setting up production infrastructure, or automating deployments. Trigger with phrases like "deploy customer.io", "customer.io production", "customer.io cloud run", "customer.io kubernetes".
Execute end-to-end tests covering full user workflows across frontend and backend. Use when performing specialized testing. Trigger with phrases like "run end-to-end tests", "test user flows", or "execute E2E suite".
Deploy project to hosting platform — read stack YAML for exact config, detect local CLI tools (vercel, wrangler, supabase, fly, sst), set up database, push code, verify live deployment. Use when user says "deploy it", "push to production", "set up hosting", or after /build completes. Do NOT use before build is complete.
Optimize Playwright E2E tests by removing anti-patterns, implementing smart waits, enabling test sharding, and improving reliability.