bms:proofread-blog
Proofread Blog Post
Review a blog post to identify areas where clarity can be improved, assess whether the piece is balanced, and suggest general improvements. This skill is advisory only -- it does not rewrite the post.
Instructions
1. Get the blog post content
- Ask the user for the blog post content if not already provided. This could be a file path, a URL, or pasted text.
- Read the full content before beginning any analysis.
2. Read through the post completely
- Read the entire post end to end before making any notes.
- Identify the audience, purpose, and tone the author is going for.
3. Assess clarity
Look for areas where the writing could be clearer. Consider:
More from benmatselby/dotfiles
git-log-summary
Provides a summary of the git log for the past period of time. Use when asked to provide a git log summary.
18bms:git-log-summary
Provides a summary of the git log for the past period of time. Use when asked to provide a git log summary.
2bms:poc
Creates a proof of concept implementation. Provides the smallest working solution to validate an idea, with no tests and minimal production concerns.
1bms:log-session
Log a one-line summary of the current OpenCode session to today's work diary under the Completed section
1bms:draft-pr
Create a draft pull request for the current branch. Summarises the diff, fills in any PR templates, and opens the PR via the gh CLI.
1bms:code-review
Performs a harsh but constructive code review of a file or set of files. Use when asked to review, critique, or give feedback on code quality.
1