// Check text against Every's editorial style guide and return a checklist of style violations. Use when someone asks to check, review, or validate text against Every's style guide, or when editing content for Every. Returns only violations—does not auto-fix.
This skill should be used when writing social media content for Every (Twitter/X and LinkedIn). It provides the complete Every social style guide including voice, tone, post archetypes, structural patterns, and platform-specific guidance. Triggers on requests to write tweets, X posts, LinkedIn posts, social copy, or when the user asks for Every's social voice.
Transform a team-built, use-case-specific skill into a generalized, onboardable skill that any Plus One bot can adopt. Trigger when the user asks to generalize a skill, make a skill distributable, or prepare a skill for the skill store.
Automatically detects AI writing patterns and produces a sequential checklist for manual editing in Google Docs. Scans for AI tells—generic phrasing, stock openers, formal transitions, correlative constructions, vague authority claims, and other patterns—then outputs the revised text first and technical details second. Auto-triggers when generating, editing, reviewing, or polishing any written content for Every.
Fast first-pass editorial assessment for Every drafts. Use when an editor receives a draft article and needs to quickly determine if it has the essential building blocks (thesis, promise, hook, stakes) and aligns with Every's strategy and voice before proceeding to deeper editing. Returns a tight, skimmable assessment with clear next steps.
A ready-to-use prompt for automating daily social media content sourcing in Cowork. Scans your Slack channels, surfaces the best content from the last 24 hours, drafts posts for X and LinkedIn, runs everything through a built-in AI-writing detector, and saves drafts for human review. Runs on autopilot as a scheduled task — no auto-publishing, ever.
Investigate growth, activation, retention, conversion, funnel bottlenecks, and product-value realization for apps and websites using analytics, database or warehouse, billing, release, and support data. Use when asked why users do not activate, return, convert, collaborate, or retain; to measure build impact; to explain churn-like behavior; or to find concrete growth levers from product data.
| name | every-style-check |
| description | Check text against Every's editorial style guide and return a checklist of style violations. Use when someone asks to check, review, or validate text against Every's style guide, or when editing content for Every. Returns only violations—does not auto-fix. |
Check text against Every's comprehensive editorial style guide and return a structured checklist of violations. This skill identifies style issues but does not automatically fix them—allowing you to make corrections in your own document editor.
When someone provides text and asks to check it against Every's style guide:
references/every-style-guide.mdReturn violations in this exact format:
## Style Violations Found
- [ ] **[RULE CATEGORY]:** [Specific issue] → [How to fix]
- Location: "[quoted text from draft]"
- [ ] **[RULE CATEGORY]:** [Specific issue] → [How to fix]
- Location: "[quoted text from draft]"
If no violations found: Respond with "No style violations found."
Do NOT include:
Reference the complete style guide in references/every-style-guide.md for all rules. Key categories include:
User: "Check this draft against Every's style guide: [text]"
Response:
## Style Violations Found
- [ ] **Names and People:** First mention of person's name not bolded → Bold the full name
- Location: "Dan Shipper is the CEO"
- [ ] **Linking and Sources:** Study mentioned without link → Add hyperlink to source
- Location: "A study found that..."
- [ ] **Capitalization:** Subheading uses title case → Change to sentence case
- Location: "Prompting Belongs In The Business School"
- [ ] **Numbers:** Slash used instead of "per" → Spell out "per"
- Location: "$20/month"
- [ ] **Specific Words and Phrases:** "vs." used instead of "versus" → Spell out "versus"
- Location: "AI vs. human"
- [ ] **Organizations:** Company name misspelled → Use correct capitalization
- Location: "Github" should be "GitHub"
references/every-style-guide.md before checking text