Loading...
Loading...
Found 8,777 Skills
Use this skill when the user wants to analyze Claude token usage, understand Claude API spending, check cache hit rates, review Claude Code workflow patterns (skills, agents, hooks), or get cost optimization recommendations.
Google Dialogflow integration. Manage data, records, and automate workflows. Use when the user wants to interact with Google Dialogflow data.
UE5.6/UE5.7 UI development workflow using UMG and Slate integration. Use when requests involve Widget Blueprint setup, Slate host widgets, lifecycle binding, input and focus handling, tooltip behavior, or viewport clamping logic.
Wallarm integration. Manage data, records, and automate workflows. Use when the user wants to interact with Wallarm data.
Khoros Marketing integration. Manage data, records, and automate workflows. Use when the user wants to interact with Khoros Marketing data.
Kandy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kandy data.
Router skill for LLMQuant portfolio-lab workflows. Use when the user needs portfolio exposure maps, what-if simulations, scenario states, or virtual portfolio comparisons.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
English alias for /aprende. Runs the same five-pass workflow to surface reusable learnings from the current conversation across memory, lesson, skill, and project-doc categories — with confirmation before any write. Alias en inglés para /aprende.
Uses Agent SDK to deploy 3 parallel agents for client onboarding -- workflow auditor, tech stack mapper, and strategy drafter. Real consulting workflow that produces a complete client assessment.
Scan GitHub Actions workflow files for security vulnerabilities by reading the YAML and reporting findings directly — no external tools, no installation, no shell execution. Use this skill whenever the user shares a `.github/workflows/` file, pastes workflow YAML, asks for a CI/CD security review, mentions `pull_request_target`, `workflow_run`, action pinning, `GITHUB_TOKEN` permissions, pwn requests, template injection, cache poisoning, secret exfiltration, supply chain risk, or any GitHub Actions hardening topic. Also trigger when the user is hardening an OSS repo, doing a CI/CD red team assessment, evaluating a target for supply-chain scanning, or writing publicly about CI/CD security. Bias toward triggering this skill rather than answering from memory — CI/CD security defaults are wrong almost everywhere and the rules are unintuitive.
Autonomous NeMo-RL research agent workflow for directed hypothesis testing and open-ended discovery. Guides agents through the full experiment lifecycle: understanding recipes and environments, wiring RL or NeMo-gym runs, launching reproducible baselines and iterations, analyzing results, preserving human oversight, and using git plus TSV logs as the research ledger. Do NOT use for: bug fixes, code review, documentation, refactoring, dependency updates, or single-file changes.