Total 51,031 skills, Tools & Utilities has 8324 skills
Showing 12 of 8324 skills
KUDO platform help — enterprise real-time AI speech translation and human interpretation in 200+ languages, embeddable widget for any meeting platform, 12,000+ interpreter marketplace, SOC 2 Type 2 + ISO 27001. Use when setting up KUDO for multilingual meetings or conferences, choosing between AI speech translation and human interpreters on KUDO, KUDO embeddable widget not working on a third-party event platform, comparing KUDO vs Interprefy vs Wordly vs JotMe for live interpretation, understanding KUDO Pro vs ProPlus vs ProPlatinum vs Enterprise pricing, or embedding KUDO translation into a hybrid event workflow. Do NOT use for choosing between all AI note-takers (use /sales-note-taker) or reviewing a call for coaching (use /sales-call-review).
Free open-source macOS cleaner built with SwiftUI — CleanMyMac alternative with zero telemetry, scheduled auto-cleaning, and Xcode/Homebrew/system cache cleanup.
Recruit CRM integration. Manage Candidates, Jobs, Companies, Users, Notes, Files and more. Use when the user wants to interact with Recruit CRM data.
Write or regenerate a value-first pull-request description (title + body) for the current branch's commits or for a specified PR. Use when the user says 'write a PR description', 'refresh the PR description', 'regenerate the PR body', 'rewrite this PR', 'freshen the PR', 'update the PR description', 'draft a PR body for this diff', 'describe this PR properly', 'generate the PR title', or pastes a GitHub PR URL / #NN / number. Also used internally by ce-commit-push-pr (single-PR flow) and ce-pr-stack (per-layer stack descriptions) so all callers share one writing voice. Input is a natural-language prompt. A PR reference (a full GitHub PR URL, `pr:561`, `#561`, or a bare number alone) picks a specific PR; anything else is treated as optional steering for the default 'describe my current branch' mode. Returns structured {title, body_file} (body written to an OS temp file) for the caller to apply via gh pr edit or gh pr create — this skill never edits the PR itself and never prompts for confirmation.
WeChat Official Account Layout | Markdown to HTML | Layout Themes | Paragraph Styles — One-click layout tool for WeChat Official Accounts, converts Markdown manuscripts to HTML that can be pasted into WeChat backend, supports multiple themes, font sizes, paragraph style switching, and WYSIWYG. Targeted at WeChat Official Account editors, independent authors, and layout specialists. Trigger words: 'layout', 'format', 'beautify', 'formatting', 'font size', 'paragraph style', 'change layout theme', 'change format', 'convert to HTML', 'make it look better', 'adjust format'. For changing preset packages/brand packages/complete theme color schemes, use aws-wechat-article-assets; for multi-link workflows (writing + review + layout + image matching + publishing), use aws-wechat-article-main.
Meltwater platform help — media intelligence, social listening, media relations (journalist database + outreach), influencer marketing, social media management, consumer intelligence, Mira AI, API, and integrations. Use when Meltwater Explore searches return noisy results, media monitoring is missing coverage, journalist contacts are outdated, influencer campaigns aren't tracking properly, social publishing isn't scheduling, Meltwater API or Mira AI isn't returning expected data, or CRM/BI integrations aren't syncing. Do NOT use for cross-platform social listening strategy (use /sales-social-listening), cross-platform media relations strategy (use /sales-media-relations), cross-platform influencer marketing strategy (use /sales-influencer-marketing), or email deliverability (use /sales-deliverability).
Jamie platform help — bot-free AI meeting note-taker, REST API with personal and workspace keys, webhook automations, CRM sync to HubSpot/Salesforce/Attio, MCP server for Claude/ChatGPT/Cursor. Use when setting up Jamie for a sales team, connecting Jamie webhooks to Make.com or a custom endpoint, pulling meeting transcripts and summaries via Jamie API, syncing Jamie action items to Asana or CRM, troubleshooting Jamie not recording or missing speakers, comparing Jamie pricing tiers, or configuring Jamie speaker recognition. Do NOT use for choosing between note-takers (use /sales-note-taker) or reviewing a specific call for coaching (use /sales-call-review).
Later platform help — social media scheduling, visual content calendar, Linkin.bio shoppable pages, analytics, Later Influence (influencer discovery, campaign management, Reporting API). Use when Later posts not publishing on schedule, Linkin.bio links not working, unsure about best posting times, Later Influence campaigns underperforming, or Later Influence API not returning expected data. Do NOT use for social media management strategy or tool comparison (use /sales-social-media-management), influencer marketing strategy (use /sales-influencer-marketing), Sprout Social config (use /sales-sproutsocial), or social listening (use /sales-social-listening).
Forms On Fire integration. Manage Forms, Users, Groups. Use when the user wants to interact with Forms On Fire data.
Author step content for Novu workflows defined in the Dashboard or generated/edited via the Novu MCP. Use when filling in step controls (subject, body, editorType, headers, body, conditions) for email, in-app, sms, push, chat, delay, digest, throttle, or HTTP Request steps.
Timekit integration. Manage data, records, and automate workflows. Use when the user wants to interact with Timekit data.
Build code-first notification workflows with @novu/framework. Use when defining workflows in TypeScript (Zod / JSON Schema / Class Validator), composing channel steps (email, SMS, push, chat, in-app) with action steps (delay, digest, custom), exposing Step Controls for non-technical teammates, rendering React/Vue/Svelte Email templates, hosting the Bridge Endpoint inside Next.js, Express, NestJS, Remix, Nuxt, SvelteKit, H3, or AWS Lambda, syncing to Novu Cloud via CLI / GitHub Actions, securing production with HMAC, or implementing translations, hydration, multi-channel orchestration, and LLM-powered notification logic in code.