← Todos los skills

motion-pipeline

ComunidadMIT

CPU-only motion data processing pipeline for game animation: BVH import, contact detection, root decomposition, motion blending, FABRIK IK. No GPU required.

El ZIP contiene solo este skill. Está en GitHub Releases del repo público orlandoneto/agent-skills — Ontoom es la vitrina. El crawler diario actualiza el catálogo.

Cómo instalar

  1. Descarga el ZIP y extrae la carpeta del skill.
  2. Cursor: .agents/skills/notque-motion-pipeline/ o .cursor/skills/notque-motion-pipeline/
  3. Claude Code: .claude/skills/notque-motion-pipeline/
  4. Otras IAs: .agents/skills/notque-motion-pipeline/
cursorclaude-codecodexgeminiany

Origen / créditos: notque/vexjoy-agent

Otros skills de esta colección

Otras colecciones

  • news-collection

    Collect, filter, and freshness-qualify news items.

  • ngrx-feature-scaffold

    Scaffolds a complete NgRx feature module (actions, reducer, effects, selectors, facade, models, tests) using modern Angular patterns. Use when adding a new feature slice to an Angular + NgRx app, standardizing existing ad-hoc state code, or bootstrapping state for a new library in an Nx monorepo.

  • performance

    Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".

  • planning

    Create and manage persistent markdown planning files for structured task execution. Use when the user asks to "create a plan", "track progress", "start a research project", or when a task requires more than 5 tool calls and needs structured phase tracking to stay focused and avoid goal drift.

  • plant-seed

    Capture forward-looking idea as a seed for future feature design.

  • prompt-engineering-patterns

    Structures prompts for LLM applications — role usage, delimiters, chain-of-thought, few-shot examples, structured output, prompt caching, and when to stop tuning and reach for RAG or fine-tuning instead. Use when building an LLM feature, rewriting a flaky prompt, moving from a prototype to production, or reviewing prompts in code review.