TalentOS Help
Skills

Save a Skill you can reuse

Turn a piece of work you keep redoing into a Skill your Talent can run again, schedule as a Routine, or share with your workspace.

A Skill is one method, written down once. It holds the instructions, what it needs to run, what it produces, and how you will know it worked. Once a Skill exists, your Talent can run it on demand, you can pin it to a Routine, and you can share it so a teammate gets your version of the work instead of their own approximation.

Every active member can create and use their own Skills privately. You do not need to be an admin.

Write one from scratch

  1. Open Skills in the Workspace group.
  2. Click New skill, then Write it yourself. The same menu also offers Create with Talent and Import a file.
  3. Name: what it does, in a few words. Publish meeting notes.
  4. Description: when your Talent should reach for it. Use when asked to publish reviewed meeting notes. This line is what decides whether the Skill gets picked, so write it as a trigger, not a summary.
  5. Instructions: the actual method. Steps, sources, format, tone, what to skip.
  6. Success criteria: how anyone can tell the run worked. The page exists in Notion and includes decisions, owners, and a source link.
  7. Click Create skill.

You now have a private Skill. Open it, and the detail page shows the instructions, the connections the work needs, its inputs and outputs, and its success criteria.

Or have your Talent write it

Pick Create with Talent from the New skill menu, or just ask in web chat, Slack, or Telegram: "Turn what we just did into a Skill I can reuse." Your Talent drafts the name, description, instructions, and success criteria, and you edit from there. This is usually faster than a blank form, because the work is fresh.

Or import one

If you already keep methods as Markdown, choose Import a file from the New skill menu and drop in a Skill folder or a SKILL.md file. Packages must be plain text: at most 100 files and 512KB of text in total, no binaries.

Success criteria are worth the extra minute. They are what turns "it produced something" into "it produced the right thing", and they travel with the Skill when a teammate adopts it.

A worked example

Marketing turns its weekly launch recap into a Skill called Build launch recap. The description says when to use it, the instructions name the approved campaign brief and reporting sheet, and the success criteria require five metrics, three learnings, and links to both sources. Run it once on demand. If the result passes that checklist, create a Routine from the Skill.

Use it

From the Skill's detail page you can run it, or click Create routine to put it on a schedule. A Routine created this way pins the exact version of the Skill you are looking at, so later edits never change a running commitment until you decide they should. See Skill versions and what a Routine pins.

Find it again

The Skills page has search plus filters for visibility (private, shared with your department, shared with the company), how the Skill runs, and category, and you can sort by name or by last updated. If a Skill is hard to find later, the name is doing too little work: rename it.

What to check

  • Your Talent does not use the Skill when you expect it to. The description is the trigger. Rewrite it as "Use when asked to..." and name the words people actually say.
  • Runs fail on a missing tool. Open the Skill and read its connections. A Skill can only use tools you have connected.
  • The import is rejected. Check the package is text only and inside the 100 file and 512KB limits. Binary and blob backed resources are blocked by design.
  • You cannot edit a Skill you can see. It is shared, which makes it read only. See Adopt a Skill someone else wrote.

On this page