Skip to content

Skills

Skills are specialized playbooks stored in the LogMan.io Library under /AI/Skills/. They follow the Agent Skills pattern.

Because skills live in the Library:

  • TeskaLabs distributes them through the Common Library
  • You can customize or author your own with the same Library workflows you already use for detections and parsers
  • The harness discovers them at conversation start without baking procedures into the default prompt

How skills work

  1. At conversation start the agent sees only name + description for each skill
  2. When a task matches, it library_reads /AI/Skills/<name>/SKILL.md — that activates the skill
  3. The skill may declare shares to mount, extra tools to activate, nested references, and scripts under /library/AI/Skills/<name>/

Progressive disclosure keeps context small until a skill is actually needed.

LogMan.io skills

Skill Library path Role
lmio-knowledge /AI/Skills/lmio-knowledge/ Product docs, OpenAPI, Common Library reference (lmio-kb share)
lmio-query /AI/Skills/lmio-query/ Analytical queries against log/event/metric data
lmio-rest-api /AI/Skills/lmio-rest-api/ Authenticated HTTP calls to a LogMan.io instance
lmio-detection-engineer /AI/Skills/lmio-detection-engineer/ Author, unit-test, hunt, and publish correlation rules

Deep dives: Knowledge base (lmio-kb), Query, REST API.

Hint

The skill list is growing quickly, so don't consider this as a final list. It certainly is not.

Other important skills

Skill Role
devops SSH, remote admin, infrastructure troubleshooting
facts Persistent fact store (share facts)
soul-bootstrap Create or update /AI/Soul/SOUL.md
skill-authoring Write new skills into the Library
llm-wiki User-curated research wiki on a share
gitlab GitLab workflows
trace-investigation Investigate harness / LLM traces

Development-oriented skills (dev-lmio-*, SchemaExpert, ShellGuru, …) may also appear depending on which Library layers are enabled.

Authoring your own

  1. Create /AI/Skills/<name>/SKILL.md in the Library with YAML frontmatter (name, description, optional shares, tools, skills)
  2. Add references/ and scripts/ as needed
  3. Prefer citing facts and Library paths over duplicating large procedures into the default prompt

Use the skill-authoring skill for the full writing guide.