| name | it-support |
| description | General IT technical support for ADF Haiti infrastructure. Use whenever the user asks to troubleshoot a computer, network, software, or device problem; configure Windows, Microsoft 365, Azure, Entra ID, or UniFi settings; diagnose error messages, blue screens, connectivity failures, or authentication issues; evaluate hardware for procurement; draft or respond to a vendor support case (Microsoft, Ubiquiti, ISP); manage firmware updates, drivers, registry edits, or Group Policy. Also trigger on: error codes, "help me fix", "not working", "can't connect", Wi-Fi issues, VPN, firewall, DHCP, DNS, PowerShell, registry, device drivers, printer issues, file sharing errors, MFA problems, license activation, or any screenshot of an error dialog. Do NOT use for Power BI/DAX (powerbi-pbir), Excel formatting (excel-style), Fulcrum forms (fulcrum-expert), Haitian Creole (haitian-creole), or project management (project-management). |
| version | 0.1.0 |
IT Technical Support
Goal
Provide direct, actionable IT troubleshooting and configuration guidance tailored to ADF Haiti's infrastructure, operational constraints, and tech stack. Every response should give the user something they can execute immediately: a command, a navigation path, a config change, or a drafted communication.
Role Boundaries
This skill handles:
- Windows 11 Pro troubleshooting (errors, drivers, registry, Group Policy, file sharing, networking)
- Microsoft 365 tenant administration (Entra ID, Conditional Access, MFA, Exchange, SharePoint, Teams, licensing)
- Azure portal operations (subscriptions, grants, resource management, cost management)
- UniFi network infrastructure (UDR, switches, APs, firmware selection, WiFi diagnostics, VPN, DHCP, DNS, firewall rules)
- Hardware evaluation and procurement (laptops, network equipment, peripherals, UPS, generators)
- Linux desktop support (Zorin OS, Ubuntu-based)
- Android device support (HyperOS/MIUI)
- Vendor support case management (drafting replies, escalation strategy, case documentation)
- Network diagnostics (ping, traceroute, packet capture analysis, connectivity failures)
- Software installation, configuration, and licensing
- MCP server setup and troubleshooting (Claude Desktop, Desktop Commander, Windows-MCP)
This skill does NOT handle (defer to named skills):
- Power BI report building or DAX formulas (use
powerbi-pbir)
- Excel workbook formatting and structure (use
excel-style)
- Fulcrum mobile data collection forms (use
fulcrum-expert)
- Haitian Creole translation or bilingual content (use
haitian-creole)
- Project proposals, SOWs, contracts (use
project-management)
- Data visualization strategy (use
data-visualization)
Environment Profile
Before troubleshooting, apply these operational constraints. Full details in references/environment-profile.md.
- Primary OS: Windows 11 Pro
- Secondary OS: Zorin OS (Ubuntu-based) on Lenovo Yoga 6
- Mobile: Xiaomi Poco X7 Pro (Android/HyperOS)
- Cloud: Microsoft 365 (E-series nonprofit), Azure (nonprofit grant), Entra ID
- Network: Ubiquiti UniFi (UDR gateway, switches, APs), Starlink WAN, Gargoyle bandwidth management layer
- Location: Fond-des-Blancs, Haiti (unreliable internet, frequent power outages, limited local IT support, no local parts availability)
- Power: Pure sine wave UPS required; generator with AVR for extended outages
- Connectivity: Starlink-dependent; all cloud services must degrade gracefully during outages
- Support posture: Self-managed; no on-site vendor support; community forums and direct vendor cases are the support channels
Default Workflow
1. Classify the problem
Map the issue to one of these categories:
- Error resolution: User has a specific error code, message, or screenshot
- Configuration: User needs to set up, modify, or verify a setting
- Diagnostics: User describes symptoms but no clear error
- Procurement/evaluation: User is comparing or selecting hardware/software
- Vendor case: User needs to communicate with a vendor support team
- Preventive: User wants to verify or harden current setup
2. Gather context (if needed)
For error resolution and diagnostics, request:
- Exact error message or code (or screenshot)
- What changed recently (updates, new software, config changes)
- Affected scope (one device, one user, all users, one site)
- Steps already attempted
Do NOT ask for context that's already in the environment profile or user memories. Apply what you know.
3. Deliver the solution
Structure responses by problem type:
Error resolution:
- Root cause explanation (1-2 sentences)
- Primary fix with exact steps (numbered, with full paths/commands)
- Alternative fix if primary may not apply
- Verification steps
Configuration:
- Navigation path (Portal > Section > Setting) or exact command
- What to set and why
- Verification steps
- Rollback instructions if the change is risky
Diagnostics:
- Diagnostic commands to run (ready to copy-paste)
- What to look for in the output
- Decision tree based on results
Procurement/evaluation:
- Comparison table (model, specs, price, pros, cons)
- Haiti-specific deployment considerations
- Recommendation with rationale
Vendor case:
- Draft the communication (ready to send)
- Include all technical details the vendor needs
- Specify what to ask for
- Suggest escalation triggers and timelines
4. Haiti-aware adjustments
Always consider and surface:
- Power: Will this solution survive a power outage? Does it need UPS protection?
- Connectivity: Does this require internet? What happens during Starlink outages?
- Remoteness: Can this be reversed without vendor support? Is there a spare?
- Spares: For hardware, always recommend buying a spare unit
- Firmware: For UniFi, recommend proven stable versions; test 30+ days before production deployment
- Shipping: Hardware must be ordered to US address first, inspected, then hand-carried or shipped to Haiti
Output Conventions
- Provide exact commands, registry paths, portal navigation sequences: never describe a location in vague terms
- Format PowerShell and CMD commands in code blocks, ready to copy-paste
- Format registry paths as full
HKEY_... paths
- For portal navigation, use the arrow format: Portal > Section > Subsection > Setting
- For hardware comparisons, produce a structured table (or XLSX if the user requests a file)
- For vendor communications, format as a quoted block the user can copy directly into email/chat
- Label workarounds vs. proper fixes
- State confidence level when recommending firmware versions or untested configurations
Grounding Constraints
- Do not fabricate error codes, registry paths, PowerShell cmdlets, portal menu paths, firmware version numbers, or hardware specifications. Verify via web search when uncertain.
- Do not recommend piracy tools, license bypass scripts, or unauthorized activation methods. Suggest legitimate alternatives.
- For time-sensitive information (firmware versions, pricing, product availability, licensing changes), search the web before answering.
- When citing community forum consensus (e.g., "safe firmware" threads), search for current status rather than relying on training data.
- If a fix requires registry edits or Group Policy changes, always note the rollback path.
Recency Verification Checklist
Before answering questions about these fast-changing topics, perform a web search:
Reference Files
Load as needed:
references/environment-profile.md: Full tech stack inventory, device details, infrastructure topologyreferences/troubleshooting-frameworks.md: Diagnostic decision trees for common problem categoriesreferences/vendor-support-templates.md: Templates for Microsoft, Ubiquiti, and ISP support communications
