Reusable workflows with Mythos Skills

Suppose you have just finished a useful review of a service page. You checked the opening message, removed unsupported claims and made the enquiry action clearer. On the next page, you want to follow the same process without reconstructing it from a previous conversation.

A Mythos Skill lets you save that process as reusable instructions. Your next request supplies the page and the outcome; the skill supplies the review method. Start with one task you already repeat and a result you know how to judge.

A page-copy-review skill could ask Mythos to identify the audience, check whether the opening explains the service, flag claims without supporting facts and suggest clearer wording for the main action. It could return the three most useful changes, with a reason and a proposed sentence for each.

That is more useful than a skill called Improve everything. A narrow job gives you a clear reason to select it and makes the result easier to review. It also leaves room for a different process when you are writing an article or explaining a product update.

Include an example if it resolves an ambiguity. For instance, explain that an unsupported claim about being the city's leading studio should become a question for the owner, rather than another superlative.

Your studio's name, audience and preferred terminology belong in Knowledge when they should inform future work. A skill describes a task you choose to perform.

For the copy review, Knowledge might explain that the business teaches adults who have never used a pottery wheel. The skill describes how to examine a page. Your current message identifies the beginner workshop page and asks for findings before any edits.

Keep temporary details in that message. This week's workshop dates can stay with the current assignment; the instruction to flag unclear booking information belongs in the reusable skill.

Workspace owners and admins can add a skill from Workspace settings → Skills. Choose Add → Write manually to enter its name, description and instructions. A short name such as page-copy-review is easy to recognize later. Build with Mythos is another option when you want help turning a process into a skill.

Once it is saved, type / in the project composer and select it, or use its exact /skill-name. For example: /page-copy-review Review the beginner workshop page and suggest three changes. Leave the page unchanged.

Custom workspace skills run when you explicitly select them. Saving one does not make it run automatically on every related request. Mythos's built-in guidance is separate and can be used automatically when relevant. The Skills documentation covers creation, imports and the available controls.

Try the saved workflow on one page before relying on it across a site. Look for specific failures: did it rewrite text you wanted to keep, repeat obvious advice or miss an unsupported promise? Correct the instruction responsible for that result.

A useful revision might say to preserve the author's wording unless it creates a concrete problem, or to quote the sentence being discussed so you can find it quickly. Add those lessons to the skill instead of making the next chat message longer.

Keep the final review with a person who knows the business. A reusable process makes the work more consistent; the published copy still needs accurate facts and a deliberate choice about what to say.