Skill Importing — Bring Claude-Style Skills into Hatz
J
Jordan Takrouri
Platforms like Claude have popularized "skills" — structured, multi-file AI instruction packages that go well beyond a basic system prompt. A skill bundles a core instruction file, reference documents the model loads on demand, supporting assets, and a trigger description that controls when it activates. Users are building skills for everything from technical playbooks to domain-specific mentors to operational runbooks, and this pattern is becoming the standard way power users encode reusable expertise into AI.
Currently, there's no way to import these into Hatz. Users who've built skill libraries on other platforms have to manually recreate them as separate Apps or Agents, losing the multi-file structure and progressive context loading in the process. For MSPs onboarding teams onto Hatz, this creates unnecessary migration friction and duplicated effort.
The core ask is a skill import pipeline that accepts a standard skill package (ZIP with a SKILL.md at root + optional reference files and assets) and converts it into Hatz-native Workshop items — mapping instructions to Agent system prompts, reference files to knowledge sources, and descriptions to Workshop metadata. Unsupported components would be flagged during import so the user knows what needs attention.
The bigger unlock is skill routing in Chat. Once skills exist as first-class objects, Hatz could evaluate a user's message against available skill descriptions and automatically load the right expertise context — no manual app or agent selection required. This would transform Chat from a general-purpose LLM interface into a context-aware assistant that knows which domain knowledge to pull in based on the question.
Long-term, this naturally extends into multi-tenant skill distribution and a community marketplace — the same management model Hatz already does well with Apps and Agents, applied to portable, versioned expertise packages that MSPs can build once and deploy across all their tenants.
C
Connor Smith
We badly want Claude-style Skills as well. We find creating agents that have fully informed responses requires much more than the existing custom connections or instructions will accomodate. We can expose something like a skill through tool calls on a custom MCP, but the engineering that will require seems redundant compared to just having something like support for Skills integrated into Hatz Agents.
A
Andrew
Yes please. This is a big limitation from my point of view. Yes, you can create an agent, but that's hard coded to do one thing. Skills allow you to use and re-use instructions wherever you are working. Being able to leverage 1 or more skills anywhere in Hatz would be a game changer.
D
Dan Davis
One could argue that this is what Agents in Hatz are for (in response to Bridget's comment), but the complexity required is beyond Agents, as Jordan detailed. Agree there needs to be skills.
B
Bridget Driscoll
Building a complex "skill package" (like a Tier 1 Helpdesk runbook or an HR onboarding mentor) takes significant prompt engineering and curation. Allowing MSPs to build that once, package it as a versioned asset, and push it across their tenant base is exactly how AI scales in the channel. I would think this request is similar to the preferences and memory integrations that were recently added to the platform.