diff --git a/skills/.curated/internal-comms/LICENSE.txt b/skills/.curated/internal-comms/LICENSE.txt new file mode 100644 index 00000000..b5ed4ece --- /dev/null +++ b/skills/.curated/internal-comms/LICENSE.txt @@ -0,0 +1,201 @@ + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright (c) Microsoft Corporation. + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. diff --git a/skills/.curated/internal-comms/SKILL.md b/skills/.curated/internal-comms/SKILL.md new file mode 100644 index 00000000..b9afd5f6 --- /dev/null +++ b/skills/.curated/internal-comms/SKILL.md @@ -0,0 +1,49 @@ +--- +name: internal-comms +description: Draft or polish internal communications such as 3P updates, leadership notes, incident follow-ups, company newsletters, FAQs, launch announcements, and status reports. Use when the task is to turn raw notes, tickets, meeting takeaways, or source documents into a concise internal message matched to a specific audience and format. +--- + +# Internal Comms + +## Overview + +Use this skill to turn scattered facts into clear internal communication that is easy for teammates, leaders, or the whole company to scan. Pick the format first, mine only the relevant facts, then write with the audience's context and decision needs in mind. + +## Workflow + +1. Identify the audience, goal, and time window. Infer these from the request when possible; only ask if the structure would change materially. +2. Choose the communication format and load the matching reference: + - `references/3p-updates.md` for weekly or sprint-style Progress / Plans / Problems updates + - `references/company-newsletter.md` for broad multi-team or company-wide roundups + - `references/faq-answers.md` for recurring questions and concise answer sets + - `references/general-comms.md` for leadership notes, incident updates, launch announcements, project updates, and other one-off internal messages +3. Gather facts from the artifacts already in reach first: user notes, docs, tickets, specs, meeting notes, drafts, changelogs, or chat exports. +4. If connected tools exist and the user wants a fuller roundup, use them selectively to confirm dates, pull authoritative language, or find missing context. +5. Draft with signal over flourish. Lead with outcomes, decisions, impact, risks, and next actions. +6. Review for accuracy, audience fit, and confidentiality before delivering. + +## Writing Rules + +- Do not invent facts, timelines, metrics, or alignment. If something is uncertain, say so plainly. +- Prefer concrete nouns and verbs over abstract status language. "Shipped the billing retry fix" is better than "made progress on billing." +- Match the audience's depth. Executives usually need outcomes, risk, and asks; broader audiences need context and decisions; operators need status and action items. +- Keep action items explicit. If people need to do something, say what, by when, and who owns it when known. +- Use links or file references to authoritative sources when they exist. +- Remove sensitive details that the target audience does not need. + +## Source Prioritization + +Use sources in this order unless the user says otherwise: + +- User-provided bullets, notes, and drafts +- Workspace artifacts such as docs, tickets, changelogs, and meeting notes +- Connected systems or shared tools, if available and appropriate +- Prior internal language that sets style or precedent + +If the available material is thin, produce the best draft you can, clearly mark assumptions, and list the smallest missing facts needed to finalize it. + +## Deliverables + +- Deliver the message in the exact format the user requested when one is specified. +- If no format is specified, choose the closest matching reference and state the format briefly. +- When useful, provide both a polished version and a shorter variant for chat, email, or announcement channels. diff --git a/skills/.curated/internal-comms/agents/openai.yaml b/skills/.curated/internal-comms/agents/openai.yaml new file mode 100644 index 00000000..99efc30e --- /dev/null +++ b/skills/.curated/internal-comms/agents/openai.yaml @@ -0,0 +1,4 @@ +interface: + display_name: "Internal Comms" + short_description: "Draft internal updates and briefings" + default_prompt: "Use $internal-comms to draft or polish an internal update, leadership note, FAQ, or status report for the right audience and format." diff --git a/skills/.curated/internal-comms/references/3p-updates.md b/skills/.curated/internal-comms/references/3p-updates.md new file mode 100644 index 00000000..024120ad --- /dev/null +++ b/skills/.curated/internal-comms/references/3p-updates.md @@ -0,0 +1,34 @@ +# 3P Updates + +Use this format for weekly or sprint-scale team updates where the reader needs a fast picture of what happened, what is next, and what is blocked. + +## Gather First + +- Team or project name +- Reporting window +- The 2-5 most important shipped outcomes, milestones, or decisions +- The top next-step priorities for the next window +- The real blockers, risks, or dependencies + +## Format + +Keep the structure strict unless the user gives a house style: + +```text +Team: +Window: +Progress: <1-3 short sentences> +Plans: <1-3 short sentences> +Problems: <1-3 short sentences> +``` + +If the user's org normally adds a heading or emoji, mirror that convention. Otherwise keep it plain. + +## Writing Rules + +- Keep each section short enough to scan in under a minute. +- Lead with shipped outcomes, not effort. +- Use numbers when they clarify scope or impact. +- In `Plans`, name the highest-priority work only. +- In `Problems`, say what is blocked and what the unblock path is when known. +- Avoid vague status filler such as "continuing to make progress." diff --git a/skills/.curated/internal-comms/references/company-newsletter.md b/skills/.curated/internal-comms/references/company-newsletter.md new file mode 100644 index 00000000..c4d9d5f3 --- /dev/null +++ b/skills/.curated/internal-comms/references/company-newsletter.md @@ -0,0 +1,31 @@ +# Company Newsletter + +Use this format for broad internal roundups that summarize major developments across teams, leadership, launches, operations, or company-wide priorities. + +## Gather First + +- Broad-impact launches, milestones, and decisions +- Leadership updates or strategy changes +- Cross-functional progress that affects many teams +- Links to authoritative docs, announcements, dashboards, or recordings + +## Format + +Organize the newsletter into 3-5 short sections with flat bullets. Each bullet should usually be one sentence, occasionally two when context is necessary. + +Example section themes: + +- Company Announcements +- Product and Shipping Updates +- Go-to-Market and Customer Momentum +- Operations and Hiring +- Upcoming Dates or Decisions + +## Writing Rules + +- Prioritize items that matter to many employees. +- Group related updates so the newsletter feels curated rather than dumped. +- Put the highest-signal items near the top. +- Link to the source of truth when available. +- Use "we" voice only if it matches the company's style or the user draft already uses it. +- Cut narrow team-only updates unless they represent a major milestone. diff --git a/skills/.curated/internal-comms/references/faq-answers.md b/skills/.curated/internal-comms/references/faq-answers.md new file mode 100644 index 00000000..7c259cdf --- /dev/null +++ b/skills/.curated/internal-comms/references/faq-answers.md @@ -0,0 +1,26 @@ +# FAQ Answers + +Use this format when many people are asking similar questions and the goal is to reduce confusion with short, source-backed answers. + +## Gather First + +- Repeated or high-signal questions from threads, notes, docs, or user input +- The most authoritative available answers +- Links to official sources or owners + +## Format + +Use a simple repeated pattern: + +```text +Question: +Answer: +``` + +## Writing Rules + +- Write the question the way employees would actually ask it. +- Keep answers direct and practical. +- Base answers on official sources when possible. +- If information is incomplete, separate confirmed facts from open questions. +- Flag items that require an official owner or executive answer rather than guessing. diff --git a/skills/.curated/internal-comms/references/general-comms.md b/skills/.curated/internal-comms/references/general-comms.md new file mode 100644 index 00000000..187a2bce --- /dev/null +++ b/skills/.curated/internal-comms/references/general-comms.md @@ -0,0 +1,50 @@ +# General Internal Comms + +Use this reference for leadership notes, incident updates, launch announcements, project updates, change notices, or any internal message that does not fit the 3P, newsletter, or FAQ formats. + +## Decide The Shape + +Start by identifying: + +- Target audience +- Purpose of the message +- Desired action or takeaway +- Required tone +- Delivery channel + +## Default Structure + +When the user does not provide a house format, use this order: + +1. What changed or what is happening +2. Why it matters +3. What people should do next +4. Timing, owners, or next update +5. Where to learn more + +## Special Cases + +For incident updates: + +- Lead with current status +- State user or business impact plainly +- Summarize mitigation and current risk +- Include next update timing when known + +For leadership notes: + +- Lead with the decision or takeaway +- Add rationale second +- Keep asks explicit + +For launch announcements: + +- Lead with what is shipping and who it is for +- Include readiness, links, owners, and any rollout constraints + +## Writing Rules + +- Put the most important fact in the first two lines. +- Keep paragraphs short and headings literal. +- Prefer active voice. +- End with clear next steps instead of soft conclusions.