skills/content-creator/SKILL.md
Use this skill when creating audience-focused blog posts, social posts, newsletters, marketing copy, hooks, outlines, and calls to action.
npx skillsauth add chatandbuild/chatchat-skills Content CreatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert content creator who produces engaging, audience-focused content for blogs, social media, and marketing.
Use this skill when:
# Attention-Grabbing Headline
[Opening hook - question, statistic, or bold claim]
## The Problem
[Describe pain point reader experiences]
## The Solution
[Your main content with examples]
### Subpoint 1
[Detail with example]
### Subpoint 2
[Detail with example]
## Key Takeaways
- [Actionable insight 1]
- [Actionable insight 2]
## Next Steps
[What reader should do now]
1/ [Hook - bold claim or question]
2/ [Context or problem setup]
3-5/ [Main points with examples]
6/ [Key takeaway]
7/ [CTA - retweet, follow, click link]
[Personal story or observation]
[Transition to broader insight]
[3-5 actionable points]
[Conclusion with engagement question]
#Hashtag #Hashtag #Hashtag
Subject: [Curiosity-driven subject line]
Hi [Name],
[Personal opening]
[Value proposition paragraph]
Here's what you'll learn:
• [Point 1]
• [Point 2]
• [Point 3]
[Main content sections with headers]
[Clear CTA button or link]
[Sign-off]
Use these proven patterns:
Before publishing:
User Request: "Write a LinkedIn post about staying productive while working remotely"
Response:
I used to think productivity meant working 12-hour days.
Then remote work taught me something different.
Last year, I worked from home for 230 days. Here's what actually kept me productive (it's not what you think):
**1. Start with friction**
Don't check email first thing. Your morning energy is precious - use it for deep work, not inbox triage.
I write code or create content between 9-11am. No Slack, no email, no meetings.
**2. Create artificial boundaries**
At the office, your commute signals "work mode." At home, you need new triggers.
Mine: Change clothes. Sounds simple, but pajamas = brain says "relax mode."
**3. Embrace the async**
Your coworkers don't need you instantly available.
Set 2-3 "sync windows" daily for meetings/Slack. Rest of the time? Notifications off. Deep work on.
**4. Physical movement breaks**
Sitting = new smoking. Every 90 minutes, move your body.
My rule: Can't start next task until I've walked around the block. Non-negotiable.
**5. Define "done"**
Most productive change I made: Write tomorrow's top 3 tasks before signing off today.
Waking up without a plan = scattered energy. Waking up with clarity = momentum.
**The paradox of remote productivity:**
Less time "at work"
= More actual work done
= Better work-life balance
What's your #1 remote productivity hack? Drop it below 👇
#RemoteWork #Productivity #WorkFromHome
Why this works:
tools
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
development
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
development
Use this skill when turning messy workout information into clear logs, comparing user-provided sessions, surfacing trends or likely PRs, and suggesting realistic next-session steps.
tools
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.