Skip to content
Skills Library
Marketing & content · Writing

create-note

/create-note

Use when user wants to capture learnings, document insights, or create a draft blog post from their current project

Repository
skills ↗
Licence
MIT
Last repository change
11.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when user wants to capture learnings, document insights, or create a draft blog post from their current project

Original author description

Use when user wants to capture learnings, document insights, or create a draft blog post from their current project

How it works

  1. When to Use
  2. Configuration
  3. Workflow
  4. Frontmatter Schema
  5. Example
  6. Notes
Original SKILL.md headings · 166 lines, 558 words
SKILL.md preview
---
name: create-note
description: Use when user wants to capture learnings, document insights, or create a draft blog post from their current project
---

# Create Note - Draft Blog Post

Create a draft blog post from learnings in any project, saved to your blog.

## When to Use

- User says `/note` or wants to document something
- User discovered something interesting while coding
- User solved a tricky problem worth sharing
- User wants to capture context for a future blog post

## Configuration

This skill requires `BLOG_CONTENT_DIR` to be set in your `CLAUDE.md`:

```markdown
## Blog Configuration
BLOG_CONTENT_DIR=/path/to/your/blog/content/directory
```

Example: `BLOG_CONTENT_DIR=/Users/you/portfolio/src/content/blog`

**If not configured**: Ask the user where their blog markdown files should be saved before proceeding.

## Workflow

### Step 0: Check Configuration

First, check if `BLOG_CONTENT_DIR` is set in the project's or user's `CLAUDE.md`.

If NOT set, ask the user:
```
Where should blog posts be saved?

Please provide the absolute path to your blog content directory
(e.g., /Users/you/site/content/blog)

You can also add this to your CLAUDE.md to skip this prompt:
BLOG_CONTENT_DIR=/your/path/here
```

Store their answer and use it for the rest of the session.

### Step 1: Gather Information

Ask the user:
1. **What did you learn or want to document?** (becomes the title)
2. **Can you give a brief description?** (1-2 sentences for the description field)
3. **Any code snippets or examples to include?** (optional)
4. **What tags apply?** (suggest based on project context)

### Step 2: Determine Project Context

Identify the current project to tag the post:
```bash
# Get project name from current directory
basename $(pwd)

# Or from git remote
git remote get-url origin 2>/dev/null | sed 's/.*\///' | sed 's/\.git$//'
```

### Step 3: Generate Slug

Convert the title to a URL-friendly slug:
- Lowercase
- Replace spaces with hyphens
- Remove special characters
- Keep it concise (3-5 words ideal)

Example: "How to use Astro Content Collections" -> `astro-content-collections`

### Step 4: Create Blog Post

Create the file at:
```
{BLOG_CONTENT_DIR}/{slug}.md
```

**Template:**
```markdown
---
title: "{title}"
date: {YYYY-MM-DD}
description: "{description}"
tags: ["{project-name}", ...other-tags]
draft: true
---

{User's content here}

{Any code snippets with proper language fencing}

{Context about why this is interesting/useful}
```

### Step 5: Confirm and Optionally Commit

Show the user:
```
Created draft: {slug}.md

Title: {title}
Tags: {tags}
Location: {BLOG_CONTENT_DIR}/{slug}.md

Would you like to commit this draft? (y/n)
```

If yes, commit to the blog repo:
```bash
cd {BLOG_CONTENT_DIR}
git add {slug}.md
git commit -m "draft: {title}"
```

## Frontmatter Schema

Required fields:
- `title` (string) - Post title
- `date` (date) - YYYY-MM-DD format
- `draft` (boolean) - Always `true` for new notes

Optional fields:
- `description` (string) - Brief summary
- `tags` (string[]) - Array of tags

## Example

User is working on import-magic and says `/note`:

```
> What did you learn?
"How to handle ESM vs CommonJS imports dynamically"

> Brief description?
"A technique for detecting and handling both module systems"

> Any code to include?
[user pastes code]

> Tags? (suggesting: import-magic, javascript)
"javascript, esm, commonjs"
```

Creates `{BLOG_CONTENT_DIR}/esm-commonjs-dynamic-imports.md`:

```markdown
---
title: "How to handle ESM vs CommonJS imports dynamically"
date: 2025-12-31
description: "A technique for detecting and handling both module systems"
tags: ["import-magic", "javascript", "esm", "commonjs"]
draft: true
---

[Content here...]
```

## Notes

- Always set `draft: true` - use `/blog` from portfolio to publish
- Include the source project as a tag for easy filtering
- Keep the initial draft concise - can flesh out later with `/blog`

Versions

RepositoryScoreLicence
This page · builtby-win/skills100MIT
atomicinnovation/accelerator100MIT
kriscard/Skills90MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 9890c556212b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100ctx-blog
    Generate blog post draft. Use when documenting project progress, sharing learnings, or writing about development experience.
  • 100blog-draft
    Draft a blog post from ideas and resources. Use when users want to write a blog post, create content from research, or draft articles. Guides through research, brainstorming, outlining, and iterative drafting with version control.
  • 90blog-review
    Fact-check and edit a blog draft for accuracy, structure, clarity, and publication readiness. Use after drafting or when the user requests an editorial review.
  • 100blog-post-writer
    Turn Nick Nisi's raw material into a blog post draft in his voice. Use when the user says "write a blog post," "draft a post," "write about [topic]," "turn my notes into a blog post," or provides scattered ideas that need shaping. Produces a deliberately flat draft with sourced…
  • 100note-to-blog
    用于从 Obsidian 笔记库中筛选可发布内容,选择博客主题,或把已有笔记转换成博客草稿。 用户提出「选一篇笔记发博客」「写博客」「博客选题」「从笔记里找文章」或 "note to blog" 时立即使用。不用于从零撰写新文章、校对已有博客草稿或整理普通笔记。
  • 100blog-draft
    Draft a clear, source-backed blog post from an approved outline and research brief. Use when the structure and factual basis are ready for prose.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.