'gather' 검색 결과

Gather business context before analysis by checking connected or provided sources for metric definitions, recent changes, and decision background. Produce a focused context note that preserves source references, conflicting evidence, assumptions, and remaining gaps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying metric definitions before analysis
• Checking recent changes before investigating performance
• Reconciling conflicting sources before writing a report

Use when gathering requirements for a customer portal, partner community, or self-service Experience Cloud site. Triggers: 'gathering requirements for customer portal', 'planning Experience Cloud site', 'what license for community portal', 'portal user journey mapping', 'self-service requirements'. NOT for building the site in Experience Builder — use admin/experience-cloud-site-setup. NOT for designing the deal-registration and MDF processes themselves — use admin/partner-community-requirements. More trigger keywords: portal persona licence matrix, which Experience Cloud licence do these requirements imply, external user needs a Contact and Account, sharing set vs sharing rule for a portal, self-registration vs SSO for a portal, portal requirements catalogue, handoff to Experience Cloud site setup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Gather scholarly evidence for a scientific manuscript or research brief. Organize supporting and conflicting findings into references, study comparison tables, and claim-to-source maps, with search records and coverage reports that help identify gaps requiring further review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Gather background literature for a manuscript
• Compare supporting, conflicting, and null findings
• Build study comparison tables and claim-to-source maps

Map an organization's internet-facing assets using public information, including domains, indexed services, employee details, and leaked data. Compile findings into a reconnaissance report to support authorized security assessments and identify potential exposure.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Gathering public information before a penetration test
• Finding unknown internet-facing assets
• Checking public sources for leaked credentials and documents

Search YouTube by keyword and collect linked video and comment datasets through the BrowserAct API. Gather titles, views, comment text, likes, and reply counts to support audience feedback research and topic monitoring.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Gathering viewer feedback for a specific topic
• Researching audience discussions around competitor videos
• Collecting comments about trending search terms

Collect Amazon product reviews by supplying an ASIN, Amazon's product identifier. BrowserAct returns ratings, review text, publication dates, reviewer details, and verified purchase status without an Amazon login, providing data for feedback research and competitor comparisons.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Gathering reviews of competing products
• Collecting feedback to identify product improvements
• Preparing comparisons by verified purchase status

Gather structured product data from Amazon search results using keywords, a brand filter, and a product limit. Collect prices, ratings, review counts, availability, and delivery details for market research or product catalog preparation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Research products from a specific brand
• Compare prices and purchase availability
• Collect ratings and review counts for competitor research

