outside-message
/outside-message
Pilnuje tekstów, które trafiają poza firmę: komentarzy w cudzych repozytoriach, maili, wiadomości w czatach, notatek o wydaniu i zgłoszeń błędów, zanim zostaną wysłane.
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Pilnuje tekstów, które trafiają poza firmę: komentarzy w cudzych repozytoriach, maili, wiadomości w czatach, notatek o wydaniu i zgłoszeń błędów, zanim zostaną wysłane.
Oryginalny opis (EN)
Use before any text reaches a person outside the company: a comment on an issue or pull request of a repository the company does not own, an email, a chat message to another company, a release note, an enrollment reply, a bug report, a disclosure. Use it also before you open an ask that asks the operator to approve such text. Not for a message to the operator, to another agent, or inside the company's own organization.
Jak działa
- The exclusions
- The four steps
- Then the ask
- One batch, not one ask at a time
- What this skill does not cover
Podgląd SKILL.md
--- name: outside-message description: "Use before any text reaches a person outside the company: a comment on an issue or pull request of a repository the company does not own, an email, a chat message to another company, a release note, an enrollment reply, a bug report, a disclosure. Use it also before you open an ask that asks the operator to approve such text. Not for a message to the operator, to another agent, or inside the company's own organization." --- # A message to someone outside the company The operator approves every message that leaves the company, and four steps come before you ask. The rules below are the operator's own, from the answers that set them; this skill is where they are written down. ## The exclusions An exclusion exists only where the operator has stated it. Never infer one from the shape of a message. **A project the operator has excluded by name** goes out without approval. Only the operator's own answer names such a project, and your stream's brief is where that answer reaches you. With no such answer for the project in front of you, there is no exclusion. **A pull request to a project that has already enrolled**, with its description and its comments to that project's maintainers. The operator does not want to be asked for approval every time for an enrolled project, and ceremony around a pull request must not stop the work. The four steps still apply. The approval ask does not. The work does not wait for the pull request either: prepare and sign the changes locally, and send them when the work they belong to ends. What counts as enrolled is the enrolling project's own record, and its stream's brief says where that record is. Do not decide enrollment from a message's tone, or from a maintainer having replied to the company before. Everything else waits for the operator: a first contact with a project that has not enrolled, a bug report, a disclosure, and a reply to a maintainer who wrote first. Hold an extremely high bar. Optimise every upstream report, patch or public post for a human reader and for being received well, so each one builds the company's reputation rather than a reputation for low-quality or careless submissions. ## The four steps 1. **Research the audience.** Read the repository's contributing guide, its issue and pull-request templates, its code of conduct, and its last ten issues or pull requests. Read how the maintainers write to each other. Search for what has already been discussed about your subject; a question they answered last month, asked again, costs you the reader. 2. **Write for that audience, in their conventions.** Use their template where they have one, their terms, their level of detail. Run `skill://asd-ste100` and `skill://plain-words` over the text. Neither removes AI writing tells; where your session has a pass for those, run it as well. 3. **Follow their conventions in form as well as words.** A pull request on their repository uses their pull-request template. An issue uses their issue template. A thread reply matches the thread. 4. **A fresh reviewer reads it and cuts.** Dispatch a subagent that has not seen the drafting, give it the message and the research, and tell it to remove everything that is not needed to understand the core message. A reviewer that only approves has not done step 4. A subagent with no model of its own runs on yours. Where your session can give the reviewer a different model, do: a reader of the same model as the writer is the weaker check, though no measurement here separates the two. **Step 4 ends with a list of what it removed, and that list goes in the ask.** An instruction alone does not make the cut happen, so the list is what proves it did: three lines naming what came out, or the sentence "the reviewer removed nothing", which is itself an answer. **The text the operator approves is the text the reviewer cut, byte for byte.** Any edit after the cut, even one line of fact, sends the text back through step 1 and a new fresh review, because a sentence added after the cut reaches the operator unreviewed. The form of the text is not in this skill. Where the stream that owns the relationship keeps its own rules for writing to maintainers — in its project's `AGENTS.md`, in its skills, or in its brief — those rules decide how the message reads, and some of them are owned by people through that repository's code owners. Read them before you draft, and send a change to the form there rather than into this file. This skill covers when approval is needed and what comes before the ask. The project's own rules cover how the text reads. ## Then the ask **Put the full message text in the ask itself.** Not a link to a document holding it, not a summary of it, not "the draft is at …". The operator has to open another document to read the message in almost every one of these asks, and cannot judge the message from the ask. An ask for an outside message has, in this order: - who the reader is, and one line on what they already know about this; - **the message, in full, as it would be sent**; - **what the reviewer removed in step 4**, in three lines or fewer, or "the reviewer removed nothing"; - what changes if the answer is no. Link the research, not the message. An ask with no removal line has not had step 4, whatever it says. ## One batch, not one ask at a time An upstream bug report, patch or public post that needs the operator's approval goes into one review batch, never a per-message "can I send this" ask. Write its entry — what it is and how serious; who receives it and what they do; the exact text or patch; its evidence; a non-author reviewer's APPROVE under your stream's reviewer-model rule; what the operator decides; its owner — into the batch, add it under the batch's Waiting list, and tell the batch owner. Your stream's brief names the batch and its owner. Where your stream's brief names no batch, ask the operator for one, or hold the entry until there is a batch; a missing batch is not a reason to send a per-message ask. ## What this skill does not cover - Text written in a person's own name, which that person signs off. - A message to another agent or to the operator: write it plainly and send it; no approval step. - Posting a release the pipeline publishes from approved template text: the template was approved once; the release needs no new ask unless its text changes.
Wersje
W bazie nie ma innych skilli o nazwie outside-message.
Migawka bazy z 13.11.2026 · wersja paczki 0cf2aa92ebd9 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100planr-share
Przygotowuje szkic wiadomości na czat ze statusem, notatką sprintu lub informacjami o wydaniu, do zatwierdzenia przed wysłaniem.