Create clear, accurate blog posts that help developers understand Lightfast capabilities and industry trends.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionblog-writerExecute the skills CLI command in your project's root directory to begin installation:
Fetches blog-writer from lightfastai/lightfast and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate blog-writer. Access via /blog-writer in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
15
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
15
stars
Create clear, accurate blog posts that help developers understand Lightfast capabilities and industry trends.
Before writing anything:
Verify every claim:
Never oversell:
Match category voice:
tldr field)faq[])resources/categories/{category}.md| Category | Use When | Audience |
|---|---|---|
| Engineering | Technical deep-dives, architecture, research | Developers, engineers |
| Company | Funding, partnerships, events, hiring | Executives, investors |
| Product | Feature launches, updates, tutorials | Customers, prospects |
| Tutorial | Step-by-step how-tos, guides | Developers learning |
| Research | Data analysis, findings, benchmarks | Engineering leaders |
Save drafts to: thoughts/blog/{YYYY-MM-DD-slug}.md
Every draft MUST include (maps to BlogPostSchema in apps/www/src/lib/content-schemas.ts):
title (core)description (150-160 chars — this is the meta description)keywords[] (min 3 — first entry is primary keyword)ogTitle, ogDescription, ogImage (social/OG)authors[] (structured array with name, url, twitterHandle)publishedAt, updatedAt (ISO datetimes)category (engineering | product | company | tutorial | research)readingTimeMinutes (integer)featured (boolean)tldr (20-300 chars)faq[] (min 1 entry)_draft: true (traceability)See resources/templates.md for complete frontmatter template.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Solid pick for teams standardizing on skills: blog-writer is focused, and the summary matches what you get after install.
blog-writer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: blog-writer is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend blog-writer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added blog-writer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
blog-writer reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for blog-writer matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for blog-writer matched our evaluation — installs cleanly and behaves as described in the markdown.
blog-writer reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in blog-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 25