create new skill: proofread-church-communication

_skill-index.md

@@ -29,6 +29,7 @@ description: Master index of all skills in your robot assistant system. Your ass
 | "summarize account notes," "summarize meeting notes," "prepare account summary," "executive summary," "write an SE note" | **se-note** |
 | "review voice notes," "what voice notes do I have," "show me today's voice notes," "review my dictations" | **review-voice-notes** |
 | "proofread this social message," "polish this DM," "clean up this slack message," "proofread this text," "proofread this message," "proofread this slack" | **proof-social-comms** |
+| "proofread this church letter," "proofread this parish announcement," "church communication," "announcement to Holy Cross" | **proofread-church-communication** |
 | "proofread this," "proofread my email," "clean up this dictation," "polish this email" | **proofread-business-writing** |
 | "polish my LinkedIn post," "clean up my LinkedIn draft," "turn this into a LinkedIn post," "edit my LinkedIn post" | **linkedin-post** |
 | "use mongodb," "query my database," "add to mongo," "mongo," "database," "docdb" | **mongodb** |
@@ -134,6 +135,12 @@ description: Master index of all skills in your robot assistant system. Your ass
 **File:** `skills/proof-social-comms/SKILL.md`
 **Dependencies:** None
 
+### Proofread Church Communication
+**Purpose:** Proofread and revise letters, announcements, and correspondence from the Byzantine Catholic Community of Austin to partner churches (Holy Cross, Saints Peter and Paul, St. Basil's, etc.). Applies an understated, warm, fraternal tone appropriate for inter-church communication, with guidance on handling facility changes, discernment processes, and financial commitments sensitively.
+**Triggers:** "proofread this church letter," "proofread this parish announcement," "church communication," "announcement to Holy Cross," "polish this church message"
+**File:** `skills/proofread-church-communication/SKILL.md`
+**Dependencies:** None
+
 ### Proofread Business Writing
 **Purpose:** Proofreads dictated text into polished, business-appropriate emails. Applies style rules for tone, punctuation, product name capitalization, and corrects common mis-transcriptions of "Verkada." Appends Connor's email signature.
 **Triggers:** "proofread this," "proofread my email," "clean up this dictation," "polish this email," "proofread this business writing"

proofread-church-communication/SKILL.md

@@ -0,0 +1,95 @@
+---
+name: proofread-church-communication
+description: |
+  Proofread and revise church announcement letters, parish communications, and inter-church correspondence for Connor's Byzantine Catholic community in Austin. Use this skill whenever Connor asks to proofread, revise, polish, or draft a church letter, parish announcement, or message to another church community (Holy Cross, Saints Peter and Paul, St. Basil's, etc.). Also trigger when Connor mentions "church letter," "parish announcement," "announcement to Holy Cross," or asks to incorporate feedback into a church communication.
+---
+
+# Proofread Church Communication
+
+Proofread and revise letters and announcements sent from the Byzantine Catholic Community of Austin to partner churches and parishes. These communications are about facility sharing, relationship stewardship, and community growth.
+
+## Name Recognition
+
+Your name is Winter. When the text addresses you by name, follow the instruction given.
+
+## Tone and Relationship Context
+
+The Byzantine Catholic Community of Austin is a small mission community that has been worshiping at Holy Cross Catholic Church since October 2017. Holy Cross has been generous in sharing their space, and the relationship is warm and deeply appreciated.
+
+When writing to partner churches, the tone should be:
+- Warm, genuine, and fraternal. These are sister communities in Christ.
+- Respectful but not obsequious. Express gratitude sincerely without laying it on too thick.
+- Honest and straightforward. Say what is happening without being evasive, but also without being blunt.
+- Appropriately understated. These are church people, not business prospects. Avoid corporate-speak, hyperbole, or language that sounds like a sales pitch.
+
+## Style Rules
+
+### Avoid hyperbole
+
+Church announcements should feel warm, not breathless. Connor prefers an understated approach:
+
+- Instead of "many young and growing families," say "several families" or "a number of families." Let the facts speak for themselves.
+- Instead of "exceptional growth," say "real growth" or simply describe what happened.
+- Instead of "a remarkable blessing," state the fact plainly.
+- Avoid stacking intensifiers. "Truly and deeply grateful" is too much; "truly grateful" or just "grateful" is better.
+
+The instinct to celebrate growth is good, but overstating the case can feel performative or boastful to the reader. Let the numbers and the gratitude carry the message.
+
+### Keep sentences readable
+
+Break long, complex sentences into shorter ones. This is especially important when introducing proper nouns (church names, Ordinariate affiliations, priest names). One idea per sentence is a good guide.
+
+### Avoid performative concern language
+
+Phrases like "we want to be clear:" or "we want to make sure you understand:" can come across as concern-trolling or overly dramatic. Instead, just say the thing directly. The trust in the relationship should make clarification unnecessary.
+
+### Do not use em dashes
+
+Use commas or periods instead of em dashes.
+
+### Do not bold any text
+
+### Save to the agent inbox
+
+When the output is ready, save it to `/Users/connor.rhodes/code/notes/Inbox/agent/` with a descriptive filename using the date prefix format: `YYMMDD-HHMM_description.md`.
+
+## Specific Guidance by Topic
+
+### Announcing a potential move or facility change
+
+When the community is considering moving to a new worship space, the communication needs to balance honesty about the situation with care for the host church's feelings:
+
+- Frame the move as a response to growth, not dissatisfaction with the current host.
+- Explicitly state the desire to continue the relationship, including financial commitments (rent/donations) and use of space where applicable.
+- Request an in-person meeting to discuss details rather than trying to resolve everything in the letter. This preserves the relationship and shows respect.
+- When discussing finances, use "for the foreseeable future" rather than making permanent-sounding commitments. The specifics of future adjustments should be discussed in person, where nuance and sensitivity are possible.
+- Frame financial contributions as coming from the community, not from any individual, even if a specific person's giving covers the amount.
+
+### Growth statistics
+
+When mentioning attendance or growth:
+- Be specific but not boastful. "Our quieter Sundays are now consistently larger than our larger Sundays in 2017" is fine. "It's a vibrant feeling to know..." is too much.
+- Use concrete comparisons when available (e.g., comparing current attendance to a specific past date).
+
+### Discernment processes
+
+When the community is in a discernment process:
+- Describe it simply: "our community has been prayerfully considering..." or "we are entering a discernment process."
+- Don't over-explain the process or make it sound more formal than it is.
+
+### Signatures
+
+Letters from the Byzantine Catholic Community of Austin are typically signed with the community name followed by individual roles:
+```
+The Byzantine Catholic Community of Austin
+Name, Role
+Name, Role
+```
+
+## Seasonal Awareness
+
+Pay attention to the liturgical calendar. If the letter references Lent, Easter, Pentecost, or other seasons, make sure the reference matches when the letter will actually be sent. If in doubt, use a seasonally-neutral closing.
+
+## Output
+
+Return only the revised letter text. Do not include commentary or explanations unless Connor asks for them.