Loading...
Loading...
Found 8,761 Skills
Use when setting up, deploying, or operating vLLM Studio (env keys, controller/frontend startup, Docker services, branch workflow, and release checklists).
Batch processing for Obsidian vaults: bulk tag normalization, wikilink extraction/fixing, frontmatter edits, vault analysis, and migration workflows. Use when asked to analyze or modify many notes in an Obsidian vault at scale, or to script/automate vault-wide changes.
The orchestration layer for AI-native creative production. This skill coordinates multiple AI tools—video, image, audio, digital humans, effects—into cohesive campaigns, productions, and creative systems. As AI tools proliferate, the challenge shifts from "can we create this?" to "how do we orchestrate these capabilities into something coherent?" The AI Creative Director thinks in systems, not tools. In pipelines, not one-offs. In brand consistency across AI-generated assets. This is where creative vision meets technical orchestration. The AI Creative Director doesn't just use AI tools—they compose them into creative instruments that produce at scales and speeds previously impossible. Use when "AI creative director, orchestrate AI, AI campaign, multi-tool, AI workflow, AI pipeline, coordinate AI, AI production, AI creative system, full AI production, AI at scale, orchestration, creative-direction, ai-production, workflow, pipeline, multi-tool, scale, quality-control" mentioned.
Diagnose and fix GitHub Actions CI failures. Inspects workflow runs and logs, identifies root causes, implements minimal fixes, and pushes to a fix branch. Use when CI is failing, red, broken, or needs diagnosis.
Extracts valuable learnings, patterns, and workflows from conversations and persists them as reusable skill files. This skill should be used when a complex problem was solved, a valuable workflow was discovered, or the user explicitly requests to capture knowledge as a skill.
Send push notifications via ntfy.sh with a lightweight shell workflow. Use when posting alerts, job status updates, reminders, or automation results to an ntfy topic using token auth or public topics.
Work with the Inpoxia repository's local tools and workflows for CLI usage, GraphMail library changes, and quality checks. Use when tasks involve running or updating `inpoxia` commands, modifying files under `src/inpoxia/**`, validating behavior with `pytest`, or enforcing style/type checks with `ruff` and `pyright`.
Async job processing patterns for background tasks, Celery workflows, task scheduling, retry strategies, and distributed task execution. Use when implementing background job processing, task queues, or scheduled task systems.
Implementation workflows and decision trees for Frappe Document Controllers. Use when determining HOW to implement server-side DocType logic: lifecycle hooks, validation patterns, autoname, submittable workflows, controller override. Triggers: how do I implement controller, which hook to use, validate vs on_update, override controller, submittable document, autoname pattern, flags system.
Automate ML workflows with Airflow, Kubeflow, MLflow. Use for reproducible pipelines, retraining schedules, MLOps, or encountering task failures, dependency errors, experiment tracking issues.
Create and audit GitHub Actions workflows with SHA pinning, permissions, and caching checks. Use when adding CI/CD, reviewing workflow files, or fixing action pinning.
Find past solutions before starting work - search errors you've fixed, files you've changed, similar questions you've asked, tool workflows that succeeded. Reduces web research and prevents redundant work.