asankarasubramanian/slack-rewriter
.cursor/skills/slack-rewriter/SKILL.md
Rewrite rough thoughts into concise, simple, and direct Slack messages. Use when the user asks to rewrite, clean up, tighten, or simplify a message for Slack, or provides a draft message they want improved.
testing
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add asankarasubramanian/pm-alfred slack-rewriterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 11:59 PM206.0s1 file scanned
SKILL.md
- name:
- slack-rewriter
- description:
- Rewrite rough thoughts into concise, simple, and direct Slack messages. Use when the user asks to rewrite, clean up, tighten, or simplify a message for Slack, or provides a draft message they want improved.
Slack Rewriter
Rewrite the user's rough thoughts into clear, concise Slack messages.
Core Principles
- One idea per sentence. Break compound sentences apart.
- Lead with the point. Put the ask, decision, or update first — context second.
- Cut filler ruthlessly. Remove "just wanted to", "I think maybe", "as you know", "basically", "going forward", hedging language, and throat-clearing.
- Use short words. "use" not "utilize", "help" not "facilitate", "need" not "require".
- Prefer active voice. "We shipped X" not "X was shipped by the team".
- Keep it scannable. Use bullets for 3+ items. Bold the key noun or action in each bullet.
Rewriting Process
- Identify the one thing the message needs the reader to know or do
- Open with that — in one line
- Add only the context the reader needs to act or understand
- Remove everything else
- Adapt tone to the audience:
- Engineers: be specific and technical
- Leadership: lead with impact/outcome, keep it brief
- Cross-functional: avoid jargon, state what you need clearly
- Casual channels: keep it light and human
Before / After Examples
Rough thought:
Hey team, just wanted to give a quick update — so we've been looking into the latency issue that was reported last week and after some investigation it looks like the root cause is the N+1 query in the dashboard endpoint, we're planning to batch the queries which should bring load times down significantly, hoping to have a fix out by Thursday
Rewritten:
Latency fix update: Root cause is an N+1 query in the dashboard endpoint. Fix is to batch the queries — targeting Thursday.
Rough thought:
Hi Sarah, I was wondering if you might have some time this week to chat about the onboarding flow? I have some thoughts about how we could potentially simplify the first-time user experience and wanted to get your perspective before I put together a more formal proposal
Rewritten:
Hey Sarah — I have ideas for simplifying the onboarding flow and would love your input before I write up a proposal. Got 30 min this week?
Rough thought:
So I've been thinking about this and I think we should probably go with option B because option A would require us to refactor the auth module which would take at least 2 sprints and I'm not sure we have the bandwidth for that right now given the Q2 commitments, whereas option B is more incremental and we can ship it within the current sprint
Rewritten:
Recommending option B. Option A needs a 2-sprint auth refactor we can't absorb with Q2 commitments. Option B ships this sprint.
What NOT to Do
- Don't add formality the original didn't have
- Don't inject emoji unless the user's draft uses them
- Don't turn a casual message into a corporate memo
- Don't lose the user's voice — simplify, don't sanitize
Related Skills
asankarasubramanian/working-backwards
development
VerifiedTrustedCommunity
Use when asked to "working backwards", "PR/FAQ", "Amazon PR/FAQ", "write a press release", "define a new product", or "write a customer-focused PRD". Helps define products by starting with the customer problem and desired outcome before building. The Working Backwards process (developed at Amazon) forces clarity on customer value before committing engineering resources.
SKILL.mdUpdated Apr 16, 2026
asankarasubramanian/user-feedback-synthesizer
databases
VerifiedTrustedCommunity
Analyze collections of user feedback to identify patterns and themes. Use when you have user feedback from multiple sources that needs synthesis.
SKILL.mdUpdated Apr 16, 2026
asankarasubramanian/seven-powers
development
VerifiedTrustedCommunity
Use when asked to "7 Powers", "build a competitive moat", "analyze defensibility", "find sustainable advantage", "economic moats", or "Hamilton Helmer framework". Helps identify durable competitive advantages. The 7 Powers framework (created by Hamilton Helmer) reveals the economic structures that protect business value from competition.
SKILL.mdUpdated Apr 16, 2026
asankarasubramanian/strategic-narrative
development
VerifiedTrustedCommunity
Use when asked to "strategic narrative", "Andy Raskin", "tell our company story", "write a pitch deck", "explain why customers should care", or "movement narrative". Helps craft compelling narratives that define movements rather than just selling products. The Strategic Narrative framework (created by Andy Raskin) transforms pitches from feature lists into stories about change.
SKILL.mdUpdated Apr 16, 2026