Total 50,313 skills, AI & Machine Learning has 8452 skills
Showing 12 of 8452 skills
This skill should be used when the user says "interview me about", "help me clarify", "stress-test my idea", "let's explore this concept", "challenge my assumptions about", "grill me on", "drill into my plan", or needs structured questioning to refine and articulate their thinking.
Turn papers, technical articles, or knowledge content into highly realistic AIGC slides. First create a narrative structure and page-by-page visual direction, then call an image generation model to produce a 16:9 slide image for each page, and finally synthesize into PPTX/PDF. Suitable for paper presentations, group meetings, open courses, technical sharing, and commercial research presentations; use this skill when users mention "paper PPT", "AI-generated PPT", "PPT that doesn't look like AI", "high-quality slides", or "page-by-page AI-generated PPT".
Build an operator-level compute template for an LLM and estimate FLOPs/MFU for a serving shape. Use when you need tensor shapes, per-op FLOPs, kernel-to-op MFU mapping, or parallelism what-if analysis.
For use when students **have completed WG-12 to WG-21** (single-file consolidation blueprint) and are working on **WG-22 Code Splitting** (`agent_core.py` + `main.py`). **First message in a new session**: Display PEAS brand screen and confirm readiness first; after confirmation, **lay out the context** before proceeding to requirement clarification. If **`prompts/` or `templates/`** are missing, copy them from `references/project_assets/` to the project root. Process: Spec Alignment (2d′) → Six-column Contract → **In-session Handoff Implementation** → Acceptance. Starting point: starter_main_wg21.py; Standard reference: reference_agent_core.py + reference_main.py. Triggers: peas-workshop-advanced-coach, PEAS workshop advanced coach, WG-22, code splitting coach, Agent.chat.
Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before /code-review and /story-done.
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
Redis LangCache guidance for semantic caching of LLM responses on Redis Cloud — calling search/set via the SDK or REST API, tuning the similarity threshold, separating caches per task type, and filtering with custom attributes. Use when caching LLM completions or RAG answers to cut API cost and latency, building a cache-aside layer in front of OpenAI / Anthropic / etc., tuning hit rate vs precision, or splitting one app's LLM workloads into multiple LangCache caches.
Redis vector search guidance covering HNSW vs FLAT algorithm choice, vector index configuration (dims, distance metric, datatype), filtered hybrid search combining vector similarity with TAG or NUMERIC filters, and the RAG retrieval pattern with RedisVL. Use when defining a VECTOR field in FT.CREATE, integrating embeddings (OpenAI, Cohere, sentence-transformers), tuning HNSW parameters (M, EF_CONSTRUCTION, EF_RUNTIME), building a retrieval-augmented generation pipeline, or filtering vector results by attribute.
Rewrite AI-generated text to sound natural and human-written. Removes LLM tells — cliché phrases, predictable structure, inflated language, and robotic patterns. Use when editing drafts, emails, articles, or any text that reads like it was written by AI.
Automate content creation from research to video generation using Claude/OpenAI and Remotion
Manages Dify via bundled CLI: pull/export DSL, patch working.yml, deploy, cache remote files, upload to Dify, run/chat workflows. Use when the user mentions Dify, workflow DSL, pull, deploy, dify-manage, or Dify file inputs.
Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.