508 skills · sorted by relevance
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.
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.
The English summary is being prepared. Showing the original description.
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.
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.
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.
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.
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.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Gather relevant code and background for subagents, agents assigned part of a larger task. Search broadly, assess each file, identify missing information, and refine the search for up to three cycles to assemble context for bug fixes or feature work.
Research a topic across multiple web sources before writing articles, reports, or presentations. Gather facts, examples, and expert views, then check current information, competing perspectives, and limitations to build a well-supported understanding.
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.
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.
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.
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.
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.
Plan and build AI agents on Google Cloud, from gathering requirements to choosing a single-agent or multi-agent design. Produce architecture diagrams, deployment code and instructions, and validation plans tailored to the workload.
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.
Turn a feature idea into a specification through structured questions about users, business goals, and technical constraints. Produce requirements, user stories, testable acceptance criteria, and an implementation checklist, including performance, security, and error handling.
Audit a development milestone before archiving it by checking requirements, connections between phases, and complete user flows. It reads existing verification reports and gathers technical debt and deferred gaps to assess whether the original completion criteria were met.
Set up a new project by gathering context, optionally researching the domain, defining requirements, and building a roadmap. It creates planning files that record the project’s background, workflow preferences, phased structure, and ongoing state.
Prepare for a demand letter by gathering the parties, facts, legal basis, deadlines, and desired outcome. Record negotiation options and information to exclude in a structured intake.md file for the separate drafting skill.