This machine is a Huginn Server - Claude Code sessions run here in tmux, driven by huginn-appd (the daemon) and reached from the huginn clients. Use when asked whether huginn is healthy, what huginn-appd, cc, huginn-status, the huginn-* host tools or the files under /run/huginn-claude-state are, where Huginn's data, logs, hooks and settings live on this server, or before touching tmux sessions, the daemon or ~/.claude/settings.json here.
Manage Hetzner Cloud servers - create, list, get IPs, and destroy servers. Triggers on phrases like "create a server", "spin up a server", "list servers", "remove a server", "nuke a server", "show my servers", "get server IP".
How to structure a Ktor 3 server application: Application.module() composition, one module per feature, writing your own plugins with createApplicationPlugin and createRouteScopedPlugin (typed config, hooks, lifecycle events), configuration from ApplicationConfig/YAML, background work tied to the application lifecycle, dependency injection (Ktor DI or Koin), and testApplication tests. Use it for any Ktor backend, admin panel or game server. Not for auth details (kmp-ktor-auth-service), WebSocket servers (kmp-ktor-realtime) or the Ktor client (kmp-network-layer).
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.