Guides

Skill Building Guide

Describe it to your Mind, and your Mind builds it. This guide takes one example, a morning standup digest read from your team's Linear board, from a single message to a published Skill on the Bazaar. The same flow works for any app your team uses.

What gets built

What your Mind builds for you.

A Skill gives your Mind a new ability: summarising your sprint, triaging your inbox, monitoring a competitor's market moves, posting a weekly update. You describe the Skill to your Mind in plain language, and your Mind builds it.
When you describe a Skill, your Mind assembles four things

How it's found

The listing other builders see when they browse the Bazaar.

Developer term: a Registry Offering.

How it connects

The wiring between the Skill and the app it works with.

Developer term: an App Manifest.

What it can do

The concrete actions the Skill is allowed to perform.

Developer term: Tool Schemas.

How it behaves

The routine the Skill follows over time.

Developer term: a Skill Playbook.

You do not need to write any of these directly. You describe the outcome, and your Mind builds and maintains all four.
01

Describe

Describe the Skill to your Mind.

Talk to your Mind in Telegram or email. Describe what the Skill should do, where it gets the information, and what you want as the result.Use this prompt to define the Skill:
Build me a Skill that reads my team's Linear board and sends me a morning standup digest: what shipped yesterday, what's in progress, and what's blocked. Keep it short.
You describe the outcome. Your Mind handles how it is implemented.
02

Refine

Refine the Skill behaviour.

Your Mind proposes how the Skill will work and reads it back to you in plain language. Review the proposal and adjust until it matches what you want.Use this prompt to refine the behaviour:
Group it by assignee, and flag anything that's been blocked for more than two days.
When the description looks correct, tell it to finish building the Skill.Use this prompt to confirm:
That's it. Build it.
03

Connect

Connect the tool.

The Skill reads your Linear, so it needs access. Give Minds access to the tool:
  1. Go to your Minds profile page.
  2. Click My Connections and search for the app, Linear in this example.
  3. Click the app and enter the API key you created in Linear.
  4. Press Save Key to confirm.

The platform stores and uses the key.

Your Mind never holds the key directly. Set this up once, and any future Skill that uses Linear (or the app of your choice) reuses the same Connection.
04

Run

Run the Skill.

Use the Skill the way you'd ask a teammate.Use this prompt to generate the standup:
Give me today's standup.
If the result does not match what you are looking for, tell your Mind what to change. It adjusts the Skill and shows you new results.Use this prompt to adjust:
Too long. One line per person, and drop anything already done.
05

Inspect

Inspect Skill actions and access.

Before you rely on a Skill or publish it, ask your Mind to show what it does and what it can access.Use this prompt to request a summary:
Show me what this Skill can do, what it reads, and what it can change. Flag anything it should not touch.
Your Mind lists its actions and its access scope. Tighten anything that looks too broad before anyone runs it.
06

Publish

Publish the Skill to the Bazaar.

After verifying the behaviour and the scope, publish the Skill to the Bazaar for other Minds and users to equip.Use this prompt to publish:
Publish this Skill to the Bazaar as "Sprint Standup" so my team can equip it.

FAQ

Questions builders ask.

Can I build a Skill around my own internal tool?

Yes. Paste its API docs into the chat and describe what you want. Your Mind builds the Skill around that API.

Where does the Connection live?

On your Minds profile page. You add a Connection once, and the platform reuses it for every Skill that needs it. Your Mind never holds the key.

Can I see what a Skill can touch before I trust it?

Yes. Ask your Mind to show its actions and its access. It lists what the Skill reads, what it can change, and where its limits are, so you can tighten anything before you rely on it.

Can I change a Skill later?

Yes. Tell your Mind what to change. It updates the Skill and shows you the result before you deploy it.

What if I want to add more capabilities to the Skill?

Tell your Mind. It updates the Skill to match, and you re-check it the same way you did the first time.

Appendix

Copy-paste prompts.

Use this list when you want to recreate or share the full flow.
1. Describe it:
   Build me a Skill that reads my team's Linear board and sends me a morning standup: what shipped yesterday, what's in progress, and what's blocked. Keep it short.
 
2. Refine it:
   Group it by assignee, and flag anything that's been blocked for more than two days.
 
3. Finish it:
   That's it. Build it.
 
4. Try it:
   Give me today's standup.
 
5. Adjust it:
   Too long. One line per person, and drop anything already done.
 
6. Check it:
   Show me what this Skill can do, what it reads, and what it can change. Flag anything it should not touch.
 
7. Share it:
   Publish this Skill to the Bazaar as "Sprint Standup" so my team can equip it.
Describe what you want in one message. Your Mind builds it, you check it, and now others can equip it too.