asq-intake

Extract Salesforce ApprovalRequest records and create a structured Google Drive workspace.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/shdzhang/emea-sts-productivity-hackathon --skill asq-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asq-intake
Source: https://github.com/shdzhang/emea-sts-productivity-hackathon/tree/main/fe-sts/skills/asq-intake
Command: npx skills add https://github.com/shdzhang/emea-sts-productivity-hackathon --skill asq-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many ASQ engagements lack a consistent intake process, scattered context, and a shared workspace, which slows scoping and delivery. This Skill centralizes ASQ metadata, account details, classification, and initial scoping notes into a consistent Google Drive workspace to accelerate handoffs and downstream collaboration.

Core Features & Use Cases

  • Extract ASQ and account records from Salesforce, including ASQ metadata, request description, and account owner information for accurate triage.
  • Classify engagement (pillar, service, format, estimated complexity) and surface flags for vague requests that require scoping.
  • Create a standardized Google Drive engagement folder with subfolders and populate CONTEXT and STATUS Google Docs containing CAST, account team, consumption summary, and Drive references.
  • Use case: an STS engineer runs intake for AR-123456 to produce a ready-to-use engagement workspace and a clear scoping summary for the delivery team.

Quick Start

Run the asq-intake skill with an ASQ number, review the extracted data, and approve creation to generate the Google Drive engagement workspace with CONTEXT and STATUS documents.

Frequently Asked Questions about asq-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate ASQ onboarding from Salesforce to Google Drive?

Automating ASQ onboarding from Salesforce to Google Drive involves extracting ApprovalRequest records and account details, then generating a structured Drive workspace with CONTEXT and STATUS documents after explicit user approval.

How does engagement intake classification work for new ASQ records?

Engagement intake classification for new ASQ records works by extracting Salesforce metadata to classify the engagement by pillar, service, format, and estimated complexity, while surfacing flags for vague requests that require scoping.

Can I generate Google Drive engagement folders from Salesforce customer data?

Yes, you can generate Google Drive engagement folders from Salesforce customer data by running intake with an ASQ number and approving the workspace creation, which produces standardized subfolders and CONTEXT and STATUS Google Docs.

What do I need to create standardized scoping documents for ASQ engagements?

To create standardized scoping documents for ASQ engagements, you need Salesforce read access and Google Drive and Docs creation permissions via MCP tools to extract CAST elements, account team details, and consumption summaries.

What is the best way to structure Google Drive workspaces for sales scoping?

The best way to structure Google Drive workspaces for sales scoping is to create a standardized engagement folder with subfolders populated with CONTEXT and STATUS Google Docs that record Drive references and ASQ metadata.

Why does ASQ intake require explicit user approval before creating Google Docs?

ASQ intake requires explicit user approval before creating Google Docs to ensure the extracted Salesforce data, including account owner information and consumption summaries, is reviewed before generating the Google Drive engagement workspace.