slack-community

Name: slack-community
Author: getnao

168stars52forks

How to install slack-community?

getnao/sylph/slack-community

$npx -y skills add getnao/sylph --skill slack-community

Installs into the current project.

Summary

Guidelines for posting in the [your-company] Slack community channel.

Files · 1

View on GitHub

SKILL.md

1	# Slack Community
2
3	Guidelines for posting in the [your-company] Slack community channel.
4
5	## MCP connectors
6
7	\| Connector \| Purpose \|
8	\|-----------\|---------\|
9	\| Slack \| Read community channels, draft responses \|
10
11	## Tone
12
13	- Casual, helpful, brief
14	- Peer-to-peer, not corporate announcement
15	- Use plain language, no marketing speak
16	- Match the energy of the channel - read recent messages first
17
18	## What to announce
19
20	\| Type \| Example \| Post? \|
21	\|------\|---------\|-------\|
22	\| New feature shipped \| "Just shipped date range filters on dashboards" \| Yes \|
23	\| Bug fix (user-reported) \| "Fixed the CSV export timeout - thanks for flagging" \| Yes \|
24	\| Content published \| "New blog post on [topic] - link" \| Yes, if relevant to community \|
25	\| Event \| "Hosting a meetup in [city] on [date]" \| Yes \|
26	\| Milestone \| "Hit 100 connected warehouses this week" \| Yes, keep it humble \|
27	\| Minor patch \| Dependency bump, typo fix \| No \|
28	\| Internal ops \| Hiring, fundraising, internal process \| No \|
29	\| Sales/marketing \| Outbound campaigns, pricing changes \| No \|
30
31	## Cadence
32
33	- Max 2-3 posts per week in the main community channel
34	- Space announcements at least 1 day apart
35	- Don't post on weekends unless it's urgent
36	- Batch small updates into a weekly roundup if there are many
37
38	## Message format
39
40	- Lead with what changed, not the backstory
41	- One short paragraph, 2-3 sentences max
42	- Link to docs, blog, or changelog for details
43	- Use emoji reactions, not threaded announcements (keeps it casual)
44
45	## Guardrails
46
47	- Draft first - never post directly; save to `content/slack/_drafts/`
48	- No customer names in community posts
49	- No pricing or commercial info in community channels
50	- No negative framing - "fixed" not "was broken", "improved" not "was slow"
51	- CAO or team reviews before posting
52
53	## Self-improvement
54
55	After the CAO reviews and approves a Slack community post:
56
57	1. Move the final version from `content/slack/_drafts/` to `content/slack/_published/`
58	2. Diff what was drafted vs what the CAO kept - identify patterns in her edits to tone, format, or what she announces
59	3. Update `content/slack/_insights.md` with what worked, what she changed, and why (note community reactions)
60	4. If her edits reveal a new rule (e.g. "never announce features without a link to docs", "always tag the engineer who shipped it"), add it to the Message format or What to announce sections
61	5. If a post gets strong community engagement, save it to `content/slack/_examples/`

People who liked this also viewed

6 picks

Type

slack-community

168stars52forks

View on GitHub

How to install slack-community?

getnao/sylph/slack-community

$npx -y skills add getnao/sylph --skill slack-community

Installs into the current project.

Summary

Guidelines for posting in the [your-company] Slack community channel.

Files · 1

View on GitHub

SKILL.md

1	# Slack Community
2
3	Guidelines for posting in the [your-company] Slack community channel.
4
5	## MCP connectors
6
7	\| Connector \| Purpose \|
8	\|-----------\|---------\|
9	\| Slack \| Read community channels, draft responses \|
10
11	## Tone
12
13	- Casual, helpful, brief
14	- Peer-to-peer, not corporate announcement
15	- Use plain language, no marketing speak
16	- Match the energy of the channel - read recent messages first
17
18	## What to announce
19
20	\| Type \| Example \| Post? \|
21	\|------\|---------\|-------\|
22	\| New feature shipped \| "Just shipped date range filters on dashboards" \| Yes \|
23	\| Bug fix (user-reported) \| "Fixed the CSV export timeout - thanks for flagging" \| Yes \|
24	\| Content published \| "New blog post on [topic] - link" \| Yes, if relevant to community \|
25	\| Event \| "Hosting a meetup in [city] on [date]" \| Yes \|
26	\| Milestone \| "Hit 100 connected warehouses this week" \| Yes, keep it humble \|
27	\| Minor patch \| Dependency bump, typo fix \| No \|
28	\| Internal ops \| Hiring, fundraising, internal process \| No \|
29	\| Sales/marketing \| Outbound campaigns, pricing changes \| No \|
30
31	## Cadence
32
33	- Max 2-3 posts per week in the main community channel
34	- Space announcements at least 1 day apart
35	- Don't post on weekends unless it's urgent
36	- Batch small updates into a weekly roundup if there are many
37
38	## Message format
39
40	- Lead with what changed, not the backstory
41	- One short paragraph, 2-3 sentences max
42	- Link to docs, blog, or changelog for details
43	- Use emoji reactions, not threaded announcements (keeps it casual)
44
45	## Guardrails
46
47	- Draft first - never post directly; save to `content/slack/_drafts/`
48	- No customer names in community posts
49	- No pricing or commercial info in community channels
50	- No negative framing - "fixed" not "was broken", "improved" not "was slow"
51	- CAO or team reviews before posting
52
53	## Self-improvement
54
55	After the CAO reviews and approves a Slack community post:
56
57	1. Move the final version from `content/slack/_drafts/` to `content/slack/_published/`
58	2. Diff what was drafted vs what the CAO kept - identify patterns in her edits to tone, format, or what she announces
59	3. Update `content/slack/_insights.md` with what worked, what she changed, and why (note community reactions)
60	4. If her edits reveal a new rule (e.g. "never announce features without a link to docs", "always tag the engineer who shipped it"), add it to the Message format or What to announce sections
61	5. If a post gets strong community engagement, save it to `content/slack/_examples/`

People who liked this also viewed

6 picks

Type