December v0.4.19

Skills & Playbooks

Install and write skills that teach December how to do a task in your project.

This page helps you install and write skills, so December can do repeated tasks your way.

Overview

A skill is a folder with a SKILL.md file. The file tells December how to do one task, such as a database migration or a code review.

Each skill becomes a slash command. For example, a skill named db-migrate becomes /db-migrate. You can also type /skill:db-migrate.

When you run a skill, December gives the task to a subagent. A subagent is a separate agent with its own context. This keeps your main conversation short.

Run a skill

  1. Type / and the skill name. Add your goal after the name:
/db-migrate add a status column to the orders table
  1. To see all your skills, type /skills in a session.

For a plan before December edits files, use /plan. See Session Artifacts & Planning.

Manage skills with the CLI

Use the december skill command to list, inspect, add, and remove skills:

# List all skills that December finds
december skill list

# Show the description and location of a skill
december skill info db-migrate

# Add skills from a GitHub repository to this project (.december/skills)
december skill add phasehumans/skills

# Add skills for all your projects (~/.december/skills)
december skill add phasehumans/skills --global

# Remove an installed skill package
december skill remove skills

december skill add clones the repository with Git. If the folder already exists, December runs git pull to update it.

Where December looks for skills

December finds skills in these folders, in your project and in each parent folder up to the Git root:

  • .december/skills
  • .agents/skills
  • .agent/skills
  • .claude/skills

December also finds skills in your home folder, for example in ~/.december/skills, ~/.agents/skills, and ~/.claude/skills. Skills that you installed for other agents work in December too.

Plugins can also add skills. Type /plugin to manage plugins.

Write a project skill

  1. Make a folder at .december/skills/<skill-name>/.
  2. Add a SKILL.md file to the folder. The file needs a name and a description:
---
name: db-migrate
description: Make a database migration and test it before you commit.
argument-hint: '[migration-name]'
---

# Database migration

When you change the database schema:

1. Read the schema in `packages/database/prisma/schema.prisma`.
2. Make the migration with `bun db:migrate:dev --create-only`.
3. Apply the migration to the test database:
    ```bash
    bun db:migrate:test
    ```
4. Run the integration tests.
  1. Exit December and start it again. /db-migrate now shows in the slash command menu.

Frontmatter fields

  • name (required): The skill name. December uses it as the slash command.
  • description (required): What the skill does. December shows it in december skill list.
  • argument-hint: The arguments that the skill expects, for example [migration-name].
  • allowed-tools: The tools that the skill can use, for example bash.