Skip to the guide text
godspeedmissioncontrol.com
Guide menu

Write your own skill

Write a skill for a job you repeat, check that Godspeed picks it by itself, and run it on a schedule.

Applies to every installation

Last updated 20 October 2026

On this page
  1. Write it
  2. Change a skill
  3. Check that Godspeed picks it
  4. Run it on a schedule

A skill is a folder in the skills folder of your mission control folder, named in lowercase with hyphens. Its SKILL.md file starts like this:

Markdown
---
name: plan-my-day
description: Plan a day around fixed commitments, priorities and available time.
---

Use the meetings, deadlines, tasks and energy limits I provide to propose today's plan.
  • name is the folder's name.
  • description says when to use it, in the words you would say. Godspeed picks skills by this line.
  • The steps follow: what to read, what to make, what to do when something is missing, and what never to do.

Write it

#
  1. In the chat, describe the job and ask Godspeed to write the skill:

    Write a skill called plan-my-week that plans my week. Show me skills/plan-my-week/SKILL.md before you save it.
  2. Check that it says what input it expects, which files it reads, what to do when information is missing, and that it sends and publishes nothing.

  3. Ask for changes until it fits, then tell Godspeed to save it. Godspeed's brain in the notebook lists it under Skills, marked Your own.

Change a skill

#

Open the skill on Godspeed's brain, change What it is for or The steps, and click Save. Earlier versions takes you back. You can also ask Godspeed to interview you about what to change and update the same file.

Check that Godspeed picks it

#

A conversation that began before the skill existed does not pick it by itself, so test in a new one:

  • Telegram on a server: send /new.
  • Claude Code or Codex: start a new session in your mission control folder.
  • The notebook's chat: update first, then click Clear conversation. Your next message starts a fresh conversation; your saved notebook stays.

Then check three things:

  1. In a new conversation, ask for the job without naming the skill. Then ask "Which skill did you use?" If it was not yours, add your words to its description.
  2. Give it a real example, such as a pasted email. Ask "Which files did you read?" and check that dates and names stayed exact.
  3. Ask again, adding "Do not open profile/projects.md for this." It passes if it says what is missing. If it invents the gap, write into the skill what to do without that file.

Run it on a schedule

#

Ask:

Run my plan-my-week skill every weekday at 7:00.

Godspeed makes a routine, a job that runs at set times, that follows the skill. It appears under Settings > Routines (Pause, move or run a routine).

Something wrong or unclear? Tell us on GitHub.