Skip to content

A Skill is reusable guidance for doing a particular kind of work. It captures a method the operator can consult when relevant, so a useful process does not depend on finding and repeating an old conversation.

Skills are useful for research, writing, analysis, design, and other tasks where the approach matters as much as the final request.

Give a Skill a clear job

A useful Skill explains when to use it, how to approach the work, and what a good result must contain. Keep its responsibility narrow enough that the operator can recognize when it applies.

For example, a Customer research synthesis Skill could specify:

  1. Identify the research question and the supplied evidence.
  2. Group observations by customer problem.
  3. Preserve disagreements and distinguish observations from interpretation.
  4. Rank findings by strength of evidence.
  5. Return a short synthesis with source links and unanswered questions.

The interview transcripts belong in Sources or Files. The Skill describes how to work with them.

Create, import, and use

Create or import a Skill in the owning Workspace, Agent, or Project surface. Give it a specific name and a description of when it should be used. Review imported instructions and dependencies before making them available to your work.

An available Skill can be discovered and consulted when relevant. Availability is different from proof that its contents were used in a particular result. For an important task, name the Skill in your request and ask for an output that makes its method observable.

ResourcePurpose
DesignVisual and brand guidance
FileSupplemental reference material
InstructionsStanding direction for the operator
SkillA reusable method for a kind of task

Use Skills from the Composer

Use /skill in the slash command menu to create or add a Skill through the available workflow. Check where the resource will be saved or assigned before confirming.

To identify a specific Skill for a request, type @ and select it from the mention picker. Then describe the task and supply the inputs. A mention references the Skill; it does not assign it permanently to the receiving resource.

For example, select your Customer research synthesis Skill and write:

Use this Skill to synthesize the attached interviews. Focus on onboarding problems. Include source references, contradictory observations, and the questions we should investigate next.

Attach the interviews using Composer attachments. Keep stable product background in Files so the Skill can stay focused on the method.

Structure a useful Skill

SectionContentExample
When to use itThe task it is designed forSynthesizing customer interviews
InputsWhat the work depends onResearch question and source material
MethodSteps and decision criteriaGroup observations, preserve disagreement, assess evidence
OutputWhat the result must containFindings, citations, limitations, and next questions
ReviewHow to judge whether it workedEach major finding is traceable to a source

Write steps that improve judgment, not a transcript of every click from a previous task. Leave room for the Operator to adapt to the actual evidence. If an input is missing, explain whether the method should ask for it or proceed with an explicit limitation.

Example: a publication review

A separate Publication review Skill could check a draft for unsupported claims, unclear terminology, broken references, and missing context. Its output might be a short list of necessary corrections followed by the revised draft.

Keep this distinct from the research Skill when the two have different inputs and outcomes. You can use both in a larger workflow without turning either into a collection of unrelated responsibilities.

Improve the method

Try the Skill against a real task and inspect the result. Look for missing evidence, ambiguous steps, or unnecessary work. Update the method at its owner rather than adding contradictory instructions in several places.

Inherited resources retain their original owner and access restrictions. A Skill cannot authorize a connection, expose credentials, or expand the operator's permissions. If its method needs an external service, set up that access separately through Connections.

When publishing a template, review redistribution rights for included Skills and their dependencies. A private method available to you is not automatically yours to redistribute.