Skills

Skills give Mythos a reusable set of instructions for a particular task. Instead of explaining your review process every time, save it as a workspace skill and call it when you need it.

A skill has a name, a description, and Markdown instructions. It can also include reference files, such as a checklist or writing sample. Workspace skills are shared across the projects in that workspace.

Choose skills or knowledge

Use Knowledge for background that should apply to future requests: your audience, terminology, design conventions, or project constraints. Use a skill for a task you want to run deliberately, such as reviewing a landing page or drafting release notes.

For example, “Use sentence case in our interface” belongs in workspace knowledge. A process for reviewing a new onboarding flow belongs in an onboarding-review skill.

Custom workspace skills run when you name them with their exact /skill-name in chat. Saving a custom skill does not make it run automatically on every matching request. The Skills built by Mythos section is separate: Mythos can use relevant built-in guidance automatically, and you can also choose it with /.

Useful things to turn into skills

Give each skill one recognizable job:

• A page review that checks the main message, navigation, mobile layout, and call to action.
• A release-note workflow that turns a list of delivered changes into a short customer update.
• An accessibility review focused on keyboard use, labels, and readable content.
• A content workflow that applies your team’s tone to a particular type of page.
• A project handoff checklist that explains what the next person needs to know.

A good skill describes how to do the work. Your message supplies the current subject, scope, and desired outcome.

Who can manage skills

Workspace owners and admins can create, edit, import, and delete workspace skills. Available skills can be viewed and used by people with the necessary access to work on the project. See People and permissions.

Built-in skills are maintained by Mythos. They are available to use, but are not editable workspace documents.

Add a workspace skill

Open Workspace settings → Skills, then choose Add. You can also reach Skills from the project’s settings.

Build with Mythos

Choose Build with Mythos to start a conversation about the workflow you want to save. Explain the task, when you intend to use it, and what a useful result looks like.

For example:

/skill-creator Help me create a customer-update skill. It should turn a short
list of completed changes into a clear email for existing customers. Ask me
about our tone and the information the email must include before drafting it.

Review the proposed name and instructions before asking Mythos to save the skill. To reuse a process from an earlier conversation, describe the useful result and explicitly ask /skill-creator to turn it into a skill. A conversation about a workflow does not by itself give every project new instructions.

Write manually

Choose Add → Write manually and fill in:

Choose Add skill when the instructions are ready. The name cannot be edited later, so choose a name you will recognize in chat. You can update the description and content.

Avoid vague descriptions such as “Help with content.” A more useful description is:

Draft a customer email from a list of completed product changes. Explain the
benefit of each change in plain language. Use this for release updates, not
marketing campaigns or promises about future features.

Import from GitHub

Choose Add → Import from GitHub and enter a public GitHub URL. You can point to a repository, a directory containing SKILL.md, or the SKILL.md file itself.

For a directory or file URL, include the branch and full path. The imported package should contain the skill document and any files its instructions reference. Review third-party instructions before using them with your projects.

An import adds a workspace copy. Edit that copy in Mythos when your team’s process changes.

Upload a ZIP

Choose Add → Upload ZIP and select a .zip or .skill archive. Include SKILL.md at the root or inside one wrapping folder, with its reference files alongside it.

The archive can be up to 50 MiB. The extracted package can contain up to 200 files and 10 MiB in total; each bundled file can be up to 1 MiB. Mythos checks the package before adding it. If an import fails, correct the reported file or format problem and try the import again.

Use a skill in chat

Type / in the project composer and choose a skill, or type its exact name. Add your request after it:

/customer-update Write an update for our existing customers about the new
saved filters and CSV export. Use the changes in this message only.

Check that you are working in the workspace where the skill was saved. A skill in one workspace is not automatically available in another.

For a review, state whether you want findings or changes:

/page-review Review the pricing page. Give me the three most useful
improvements first; leave the page unchanged until I choose an improvement.

A skill can guide the work, but does not replace your instructions or the approvals needed for an external action. Review any proposed change that affects a connected account.

Write a useful skill

Keep the instructions specific enough that another person could follow them. Explain what to look at, what to avoid, and what to return.

For a page-review skill, a compact starting point is:

Review one page named in the request.
1. Identify the intended visitor and the main action.
2. Check whether the headline explains the benefit.
3. Check navigation, form labels, and the mobile layout.
4. Separate observed problems from things that need a manual check.
5. Return up to five findings, each with the location and a suggested change.
Do not invent customer quotes, conversion figures, or test results.
Review first. Change the page only when the request asks for changes.

Add a short example of the output if format matters. Keep longer reference material in bundled files and name the relevant file in the instructions. A bundled reference is most useful when the skill explains when to consult it.

The complete skill document is limited to 128 KiB of UTF-8 text, and the description to 10,000 UTF-8 bytes. These are byte limits, so some characters use more than one byte. A focused playbook is usually much shorter.

Edit, download, or remove a skill

In Settings → Skills, open a workspace skill to change its description or content. Save the change before starting the next task that needs the revised instructions.

Use Download to save its .skill package, including bundled files. You can import the package into another workspace if you have permission there.

Choose Delete skill only when the workflow is no longer needed. Deleting it removes the shared skill from that workspace’s projects. It does not undo work already done using the skill.

If you need a new name, create a skill with the new name, then remove the old one once your team has switched to it.

Keep skills useful

Start with a workflow you already repeat. Try it on a small task, inspect the result, and improve the instructions where they were unclear. Keep permanent project facts in Knowledge so that the skill does not carry stale copies.

If Mythos does not use the custom skill, check the exact slash name and current workspace first. If it uses the skill but produces the wrong result, tighten the requested scope and add a concrete example to the instructions.

Creating or using a skill through chat is part of the normal Build usage. The amount of work you ask the skill to perform still matters.