Collect DTMF input and speech from callers using standard gather or AI-powered gather. Build interactive voice menus and AI voice assistants. This skill provides Python SDK examples.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Collect DTMF input and speech from callers using standard gather or AI-powered gather. Build interactive voice menus and AI voice assistants. This skill provides JavaScript SDK examples.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Collect DTMF input and speech from callers using standard gather or AI-powered gather. Build interactive voice menus and AI voice assistants. This skill provides Ruby SDK examples.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Collect DTMF input and speech from callers using standard gather or AI-powered gather. Build interactive voice menus and AI voice assistants. This skill provides Go SDK examples.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Collect DTMF input and speech from callers using standard gather or AI-powered gather. Build interactive voice menus and AI voice assistants. This skill provides REST API (curl) examples.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Collect DTMF input and speech from callers using standard gather or AI-powered gather. Build interactive voice menus and AI voice assistants. This skill provides Java SDK examples.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Systematically gather comprehensive travel itinerary requirements through structured discovery questions, MCP-powered research (Perplexity, Exa), and expert detail gathering. Use when users request travel planning, itinerary creation, or trip assistance requiring deep research and personalized requirements gathering. Outputs detailed requirements specification with day-by-day itineraries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when gathering, structuring, and documenting requirements for a Financial Services Cloud (FSC) wealth management implementation — including financial planning workflow discovery, portfolio review process mapping, client lifecycle requirements, advisor tooling needs, and FSC architecture determination (managed package vs. FSC Core). Trigger keywords: wealth management requirements, FSC requirements gathering, financial planning workflow, portfolio review process, advisor tools setup, FSC data model scoping, wealth management process mapping. NOT for implementation, configuration, or code — use financial-account-setup, fsc-action-plans, or apex/fsc-financial-calculations for those. NOT for FSC architecture decisions — use architect/wealth-management-architecture. NOT for Health Cloud or NPSP requirements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Eliciting, documenting and structuring requirements for a Salesforce implementation: stakeholder discovery interviews, As-Is and To-Be process mapping, and gap analysis against standard Salesforce capability. Trigger keywords: requirements gathering, user story, As-Is To-Be, gap analysis, stakeholder interview, process mapping, business requirements, fit gap. NOT for authoring the user stories themselves - use admin/user-story-writing-for-salesforce. NOT for scoring requirements against a specific org - use admin/fit-gap-analysis-against-org. NOT for technical design decisions - use architect/solution-design-patterns. Also covers the requirements catalogue itself (one row per requirement, MoSCoW priority, source stakeholder, downstream target) and Salesforce non-functional requirements: record volume, sharing layer, integration pattern, reporting joins, mobile/offline, and licence implication.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to elicit, document, and validate CRM Analytics requirements — covering data source mapping (Salesforce object sync vs external connector vs Data Cloud), transformation needs, audience-specific lens or dashboard views, and drill-down path specifications — before any dataset or dashboard is built. Trigger keywords: CRM Analytics requirements, analytics data source mapping, CRM Analytics audience requirements, analytics visualization requirements. NOT for the formula and target behind each KPI — use admin/analytics-kpi-definition. NOT for building the dashboard once requirements are agreed — use admin/analytics-dashboard-design.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

검색과 평가를 반복하여 하위 에이전트의 작업에 필요한 코드와 배경 정보를 추립니다. 발견한 용어와 부족한 정보를 다음 검색에 반영해 관련 파일을 모읍니다.

• 결함 수정 담당자에게 필요한 파일 찾기
• 기능 추가 전 기존 구현 수집
• 프로젝트 용어에 맞춰 검색 조정

웹 정보를 여러 관점에서 조사해 데이터·사례·전문가 의견을 정리합니다. 글이나 자료를 만들기 전에 정보의 최신성, 반대 의견과 한계도 확인합니다.

• 글을 쓰기 전 근거 자료 수집
• 발표 자료에 쓸 데이터와 사례 수집
• 기술과 그 한계 비교

Inspect Figma screens to gather details for implementation, including component variants, spacing, shared design settings, and image assets. It helps an agent understand layouts and design libraries before turning a design into code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Gathering implementation details from a Figma screen
• Checking component variants and spacing
• Extracting image assets for implementation

Retrieve lab results and clinician notes from Function Health. Summarize biomarker names, collection dates, values, and reference ranges, and gather the available history for reviewing changes over time without filling gaps in the records.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing lab values and reference ranges
• Gathering past lab results to review changes
• Reading clinician consultation notes

Find autonomous AI agents, frameworks, and tools through AgentFolio. Compare their capabilities, intended users, integrations, and deployment options to shortlist existing products or gather examples and ideas before designing an agent of your own.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding existing agents before building your own
• Shortlisting agent vendors for evaluation
• Researching competitors and market gaps

Gather information from multiple Notion pages and combine it into briefs, summaries, comparisons, or detailed reports. Include citations and source links, identify missing or conflicting evidence, and document findings in Notion.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Summarize information scattered across Notion
• Compare options using existing internal sources
• Prepare reports with citations and source links

Classify a failed NemoClaw GitHub Actions job using logs with sensitive information hidden and output size limited. Optionally inspect saved artifacts to identify failure patterns and gather evidence for further investigation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Classifying a failed GitHub Actions job
• Inspecting saved artifacts for failure evidence
• Gathering initial evidence for an E2E failure