1,153 件 ・ 関連度順
概要と使いどころ
Use when a task needs the judgment of an Area, Ethnic, or Cultural Studies Professor — designing a joint-appointment course load across two departments, prepping a tenure or mid-tenure review file for interdisciplinary scholarship, deciding whether a course survives an enrollment or political-pressure threat, evaluating community-engaged research for a merit case, or writing a Title VI/FLAS-adjacent grant narrative.
日本語の概要は準備中です。原文の説明を表示しています。
Search LCSC Electronics for electronic components — find parts by LCSC number (Cxxxxx) or MPN, check stock/pricing, download datasheets, analyze specifications. Sister company to JLCPCB, same parts library. Sync and maintain a local datasheets directory for a KiCad project. No API key needed — uses the free jlcsearch community API. Use this skill when the user mentions LCSC, JLCPCB parts library, JLCPCB assembly parts, production sourcing, Cxxxxx part numbers, needs to find LCSC equivalents for parts, is preparing a BOM for JLCPCB assembly, or wants to download datasheets and LCSC is available. For package cross-reference tables and BOM workflow, see the `bom` skill.
日本語の概要は準備中です。原文の説明を表示しています。
Run professional Discord servers — community structure, moderation, events, bots, and engagement for teams and audiences.
日本語の概要は準備中です。原文の説明を表示しています。
Repurpose blog posts for social media, email, video, podcast, and community channels. Generates Twitter/X threads, LinkedIn posts and articles, Threads, Bluesky, TikTok, Instagram, YouTube Shorts and long-form scripts, Reddit, newsletter, podcast, Discord, and Slack variants. Adapts tone for each platform. Use when user says "repurpose", "blog repurpose", "share blog", "social media", "twitter thread", "linkedin post", "youtube script", "reddit post".
日本語の概要は準備中です。原文の説明を表示しています。
Use when configuring OmniStudio at the org level: enabling Standard Runtime, selecting the Runtime Namespace, assigning Permission Set Licenses, toggling feature settings, and granting Experience Cloud community access. Trigger keywords: OmniStudio Settings, Standard OmniStudio Runtime, managed package runtime, runtime namespace, OmniStudio Permission Set, OmniStudio PSL. NOT for moving an org off the vlocity namespace — use omnistudio/vlocity-to-native-omnistudio-migration. NOT for deciding whether to adopt OmniStudio — use architect/omnistudio-vs-standard-decision.
日本語の概要は準備中です。原文の説明を表示しています。
Migrating Classic Knowledge (KnowledgeArticleVersion / Article Types) to Lightning Knowledge (Knowledge__kav with record types): article-type-to-record-type mapping, multi-language translation preservation, data category re-architecture, file attachment porting, version and publication-state retention, channel visibility translation, and downstream Case Feed / Community / Bot rewiring. NOT for new Lightning Knowledge setup or editorial publishing workflow design (use admin/knowledge-base-administration).
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up CMS workspaces, creating or publishing content types for Experience Cloud sites, managing content scheduling, or configuring audience targeting on content variants. Triggers: 'set up CMS workspace', 'publish content to Experience Cloud site', 'content scheduling community', 'audience targeting content', 'managed content vs unmanaged', 'custom content type metadata', 'CMS channel configuration'. NOT for moderating member-posted content — use admin/experience-cloud-moderation. NOT for Knowledge vs an external CMS or CMS Connect — use architect/knowledge-vs-external-cms.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or configuring public pages on an Experience Cloud site — guest user profile setup, page-level access settings in Experience Builder, object/field visibility for unauthenticated visitors, and explicit sharing rules that expose data on public pages. Triggers: 'configure public pages Experience Cloud', 'guest user profile setup', 'unauthenticated site access', 'public community page visibility', 'make page visible without login'. NOT for authenticated user features (use admin/experience-cloud-member-management). NOT for security hardening or remediation of guest user exposure (use security/guest-user-security). Also covers the deployable shape: pageAccess on the route file, the guest Profile's objectPermissions and fieldPermissions, sharingGuestRules, siteGuestRecordDefaultOwner on CustomSite, and the Network guest flags.
日本語の概要は準備中です。原文の説明を表示しています。
Use when admins are governing the Chatter group lifecycle — creation policy, public/private/unlisted visibility decisions, group ownership transfer when owners leave, archived vs inactive vs deleted state changes, auto-archive behavior, naming conventions, group templates (Information Templates), and orphan-group cleanup after user terminations. Triggers: 'we have 800 dead chatter groups', 'group owner left the company who owns it now', 'should this group be public private or unlisted', 'when does a chatter group auto-archive', 'how do I delete vs archive a chatter group', 'we need a chatter group naming convention'. NOT for Chatter notification / digest / feed-noise tuning (use admin/chatter-notification-tuning), NOT for Chatter REST API integration patterns (use apex/apex-connect-api-chatter), NOT for Custom Notifications API (use apex/apex-custom-notifications-from-apex), NOT for Experience Cloud / Customer Community group access (different sharing model).
日本語の概要は準備中です。原文の説明を表示しています。
Rewrite a support response in a different tone - formal, casual, technical, empathetic, or concise.
日本語の概要は準備中です。原文の説明を表示しています。
Search the knowledge base in [Notion](https://composio.dev/toolkits/notion) for answers to customer questions.
日本語の概要は準備中です。原文の説明を表示しています。
Bulk verify customer email addresses using [Clearout](https://composio.dev/toolkits/clearout) or [Mailcheck](https://composio.dev/toolkits/mailcheck)
日本語の概要は準備中です。原文の説明を表示しています。
Draft a customer support email reply based on ticket context.
日本語の概要は準備中です。原文の説明を表示しています。
Identify churned or at-risk customers and draft personalized winback emails
日本語の概要は準備中です。原文の説明を表示しています。
Manage and resolve [Intercom](https://composio.dev/toolkits/intercom) conversations — triage, reply, snooze, or close
日本語の概要は準備中です。原文の説明を表示しています。
Generate a support metrics summary from [Gorgias](https://composio.dev/toolkits/gorgias) tickets and optionally push to [Google Sheets](https://composio.dev/toolkits/googlesheets)
日本語の概要は準備中です。原文の説明を表示しています。
Enrich customer/lead profiles with business data using [LeadIQ](https://composio.dev/toolkits/leadiq), [RocketReach](https://composio.dev/toolkits/rocket-reach), or [Clearout](https://composio.dev/toolkits/clearout)
日本語の概要は準備中です。原文の説明を表示しています。
Pull open tickets from [Zoho Desk](https://composio.dev/toolkits/zoho-desk) and triage by priority and department
日本語の概要は準備中です。原文の説明を表示しています。
Analyze customer message text for sentiment, urgency, and emotional tone.
日本語の概要は準備中です。原文の説明を表示しています。
Check SLA compliance across open tickets and flag breaches or at-risk tickets
日本語の概要は準備中です。原文の説明を表示しています。
Analyze ticket history to identify patterns and generate reusable support macros/playbooks.
日本語の概要は準備中です。原文の説明を表示しています。
Set up customer outreach sequences via [Lemlist](https://composio.dev/toolkits/lemlist), [Reply.io](https://composio.dev/toolkits/reply-io), or [Woodpecker](https://composio.dev/toolkits/woodpecker-co)
日本語の概要は準備中です。原文の説明を表示しています。
Identify VIP/high-value customer tickets and flag them for priority handling.
日本語の概要は準備中です。原文の説明を表示しています。
Translate a customer message and draft a reply in their language.
日本語の概要は準備中です。原文の説明を表示しています。