Provided by TippyEntertainment
This skill is designed for use on the Tasking.tech agent platform (https://tasking.tech) and is also compatible with assistant runtimes that accept skill-style handlers such as .claude, .openai, and .mistral. Use this skill for both Claude code and Tasking.tech agent source.
Omnissa — Horizon Desktops
This skill covers practical workflows for designing, deploying, and operating VMware Horizon desktop environments (Connection Server, Composer/Instant Clone, vCenter, ESXi/vSphere, and cloud variants). Focus areas include image & template strategy, provisioning, identity integration, security, monitoring, and automation.
Files & Formats
Required files and typical formats for Horizon projects:
SKILL.md — skill metadata (YAML frontmatter: name, description)README.md — short overview and runbooks (optional)- Image & templates:
.ova, .ovf, .vmdk, AMI/VM templates lists (.txt/.json)
- Automation:
.ps1 (PowerCLI/PowerShell), .sh, .py (pyvmomi), Terraform (.tf), Ansible (.yml)
- vSphere exports/configs:
.json, .yaml, .xml
- IaC & CI:
azure-pipelines.yml, .github/workflows/*.yml
- Docs & runbooks:
.md (runbooks, troubleshooting guides)
- Monitoring & dashboards:
.json (vRealize/Log Insight dashboards), saved queries (.txt)
- Policy & security:
.json (NSX/Firewall rules), RBAC lists (.csv)
Core Responsibilities
Validate environment & prerequisites
- Identify vCenter/vSphere versions, Connection Server topology, Composer/Instant Clone usage, and AD integration method.
Image & bundle strategy
- Design golden images, snapshot policies, patch/update workflows, and template management (Instant Clone vs full clone tradeoffs).
Provisioning & lifecycle management
- Automate provisioning (PowerCLI, Terraform, Ansible) and manage lifecycle: create, rebuild, recompose, retire.
Directory, identity & profiles
- Ensure domain join, AD permissions for computer objects, GPO strategy, profile management (UE/VMT, FSLogix if used) and SSO integration.
Networking & security
- Design secure network segments, consider NSX micro-segmentation, load balancing for Connection Servers, and encryption in transit/at rest.
Monitoring & troubleshooting
- Use vRealize, Horizon dashboards, and logging to monitor session health, connection failures, and resource usage; use SVM/SSO logs for troubleshooting.
Scaling, cost & DR
- Recommend pooled vs dedicated, schedule-based power management, and disaster recovery/backup approaches.
Output style
- Provide concise runbooks and minimal copyable PowerCLI/CLI/Ansible/Terraform examples.
- Reference precise file paths and configuration snippets when suggesting edits.
- Prefer pragmatic automation and clear rollback instructions.
1---2name: omnissa-horizon-desktops3description: Manage, deploy, secure, and operate VMware Horizon desktop fleets (on‑premises or cloud-hosted) with domain-join, image pipelines, automation, and monitoring.4---5# Provided by TippyEntertainment6# https://github.com/tippyentertainment/skills.git789This skill is designed for use on the Tasking.tech agent platform (https://tasking.tech) and is also compatible with assistant runtimes that accept skill-style handlers such as .claude, .openai, and .mistral. Use this skill for both Claude code and Tasking.tech agent source.10111213# Omnissa — Horizon Desktops1415This skill covers practical workflows for designing, deploying, and operating VMware Horizon desktop environments (Connection Server, Composer/Instant Clone, vCenter, ESXi/vSphere, and cloud variants). Focus areas include image & template strategy, provisioning, identity integration, security, monitoring, and automation.1617## Files & Formats1819Required files and typical formats for Horizon projects:2021- `SKILL.md` — skill metadata (YAML frontmatter: `name`, `description`)22- `README.md` — short overview and runbooks (optional)23- Image & templates: `.ova`, `.ovf`, `.vmdk`, AMI/VM templates lists (`.txt`/`.json`)24- Automation: `.ps1` (PowerCLI/PowerShell), `.sh`, `.py` (pyvmomi), Terraform (`.tf`), Ansible (`.yml`)25- vSphere exports/configs: `.json`, `.yaml`, `.xml`26- IaC & CI: `azure-pipelines.yml`, `.github/workflows/*.yml`27- Docs & runbooks: `.md` (runbooks, troubleshooting guides)28- Monitoring & dashboards: `.json` (vRealize/Log Insight dashboards), saved queries (`.txt`)29- Policy & security: `.json` (NSX/Firewall rules), RBAC lists (`.csv`)3031## Core Responsibilities32331. **Validate environment & prerequisites**34 - Identify vCenter/vSphere versions, Connection Server topology, Composer/Instant Clone usage, and AD integration method.35362. **Image & bundle strategy**37 - Design golden images, snapshot policies, patch/update workflows, and template management (Instant Clone vs full clone tradeoffs).38393. **Provisioning & lifecycle management**40 - Automate provisioning (PowerCLI, Terraform, Ansible) and manage lifecycle: create, rebuild, recompose, retire.41424. **Directory, identity & profiles**43 - Ensure domain join, AD permissions for computer objects, GPO strategy, profile management (UE/VMT, FSLogix if used) and SSO integration.44455. **Networking & security**46 - Design secure network segments, consider NSX micro-segmentation, load balancing for Connection Servers, and encryption in transit/at rest.47486. **Monitoring & troubleshooting**49 - Use vRealize, Horizon dashboards, and logging to monitor session health, connection failures, and resource usage; use SVM/SSO logs for troubleshooting.50517. **Scaling, cost & DR**52 - Recommend pooled vs dedicated, schedule-based power management, and disaster recovery/backup approaches.5354## Output style5556- Provide concise runbooks and minimal copyable PowerCLI/CLI/Ansible/Terraform examples.57- Reference precise file paths and configuration snippets when suggesting edits.58- Prefer pragmatic automation and clear rollback instructions.
tippyentertainment