fe-account-transition

Generate account transition documents in Markdown from Salesforce, Logfood, Glean, and JIRA data.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/LaurentPRAT-DB/LPT_claude_config --skill fe-account-transition
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fe-account-transition
Source: https://github.com/LaurentPRAT-DB/LPT_claude_config/tree/main/skills/fe-vibe-export/fe-workflows/1.2.0/skills/fe-account-transition
Command: npx skills add https://github.com/LaurentPRAT-DB/LPT_claude_config --skill fe-account-transition

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive account transition documents, ensuring new Account Executives and Solution Architects have all the necessary technical and historical context for a smooth handover.

Core Features & Use Cases

  • Data Aggregation: Gathers critical information from Salesforce, Logfood, Glean, and JIRA.
  • Document Generation: Creates a structured Markdown document detailing account status, use cases, consumption, and escalations.
  • Use Case: When an Account Executive leaves, this skill can automatically compile a detailed handover document for their replacement, including all active and past projects, customer contacts, and technical deep dives.

Quick Start

Use the fe-account-transition skill to generate a transition document for the 'Acme Corp' account.

Frequently Asked Questions about fe-account-transition

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

FAQPage Schema
How do I automate account transition document generation for new Account Executives?

Automating account transition document generation involves integrating Salesforce, Glean, and JIRA data to compile account history, technical use cases, and escalations into a structured Markdown handover file.

What is included in an automated account handover document for Solution Architects?

An automated account handover document includes critical account status details, active technical use cases, consumption data, and engineering escalations aggregated from Salesforce, Logfood, Glean, and JIRA.

Can I pull customer technical use cases and consumption data directly from Salesforce and JIRA?

Yes, you can pull technical use cases and consumption data directly from Salesforce and JIRA, alongside Logfood and Glean, aggregating them into a structured Markdown format for seamless account handovers.

What's the best way to compile engineering escalations and account history for a seamless handover?

The best way to compile engineering escalations and account history is using an automated script that queries JIRA and Glean, outputting a structured Markdown document for new Account Executives.

Do I need access to Logfood and Databricks to generate account transition documents?

You need access to Logfood and Databricks to gather comprehensive consumption data and technical context, ensuring the generated account transition Markdown document contains all necessary handover details.