create-scratch
Create a new scratch file in .agents/scratches/
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
You are creating a new scratch file in the .agents/scratches/ directory.
Your Task
- Determine the slug - Based on the conversation context and intent, determine an appropriate file slug (kebab-case recommended). Ask the user if unclear.
- Gather content - Collect or generate the scratch content from the discussion
- Create the file - Use the create-scratch script to generate the file
Usage
The script will automatically:
- Generate a unique three-word ID (e.g.,
calm-teal-cloud) - Create frontmatter with current date and formatted title
- Save the file as
{id}-{slug}.mdin.agents/scratches/
Creating the File
Option 1: Direct Content
If you have the content ready, run:
bun scripts/create-scratch.ts "<slug>" "Your scratch content here"
Option 2: Multi-line Content (Heredoc)
For multi-line content, use heredoc:
bun scripts/create-scratch.ts "<slug>" << HEREDOC
Your multi-line
scratch content
goes here
HEREDOC
Option 3: Pipe Content
You can also pipe content:
echo "Your content" | bun scripts/create-scratch.ts "<slug>"
File Format
The created file will have:
---
date: 2026-01-21
title: Scratch Title
---
Your content here
The title is automatically formatted from the slug (e.g., quick-notes → Quick Notes).
Guidelines
- Use descriptive slugs in kebab-case (e.g.,
exploration-ideas,temporary-notes) - Scratch files are for temporary notes, explorations, or ideas
- The unique ID ensures no filename conflicts
- Files are automatically dated for organization
Begin
Create a scratch file using an appropriate slug based on the conversation context and content for notes or exploration.
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-03-11
- Index updated
- 2026-03-11
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!