Skip to content

AI content in the Library

The Library is the central content store of TeskaLabs LogMan.io. Parsers, correlation rules, dashboards, site descriptors — and AI content — all live there.

Users who already work with the Library for SIEM content use the same product feature for AI:

  • Browse and search under /AI/
  • Edit items to customize behaviour
  • Author new skills and prompts
  • Rely on layered delivery from the TeskaLabs Common Library

See also the user guide: Library.

Why AI content is in the Library

Putting prompts, skills, and Soul in the Library means:

  • One place for product content — operators already know how to navigate, copy, and edit Library items
  • Customization — override a shipped skill or prompt on a tenant or personal layer without forking the harness
  • Distribution — TeskaLabs ships and updates AI content through the Common Library, the same channel as detections and parsers
  • Auditability — changes to agent behaviour are Library changes, reviewable like any other declaration

In the sandbox the Library is also mounted read-only at /library, so scripts under a skill can run as python3 /library/AI/Skills/… without copying files into the workspace.

Layout under /AI/

Path Role
/AI/Prompts/ System prompts (default agent behaviour, summarize, goal, final-answer judge, …)
/AI/Skills/ Agent skills (SKILL.md playbooks, references, scripts)
/AI/Soul/SOUL.md Personality and relationship preferences for the agent
/AI/Agents/ Agent-specific prompt material where used
/AI/Models/ Optional model-related Library content

How knowledge is organized

The default system prompt (Library path /AI/Prompts/default.md) teaches a strict routing for durable knowledge. All of these destinations are Library-backed or Library-activated skills:

Kind of knowledge Destination Where it lives
Personality, tone, language, timezone Soul Library /AI/Soul/SOUL.md (skill soul-bootstrap)
Facts, conventions, lessons from mistakes Facts store Share /workspace/facts after activating the facts skill
Repeatable procedures Skills Library /AI/Skills/<name>/SKILL.md (author with skill-authoring)

That separation keeps the harness predictable: personality does not pollute operational memory, and playbooks stay versionable Library content.

Customization

You can:

  • Edit shipped prompts or skills in the Library (respecting layering rules)
  • Add a new skill under /AI/Skills/<your-skill>/ with a SKILL.md frontmatter
  • Bootstrap or update Soul through the UI / soul-bootstrap skill
  • Keep tenant-specific procedures in your own skills instead of stuffing them into the default prompt

Warning

Changing Library items changes product behaviour — including how the AI agent acts. Prefer small, reviewable edits; use skills for procedures and facts for durable truths.