asq-close

Automate ASQ ticket closure with consumption analysis and structured close notes.

Updated Apr 8, 2026

Search Tags:#automation #impact #closure #consumption #sts #asq #genie-rooms

Ready to run

npx skills add https://github.com/shdzhang/emea-sts-productivity-hackathon --skill asq-close

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: asq-close
Source: https://github.com/shdzhang/emea-sts-productivity-hackathon/tree/main/fe-sts/skills/asq-close
Command: npx skills add https://github.com/shdzhang/emea-sts-productivity-hackathon --skill asq-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close ASQ tickets efficiently by automating consumption and impact analyses and standardizing close notes against STS expectations.

Core Features & Use Cases

Payload preparation: Assemble required fields for SFDC closes.
Context gathering: Aggregate customer, engagement, and consumption data.
Close-note drafting & Slack update: Generate structured notes and messages aligned to STS deliverables.
Lifecycle integration: Coordinate with Genie Rooms and STS service expectations to validate closure readiness.

Quick Start

Trigger the ASQ close workflow by providing the ASQ id or alias to the close tool and letting it orchestrate payload creation, context gathering, analysis, and note generation.

Frequently Asked Questions about asq-close

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

FAQPage Schema

How do I automate ASQ ticket closure with consumption and impact analysis?▼

Automating ASQ ticket closure involves orchestrating payload preparation, context gathering, and consumption analysis to generate structured close notes. This workflow validates closure readiness against STS expectations and coordinates updates across SFDC, Slack, and knowledge bases.

What is the best way to generate structured close notes for ASQ engagements?▼

Generating structured close notes for ASQ engagements requires aggregating customer and consumption data to draft standardized messages. This approach aligns finalization outputs directly with STS service deliverables and updates Slack messaging.

Does the ASQ close automation workflow integrate with Genie Rooms and SFDC?▼

Yes, ASQ close automation integrates with Genie Rooms to validate lifecycle readiness and updates SFDC records with prepared payloads. It also coordinates with Slack to deliver final closure messages.

How do I prepare SFDC payloads for ASQ engagement finalization?▼

Preparing SFDC payloads for ASQ finalization involves assembling required fields from gathered context and consumption analysis. The automation workflow extracts this data to ensure closures satisfy STS functional requirements.

Can I validate ASQ closure readiness against STS expectations automatically?▼

Validating ASQ closure readiness against STS expectations is automated by coordinating with Genie Rooms throughout the engagement lifecycle. This ensures all consumption analysis and close-note drafts meet service deliverables before finalization.

What limitations exist when automating end-to-end ASQ ticket closures?▼

Automating end-to-end ASQ ticket closures requires providing a valid ASQ id or alias to initiate the workflow. The process depends on accurate context gathering from integrated systems to properly execute consumption and impact analysis.