creating-articles
Creates new blog posts for the Artsy Engineering blog. Use when the user wants to write, create, or start a new blog post or article.
When & Why to Use This Skill
This Claude skill streamlines the end-to-end process of creating professional blog posts for the Artsy Engineering blog. By automating template selection, author validation, and front-matter configuration, it ensures that technical articles are consistently formatted and adhere to organizational standards, significantly reducing the administrative overhead for developers and writers.
Use Cases
- Case 1: Quickly initiating a 'regular-post' to document a specific technical problem and its solution, ensuring the file is correctly dated and formatted for the Jekyll-based blog.
- Case 2: Drafting a comprehensive technical deep-dive using the 'long-post' template to provide a structured narrative for complex architectural changes or new feature releases.
- Case 3: Writing a narrative-driven 'epic-post' that follows a monomyth structure to share significant engineering journeys or major project milestones with the community.
- Case 4: Automating the validation of author credentials against the site's configuration file (_config.yml) to maintain data integrity and proper attribution across the engineering blog.
| name | creating-articles |
|---|---|
| description | Creates new blog posts for the Artsy Engineering blog. Use when the user wants to write, create, or start a new blog post or article. |
Creating Articles
For full documentation, see docs/authoring_articles.md.
Workflow
Step 1: Gather Information
Use AskUserQuestion to ask the user:
Template selection - Ask which template they want to use:
regular-post- Short, straightforward posts (recommended for most posts)long-post- Detailed posts with introduction, body, and conclusionepic-post- Narrative-style posts following the monomyth structure
Author name - Ask for their name, then check if they exist in
_config.ymlunder theauthors:key.
Step 2: Validate Author
Read _config.yml and search for the author under the authors: section.
If author exists: Use their author key (e.g., orta, db, joey).
If author does not exist: Inform the user they need to add themselves to _config.yml first:
authors:
authorkey:
name: Full Name
github: githubUsername
twitter: twitterHandle # optional
site: https://example.com # optional
Step 3: Create the Post
- Generate filename:
YYYY-MM-DD-post-title.markdown(use today's date) - Copy the selected template from
Post-Templates/to_posts/ - Update the front matter:
- Set
title - Set
dateto today - Set
authorto the author key - Set
categories(ask user if not provided)
- Set
Templates Reference
| Template | File | Use Case |
|---|---|---|
| Regular | Post-Templates/YYYY-MM-DD-regular-post.markdown |
Quick posts about a problem and solution |
| Long | Post-Templates/YYYY-MM-DD-long-post.markdown |
Detailed technical deep-dives |
| Epic | Post-Templates/YYYY-MM-DD-epic-post.markdown |
Narrative journey-style posts |