Method 1: Write instructions manually
Go to Skills in the sidebar and click Add Skill, then select Write skill instructions. Fill in the following fields:The description field
The description is critical. The AI reads it on every message to decide whether this Skill is relevant. A vague description causes the Skill to activate at the wrong time, or not at all.
Write the description as if explaining to a colleague when they should reach for this Skill. Include concrete trigger phrases.
Method 2: Create with chat
Go to Skills, click Add Skill, then select Create with chat. Describe what you want in plain language and Langdock generates the name, description, and instructions for you. This is the fastest starting point if you are not sure how to phrase the instructions. Chat shows Save this skill? with the name, handle, description, instructions, and any integrations and files the Skill will include. Nothing is saved until you click Save skill. Cancel saves nothing. If the handle already belongs to a Skill you can edit, the card is Update this skill? and warns that saving replaces it for everyone who uses it. The button says Update skill. Saving a Skill from chat works in the web app and the desktop app, where you can confirm the card. Files in the conversation can become supporting files. Ask Langdock to include attachments you uploaded or files it generated in the chat. Nothing is copied until you confirm. Each request copies up to 20 files, with a 5 MB limit per file.Method 3: Upload a Markdown file or ZIP bundle
Upload a Markdown file to create a Skill without supporting files. For Skills that include supporting files, upload a.zip archive with a SKILL.md file.
Go to Skills, click Add Skill, then select Upload a skill and drag in your file.
Markdown file format
The Markdown file must contain a YAML frontmatter block at the top:
The instructions body (the content after the frontmatter block) is required.
ZIP bundle
A ZIP archive can contain aSKILL.md file plus supporting files such as scripts, references, or assets.
Structure: The SKILL.md must be at the root of the archive or inside a single top-level directory.
Allowed file types: .md, .mdx, .txt, .py, .sh, .js, .ts, .json, .yaml, .yml, .toml, .csv, .sql, .xml, .xsd, .html, .css, .svg, .pdf, .docx, .xlsx, .pptx, .png, .jpg, .jpeg, .gif, .webp
Size limits:
Edit an existing Skill
Go to Skills and select a Skill to open its detail view. If you can edit the Skill, you can update:- Name and icon in the header.
- Category from More options in the header.
- Description and instructions by opening
SKILL.mdand clicking Edit skill. - Supporting files by adding new files and folders or uploading files. You can edit, rename, move, or delete existing supporting files.
- Integrations by clicking Edit integrations.
SKILL.md remains the main instructions and metadata file and cannot be renamed, moved, or deleted. Other Markdown files can use different names.
You can also update a Skill from chat. Ask Langdock to change a Skill you can edit. Chat shows Update this skill? and writes nothing until you click Update skill. Cancel saves nothing. The card also warns that saving replaces the Skill for everyone who uses it. If you can only view a shared Skill, chat leaves that Skill unchanged and creates a personal copy.
You can also add supporting files from chat. Ask Langdock to copy conversation attachments into a Skill you created. Chat shows Add files to this skill? and adds nothing until you click Add files. Cancel adds nothing. A file copied to an existing path replaces the previous version.
Writing good instructions
The quality of a Skill depends almost entirely on the quality of its instructions.- Be specific about the output. Do not say “summarize things.” Say “write a three-section summary with: (1) key decisions made, (2) open questions, (3) next steps. Each section should be 3 to 5 bullet points.”
- Write the description as if explaining to a new colleague. Vague descriptions cause the AI to activate the Skill at the wrong time, or not at all.
- Test before sharing. Install the Skill, start a new chat, and see if the AI behaves as expected. Adjust based on what you observe.
- Keep instructions focused. A Skill that does one thing well is more reliable than one that tries to cover many cases.
- Include concrete trigger phrases in the description. Examples: “when asked for updates,” “when drafting a reply to a customer,” “when summarizing a meeting.”
Limitations
What Skills cannot do:
- Skills do not have memory across sessions. Instructions are re-read fresh at the start of each conversation. For persistent memory, use Chat Memory.
- Skills cannot access live data on their own. Unless linked to an integration, a Skill only provides instructions and does not fetch real-time information.
- No version history. When you update a Skill’s instructions, the previous version is not saved.
FAQ
When should I create a Skill?
When should I create a Skill?
Create a Skill when you have reusable instructions that should guide future chats. Skills are best for repeatable work patterns, writing rules, domain context, or internal processes that are too small to require a full agent.
What should I check if a new Skill does not work well?
What should I check if a new Skill does not work well?
Check whether the instructions are specific, scoped, and testable. Avoid mixing too many unrelated goals in one skill, and test it with realistic prompts before sharing it widely.