Loading...
Loading...
Found 8,772 Skills
Manage video production projects including character profiles, project manifests, workflow history, and asset tracking. Use when creating new projects, managing characters, or tracking production state.
This skill should be used when the user asks to "create a GitHub Actions workflow", "set up CI/CD", "configure GitHub Actions", "add automated testing", "deploy with GitHub Actions", or needs guidance on GitHub Actions workflows, syntax, or automation.
Generates importable n8n workflow JSON files that sync data between Personize and 400+ apps. Produces ready-to-import workflows for batch sync, webhook ingestion, per-record AI enrichment, and data export — no code required. Use this skill whenever the user wants no-code integrations, visual workflows, n8n automation, or to connect Personize to HubSpot, Salesforce, Google Sheets, Slack, Postgres, or any app without writing code. Also trigger when they mention 'workflow automation', 'scheduled sync without code', 'visual pipeline', or 'connect Personize to [app]' and don't want to write TypeScript.
Guides writing academic papers section by section using an 11-step workflow with LaTeX templates and counterintuitive writing tactics. Covers Abstract, Introduction, Method, Experiments, Related Work, Conclusion, and Supplementary. Use when: user asks to write or draft a paper section, needs LaTeX templates, wants to improve academic writing quality, optimize novelty framing, or mentions 'write introduction', 'draft method', 'paper writing'. Do NOT use for pre-submission review (use paper-review), experiment execution (use experiment-pipeline), or paper planning/story design (use paper-planning).
Swap faces in a video using AI via the HeyGen API. Use when: (1) Replacing a face in a video with another face, (2) Face swapping from a source image onto a target video, (3) Creating personalized videos by swapping in a person's face, (4) Working with HeyGen's /v1/workflows/executions endpoint for face swap processing.
Use this skill when working with internationalization (i18n), localization (l10n), translation workflows, right-to-left (RTL) layout support, pluralization rules, or ICU MessageFormat syntax. Triggers on translating strings, setting up i18n libraries (react-intl, i18next, FormatJS), handling plural forms, formatting dates/numbers/currencies for locales, building translation pipelines, configuring RTL stylesheets, or writing ICU message patterns with select/plural/selectordinal.
Extract learnings about Claude Code behavior from a session and add them to the project's CLAUDE.md file. Use for behavioral rules, workflow patterns, and project-specific instructions that apply to the main Claude Code agent. Invoke via /update-claude-learnings after sessions revealing behavioral patterns.
Convert PDF files into editable Word and Markdown outputs with the bundled conversion scripts and workflow guide.
Use this skill when facilitating remote team collaboration - async-first workflows, documentation-driven decision making, meeting facilitation, and distributed team communication. Triggers on designing async processes, writing RFCs or decision docs, preparing meeting agendas, running standups or retros, establishing communication norms, reducing meeting load, or improving handoff quality across time zones.
[Trigger] When PPT workflow needs SVG slide quality review via Gemini. [Output] Structured review assessment with scores, pass/fail, and fix suggestions. [Skip] For content authoring or SVG generation tasks (those are handled by Claude). [Ask] No user input needed; invoked by review-core agent. [Resource Usage] Use references/, scripts/ (`scripts/invoke-gemini-ppt.ts`).
Capsule CRM integration. Manage crm and sales data, records, and workflows. Use when the user wants to interact with Capsule CRM data.
Classify user requests and route to the correct agent + skill combination. Use for any user request that needs delegation: code changes, debugging, reviews, content creation, research, or multi-step workflows. Invoked as the primary entry point via "/do [request]". Do NOT handle code changes directly - always route to a domain agent. Do NOT skip routing for anything beyond pure fact lookups or single read commands.