ai-playbook 1.0.0

package/skills/support-engineering/README.md

@@ -0,0 +1,107 @@
+# Support Engineering
+
+## Overview
+
+The **Support Engineering** skill enables AI models to troubleshoot, diagnose, and resolve technical issues while acting as the voice of the customer, providing excellent technical support, and driving continuous product improvement through customer feedback.
+
+This skill combines deep technical knowledge with excellent communication and problem-solving abilities.
+
+---
+
+# Goals
+
+* Resolve customer issues quickly
+* Reduce time-to-resolution
+* Improve customer satisfaction
+* Identify product improvements
+* Document solutions
+* Build customer relationships
+* Share product feedback
+* Drive quality improvements
+
+---
+
+# Capabilities
+
+## Troubleshooting
+* Root cause analysis
+* Systematic debugging
+* Log analysis
+* Network troubleshooting
+
+## Communication
+* Clear technical explanation
+* Empathetic customer interaction
+* Written and verbal communication
+* Documentation
+
+## Product Knowledge
+* Deep system understanding
+* Feature expertise
+* Configuration knowledge
+* Integration expertise
+
+## Technical Skills
+* System administration
+* Database operations
+* Network management
+* Cloud platforms
+
+---
+
+# When to Use
+
+* Troubleshooting customer issues
+* Providing technical guidance
+* Documenting solutions
+* Escalating complex issues
+* Gathering feature feedback
+* Creating knowledge articles
+* Training customers
+
+---
+
+# Expected Workflow
+
+```
+Understand Issue
+        ↓
+Gather Information
+        ↓
+Diagnose Problem
+        ↓
+Implement Solution
+        ↓
+Verify Resolution
+        ↓
+Document & Share
+```
+
+---
+
+# Best Practices
+
+Always:
+* Listen to customer needs
+* Communicate clearly
+* Document solutions
+* Follow up thoroughly
+* Escalate appropriately
+* Share feedback
+* Maintain professionalism
+* Respond promptly
+
+Never:
+* Make assumptions
+* Skip troubleshooting steps
+* Blame the customer
+* Forget to document
+* Overpromise solutions
+* Ignore follow-up
+* Skip escalation
+
+---
+
+# Success Criteria
+
+Successful support engineering resolves issues quickly, maintains high satisfaction, documents solutions, and drives product improvements.

package/skills/support-engineering/examples.md

@@ -0,0 +1,85 @@
+# Support Engineering Skill - Examples
+
+This document contains practical examples demonstrating when and how to use the Support Engineering Skill.
+
+---
+
+# Example 1 - Troubleshooting Customer Issue
+
+## User Request
+Customer reports the API is returning 500 errors intermittently.
+
+## Expected Behavior
+* Gather logs and stack traces
+* Reproduce issue if possible
+* Identify root cause
+* Implement workaround if needed
+* Implement fix
+* Verify resolution
+* Document solution
+
+---
+
+# Example 2 - Root Cause Analysis
+
+## User Request
+Analyze why this customer experienced a 2-hour outage.
+
+## Expected Behavior
+* Review incident logs
+* Identify triggering event
+* Analyze system behavior
+* Identify prevention opportunities
+* Document timeline
+* Create action items
+
+---
+
+# Example 3 - Knowledge Base Article
+
+## User Request
+Create an article for the most common support question.
+
+## Expected Behavior
+* Identify common issue
+* Write clear explanation
+* Provide step-by-step solution
+* Include screenshots
+* Add troubleshooting section
+* Enable feedback mechanism
+
+---
+
+# Example 4 - Performance Investigation
+
+## User Request
+Customer reports slow response times. Investigate.
+
+## Expected Behavior
+* Analyze metrics
+* Review logs
+* Check resource usage
+* Identify bottleneck
+* Recommend optimization
+* Monitor improvement
+
+---
+
+# Example 5 - Feature Request Analysis
+
+## User Request
+Customers keep requesting this feature. Analyze the requests.
+
+## Expected Behavior
+* Categorize requests
+* Identify patterns
+* Assess impact
+* Estimate effort
+* Write feature proposal
+* Present to product team
+
+---
+
+# Success Criteria
+
+Successful support engineering resolves issues quickly, maintains high satisfaction, documents solutions, and drives product improvements.

package/skills/support-engineering/skill.md

