Skip to main content
Some of your best AI work isn’t a result. It’s a method: how you review a release, write a client brief, or check a contract before signing. A Skill keeps that method in Ligura so any of your connected AI apps can follow the same steps next time. Skills work with the AI apps you already use. Save one from Claude, use it from ChatGPT, or the other way around. Any AI app connected to Ligura through MCP can find and read your Skills.

​
How a Skill differs from other saved work

A Skill follows the open Agent Skills format: a SKILL.md file with a name, a short description, and step-by-step instructions, plus optional supporting text files such as checklists, templates, or reference notes. If you already use skills in an AI app that supports them, the format will look familiar.

​
Save a Skill

When an AI session works out a procedure worth repeating, ask the AI to save it:
Save the steps we just followed as a Ligura skill in the Elephas Teams Launch Work.
You can also ask for a Skill directly:
Create a Ligura skill for reviewing a release. Include our checklist as a separate file.
Skills are saved by your connected AI apps, in the same way as other saved work. The Ligura website doesn’t have a separate create or import button. Ask the AI to confirm the Skill’s name and where it was saved.

​
Review it, then mark it Current

A new Skill arrives as a Draft. Open it in Ligura from the Work’s Skills category to check it:
  • Instructions shows the steps as formatted text.
  • Files lists the supporting files. Select one to read it.
  • Source shows the exact SKILL.md.
When the Skill is ready for reuse, choose Mark Current. Current means you recommend this version for reuse. It does not mean Ligura has tested or approved the instructions, so read them before you mark them Current. You can also ask an AI app to mark it Current once you have reviewed it.

​
Use a Skill from any connected AI app

In a later session, in the same app or a different one, ask for the Skill by name:
Use our Ligura release review skill for this.
The AI looks through your Current Skills, reads the one that fits, and loads only the supporting files the task needs. If two Skills could match, it should ask which one you mean. You can also start from Ligura. Open the Skill, choose Use with AI, then Copy prompt, and paste the prompt into your AI app. The prompt names the exact version you were looking at, so the AI uses that version or tells you if it has changed. A Skill can be used while you work on something else. Using the release review Skill for a different Work does not move or copy it.

​
Update a Skill

Ask the AI app that is using the Skill to improve it:
Update our release review skill: add a step to check the changelog before tagging.
Or open the Skill in Ligura and choose Edit Skill to change the SKILL.md source and its files, then Save new revision. Each change keeps a recorded revision, so you can see what changed and who changed it. If someone else saved a newer version while you were editing, Ligura keeps your edits and shows you the latest version before anything is overwritten. When a Skill is replaced by a better one, use Replace so people and AI apps move to the newer Skill. Use Archive to take an old Skill out of the active set.

​
Download a Skill

Some AI apps can install skills locally. To use a Skill that way, open it in Ligura and choose:
  • Download Skill for a ZIP with SKILL.md and every supporting file.
  • Download SKILL.md for the instructions only. Supporting files are not included.
Installing a downloaded Skill follows that app’s own steps. A downloaded copy does not update when the Skill changes in Ligura.

​
Share a Skill with your team

Share a Skill like any other saved item. Share the whole Work, or share just the Skill so a colleague can use it without seeing the rest of the Work. Check Let them use it with their AI apps if they should be able to use it from their own connected AI apps. See sharing and invitation links.

​
What a Skill can and can’t do

  • The AI follows the Skill with its own tools and permissions. If a step needs a tool, file, or connection the app doesn’t have, the AI should tell you instead of claiming it finished.
  • A Skill grants nothing on its own. Requested tools listed in a Skill are a request, never a permission. A Skill can’t change who has access, switch workspace, or approve actions you haven’t approved.
  • Ligura doesn’t run Skills. It stores and serves the text. Scripts inside a Skill are shown as text and never run by Ligura.
  • Text files only, for now. A Skill can hold SKILL.md and up to 31 supporting text files. Each file can be up to 64 KiB, and the whole Skill up to 512 KiB. Images and other binary files aren’t supported in Skills yet.
Keep passwords, API keys, and other secrets out of Skills, as with any saved work.

​
If something doesn’t work

Next: What you can save. For help, contact support@getligura.com.