> ## Documentation Index
> Fetch the complete documentation index at: https://docs.langdock.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Webinar & FAQ

> Answers to common questions about Skills in Langdock.

<iframe width="100%" height="420" src="https://www.youtube.com/embed/hZv5ECDFVkU" title="Skills Webinar" frameBorder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowFullScreen />

<AccordionGroup>
  <Accordion title="What is the main difference between an agent and a skill?">
    Agents are a dedicated environment for getting a specific set of tasks done. Skills are reusable instructions that load automatically when you need them. Skills extend what agents can do: if you move generic rules like tone of voice, output formats, and brand guidelines into skills, agents become leaner and focus only on what makes them specific. In some cases, a skill can replace an agent entirely. If your team opens an agent just to get properly formatted output, that should be a skill instead. Rule of thumb: if users have to consciously "go somewhere" for something that should always just work, it belongs in a skill.
  </Accordion>

  <Accordion title="What is the main difference between Project Instructions and a Skill? Do skills apply to all work and project instructions only to the project?">
    Project instructions apply only to project chats. Skills apply to normal chats and are not limited to a single project.
  </Accordion>

  <Accordion title="Do I have to tell Langdock which skill to use, or does it pick automatically? Is explicit skill steering possible?">
    Skills can trigger automatically via semantic matching (not keywords). You can also manually steer by tagging a skill via the @ menu.
  </Accordion>

  <Accordion title="Does the LLM decide to pull a skill based on keywords? Does skill naming impact triggering?">
    No. Triggering is semantic and driven primarily by the skill description, not keyword matching or the skill name. Names help humans manage skills.
  </Accordion>

  <Accordion title="Can skills be added to agents? Will agents be able to use skills I created?">
    Yes. Attach skills to agents in the agent configuration under Actions.
  </Accordion>

  <Accordion title="What is the benefit of adding a skill directly into a project if skills work in every chat anyway?">
    Skills active in normal chats are not automatically applied in project chats or agent chats, so explicitly adding them there matters.
  </Accordion>

  <Accordion title="Can specific selected skills be used per chat, or only globally / via agents and projects?">
    Globally active skills auto-apply to all chats. You can disable individual skills for a session via the skills indicator, and you can scope skills by attaching them to agents or projects.
  </Accordion>

  <Accordion title="If Custom Instructions, Skills, and an Agent contradict each other, how is that handled?">
    No formal rulebook, but typical priority is: agent prompt first, then skills, then custom instructions. The model generally follows the most specific instruction.
  </Accordion>

  <Accordion title="Is there an upper limit on how many skills can or should be installed/active? What happens if too many are active?">
    Yes. Max 20 active skills per user; admins can force-apply up to 8 workspace-wide skills. Too many active skills can cause wrong-skill selection or unpredictable behavior; the limit mitigates this.
  </Accordion>

  <Accordion title="Who can share or create skills — everybody or only admins?">
    Admins can decide in the role settings which roles can share and create skills. Only admins can share workspace-wide or force-apply skills to everyone. For individual skills, both the skill Owner and any user with Editor access can share the skill with other users and groups.
  </Accordion>

  <Accordion title="How can you upload assets or resource files (e.g. templates, Python scripts) to a skill?">
    Upload either a plain Markdown file or a `.zip` Skill bundle with supporting files such as templates, reference documents, or scripts. You can also open an existing or imported Skill to add, upload, edit, rename, move, or delete supporting files. The ZIP limit is 25 MB and the uncompressed limit is 20 MB. Scripts are reference only and are not executed automatically. Disallowed file types are skipped.
  </Accordion>

  <Accordion title="Must the file name always be SKILL.md, or can it be anything?">
    Inside a ZIP archive, the main instructions and metadata file must be named `SKILL.md`. For a plain file upload, you can use any `.md` file name. You can also create and manage other Markdown files with different names in the Skill detail view.
  </Accordion>

  <Accordion title="Can I import skills 1:1 from Claude / Claude Code skills?">
    Yes, if they're in SKILL.md format or packaged as a .zip.
  </Accordion>

  <Accordion title="Are skills limited to certain models (Claude vs GPT), or are they model-agnostic?">
    Skills are model-agnostic.
  </Accordion>

  <Accordion title="Is there a skill builder in Langdock?">
    Yes. There is a "Skill Creator" skill that helps generate skills in Langdock.
  </Accordion>

  <Accordion title="How can I best use skills as a consultant with different clients (different PPT masters, brand guidelines, etc.)?">
    Create one skill per customer, or build one skill that contains rules for selecting the right guideline set per customer.
  </Accordion>

  <Accordion title="Can admins deactivate system skills like Skill Builder?">
    System skills can not be deactivated.
  </Accordion>
</AccordionGroup>