NewsBlur: Skill for Claude Code

Your task

Write a blog post announcing a new NewsBlur feature based on the changes in the current branch. The blog post should match NewsBlur's voice and style.

Arguments provided: {{ arguments }}

Use the arguments to determine:

• Length: short (2-3 paragraphs), medium (standard feature announcement), or long (in-depth with history/context)
• Tone: Any specific tone guidance (excited, technical, casual, etc.)
• Focus: Any specific aspects to emphasize

Steps to execute

1. Analyze the branch changes to understand the feature:

   git log main..HEAD --oneline
   git diff main..HEAD --stat
   

   Then read the full diff to understand what was built:

   git diff main..HEAD
   

2. Read the last 10 blog posts to match the voice and style:

   ls -t blog/_posts/*.md | head -10
   

   Read each of these files to understand:

   • The conversational first-person voice
   • How features are introduced and explained
   • Screenshot placement and formatting
   • Section structure (headers, examples, etc.)
   • How posts end (forum link, availability info)

3. Write the blog post following these guidelines:

   Front matter:

   ---
   layout: post
   title: <compelling title that describes the feature>
   date: YYYY-MM-DD 09:00:00 -0700  # 9am Pacific on the publish date
   tags: ["web"]  # or ["ios"], ["android"], or multiple
   ---
   

   Always set date to 9am Pacific on the publish date, the same date as the filename. Use -0700 during daylight time (second Sunday of March to first Sunday of November) and -0800 otherwise. blog/_config.yml sets timezone: America/New_York, so a post dated only by its filename publishes at midnight Eastern, and feed readers in Pacific time show it on the previous evening.

   Voice and style:

   • First-person conversational tone ("I wanted...", "You can now...")
   • Start with the problem or motivation, then introduce the solution
   • Be direct and practical, not marketing-speak
   • Include real examples of how to use the feature
   • No em dashes or hyphens as punctuation. Restructure sentences instead.
   • Avoid AI slop: no overly polished language, no filler phrases like "excited to announce"