@@ -0,0 +1,103 @@
+# Support Engineer – Core Skill Set
+
+A Support Engineer (also called Technical Support Engineer, Solutions Engineer, or Site Reliability Engineer – depending on the organization) is responsible for troubleshooting, diagnosing, and resolving technical issues for customers while acting as the voice of the customer inside the product organization.  
+The skills listed below are grouped by **technical expertise**, **soft skills**, **tools & processes**, and **career development**. Use this document as a reference for hiring, self‑assessment, or creating a personal development plan.
+
+---
+
+## Table of Contents
+1. [Technical Foundations](#technical-foundations)  
+2. [Customer‑Facing Abilities](#customer-facing-abilities)  
+3. [Process & Tooling](#process--tooling)  
+4. [Certifications & Learning Resources](#certifications--learning-resources)  
+5. [Success Metrics](#success-metrics)  
+6. [Glossary](#glossary)
+
+---
+
+## Technical Foundations
+| Skill | Proficiency | Typical Tools / Technologies |
+|-------|-------------|------------------------------|
+| **Operating Systems** | Advanced | Windows Server, RHEL / Ubuntu / SUSE Linux, macOS |
+| **Networking** | Advanced | TCP/IP, DNS, DHCP, VPN, VLANs, firewalls, load balancers |
+| **Scripting & Automation** | Advanced | Bash, PowerShell, Python, Perl, Ansible, Puppet, Chef |
+| **Cloud Platforms** | Intermediate | AWS (EC2, S3, RDS, CloudWatch), Azure (VMs, Functions), GCP (Compute Engine) |
+| **Web Services & APIs** | Intermediate | REST, SOAP, GraphQL, JSON, XML, OAuth, authentication mechanisms |
+| **Databases** | Intermediate‑Advanced | MySQL, PostgreSQL, SQL Server, Oracle, MongoDB |
+| **Virtualization & Containerization** | Intermediate | VMware, Hyper‑V, KVM, Docker, Kubernetes |
+| **Performance Monitoring** | Intermediate | Prometheus, Grafana, Nagios, Zabbix, ELK stack |
+| **Security Basics** | Intermediate | Patch management, vulnerability scanning, TLS/SSL, IAM |
+| **Version Control** | Advanced | Git (branching, rebasing, PR workflow) |
+| **Ticketing & ITSM** | Advanced | JIRA, ServiceNow, Zendesk, Microsoft Dynamics |
+| **Remote Access** | Advanced | SSH, RDP, TeamViewer, LogMeIn |
+| **Product Knowledge** | Expert | Deep familiarity with the specific SaaS/On‑Prem product(s) you support |
+
+---
+
+## Customer‑Facing Abilities
+- **Empathy & Active Listening** – Understand customer pain points and convey genuine concern.  
+- **Clear Communication** – Translate technical jargon into plain language; tailor explanations to non‑technical stakeholders.  
+- **Problem‑Solving Mindset** – Apply a systematic, root‑cause‑first approach.  
+- **Negotiation & Escalation Management** – Set realistic expectations and manage escalation paths.  
+- **Documentation Skills** – Write concise, reusable knowledge‑base articles, SOPs, and post‑mortems.  
+
+---
+
+## Process & Tooling
+- **Ticket Management** – Create, categorize, prioritize, and close tickets while ensuring SLA compliance.  
+- **Incident Triage** – Quickly assess severity, isolate affected components, and assign priority.  
+- **Root‑Cause Analysis (RCCA)** – Use structured methods (5‑Whys, Fishbone diagram) to uncover underlying issues.  
+- **Work‑Arounds & Fixes** – Implement temporary solutions or permanent patches; document steps for repeatability.  
+- **Monitoring & Observability** – Leverage dashboards (Grafana, Datadog, Splunk) to proactively detect anomalies.  
+- **Collaboration Channels** – Use Slack/Teams, Confluence, and internal wikis for knowledge sharing and escalation coordination.  
+- **Post‑Mortem Participation** – Contribute to incident reviews to improve processes and prevent recurrence.  
+
+---
+
+## Certifications & Learning Resources
+| Focus Area | Recommended Certifications |
+|------------|-----------------------------|
+| **Operating Systems** | Microsoft Certified: Windows Server; Linux Foundation – LPIC‑1/2 |
+| **Networking** | Cisco CCNA; CompTIA Network+ |
+| **Cloud** | AWS Certified Solutions Architect – Associate; Azure Administrator Associate |
+| **Databases** | Oracle OCA; AWS Certified Database – Specialty |
+| **Security** | CompTIA Security+; CISSP (for deeper focus) |
+| **Service Management** | ITIL Foundation; ITIL Intermediate – Service Transition |
+| **Project Management** (optional) | PMP; Scrum Master |
+
+**Learning Channels**  
+- Official product documentation & release notes  
+- Vendor training portals (e.g., A Cloud Guru, Pluralsight)  
+- Community forums – Stack Overflow, Reddit, vendor‑specific boards  
+- Blogs, webinars, and user‑group meet‑ups  
+- Sandbox / lab environments for hands‑on practice  
+
+---
+
+## Success Metrics
+- **SLA Compliance** – ≥ 95 % of incidents resolved within agreed timeframes.  
+- **First‑Contact Resolution (FCR)** – ≥ 70 % of tickets resolved on the first interaction.  
+- **Customer Satisfaction (CSAT)** – Average score ≥ 4.5 / 5.  
+- **Mean Time to Resolve (MTTR)** – Continuous reduction; benchmark against team baseline.  
+- **Knowledge‑Base Coverage** – Minimum of 5 new KB articles per month; each article ≥ 100 views.  
+- **Escalation Rate** – ≤ 10 % of tickets escalated to development.  
+
+---
+
+## Glossary
+- **SLA** – Service Level Agreement; formal contract defining response/resolution times.  
+- **FCR** – First‑Contact Resolution; metric of issues solved without further escalation.  
+- **MTTR** – Mean Time to Resolve; average duration from issue creation to closure.  
+- **RCA** – Root‑Cause Analysis; systematic process to identify the fundamental cause of an incident.  
+- **KB** – Knowledge Base; repository of documented solutions, guides, and FAQs.  
+
+---
+
+*End of Document*  
+
+--- 
+
+*Prepared for internal use – Support Engineering Team*  
+
+--- 
+