@assuredloop/orca-bot-kit 0.1.0 → 0.3.0

package/skills/obk-writing/LICENSES.md

@@ -0,0 +1,272 @@
+<!-- The licences of the sources this skill was consolidated from. They travel
+     with the skill directory because the licences require it of anyone who
+     distributes the material. NOTICE.md says what was taken from each source;
+     this file carries the permission notices themselves. -->
+
+# Licences of the sources
+
+`obk-writing` consolidates material from the sources named in
+[NOTICE.md](NOTICE.md). Their licences are reproduced below in full.
+
+## MIT
+
+The MIT permission notice below applies to the work of each of these copyright
+holders, and each notice is reproduced with it:
+
+- **Cursor `plugins`, the pstack plugin**, Copyright (c) 2026 Lauren Tan
+  (`cursor_plugins/pstack/LICENSE`)
+- **`citypaul/.dotfiles`, the technical-writing skill, whose nested licence
+  governs its directory over the repository root's**, Copyright (c) 2025 Adam Bulmer
+  (`citypaul_.dotfiles/claude/.claude/skills/technical-writing/LICENSE`)
+- **`citypaul/.dotfiles`, for the double-check skill, under the repository
+  root**, Copyright (c) 2024 Paul Hammond
+  (`citypaul_.dotfiles/LICENSE`)
+- **`addyosmani/agent-skills`**, Copyright (c) 2025 Addy Osmani
+  (`addyosmani_agent-skills/LICENSE`)
+- **`mattpocock/skills`**, Copyright (c) 2026 Matt Pocock
+  (`mattpocock_skills/LICENSE`)
+- **`garrytan/gstack`**, Copyright (c) 2026 Garry Tan
+  (`garrytan_gstack/LICENSE`)
+
+Each licence file was read at the path given above.
+
+```
+MIT License
+
+Copyright (c) 2026 Lauren Tan
+Copyright (c) 2025 Adam Bulmer
+Copyright (c) 2024 Paul Hammond
+Copyright (c) 2025 Addy Osmani
+Copyright (c) 2026 Matt Pocock
+Copyright (c) 2026 Garry Tan
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```
+
+## Apache License 2.0
+
+`anthropics/skills`' `internal-comms` skill is licensed under the Apache
+License, Version 2.0, in its own `LICENSE.txt`, "Copyright 2026 Anthropic,
+PBC." Section 4(a) requires that recipients of the work or of a derivative work
+be given a copy of the licence, so it is reproduced in full below.
+
+```
+
+                                 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 2026 Anthropic, PBC.
+
+   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.
+```

package/skills/obk-writing/NOTICE.md

@@ -0,0 +1,161 @@
+<!-- Attribution for the sources this skill was built from. Kept out of
+     SKILL.md so it is not read into context on every use; it travels with
+     the skill directory, which is what the licences require. -->
+
+# Sources and licences
+
+The permission notices these licences require are in
+[LICENSES.md](LICENSES.md), beside this file.
+
+The skill `obk-writing` was consolidated for this kit from these, with thanks.
+Each licence below was read from the file named beside it.
+
+- **Cursor `plugins`, `pstack/skills/technical-writing`**: MIT,
+  `cursor_plugins/pstack/LICENSE`, "Copyright (c) 2026 Lauren Tan". The
+  sentence-level core of this skill. Its three rules above the layers: cut
+  every word that does no work, use the short everyday word, and when a rule
+  makes a sentence worse fix it another way or leave it alone, because a
+  sentence that follows every rule and sounds machine-written has failed. Its
+  four layers, generalised here from documentation to writing in general:
+  choosing what kind of piece this is and not mixing kinds in one piece;
+  addressing the reader directly, saying who does what,
+  writing instructions as instructions with the condition in front, common case
+  before exceptions; loading one instruction or one thought per sentence and
+  splitting the one that carries two; and leaving no sentence open to two
+  readings, which brings "only" beside the word it changes, every "it" pointing
+  at one thing, broken-up noun stacks, the small words that make a sentence
+  parse one way, saying which parts an "and" joins, preferring a full stop, and
+  skipping idioms and metaphors for the sake of whoever reads in a second
+  language. Also its rhythm section, that a piece can obey every rule and still
+  read machine-written when every sentence is clipped to the same length; its
+  heading rule, that a heading carries the point rather than the topic; its
+  list rules; and the instruction to call each thing by one name everywhere.
+- **Cursor `plugins`, `pstack/skills/unslop`**: same licence. Two of its rules
+  are load-bearing here. Say what it does rather than how it feels, with its
+  test: ask what the sentence tells the reader to do or know, restate it as a
+  fact, a number or an instruction, and cut it if you cannot; and if the
+  sentence could appear unchanged in something about a different subject, it
+  says nothing about this one. And name the source or delete, against "experts
+  believe" and "studies show". Its active-voice, adverb and synonym-cycling
+  rules are here too, and its over-compression rule is why this skill says to
+  shorten by cutting rather than by squeezing prose into shorthand. Its
+  catalogue of banned words is deliberately not carried: the research pack
+  records that a ban-list pulls the banned thing into context, so the rules
+  named above are kept in their positive form, not every rule in the catalogue,
+  and the word list is left where it is, as something to review against rather
+  than to load.
+- **`citypaul/.dotfiles`, `claude/.claude/skills/technical-writing`**: MIT,
+  that skill's own nested `LICENSE`, "Copyright (c) 2025 Adam Bulmer", which
+  governs its directory rather than the repository root's MIT licence in
+  Paul Hammond's name. This is the page-level and claim-level half. Reader
+  first, leading with the payoff and organising around the reader's next action
+  rather than the system's internal structure. Scannable, with headings that
+  summarise a section's payoff. Selective rather than compressed: the way to
+  keep something short is to cut what does not change the reader's next step.
+  Its material-claims rule, which is where this skill's fact-checking comes
+  from: no capability claim without something a reader can check, counts and
+  versions rot so date them or generate them, honest limits are content rather
+  than confession and belong where the reader makes the decision, an empty
+  state must not read like success, and a document that describes a system is a
+  claim about that system, so verify against the source rather than memory and
+  update the description in the same change. Its exact-strings rule, since
+  people copy what you wrote. Its document shapes, including the proposal that
+  leads with the decision requested. And from `resources/formatting.md`, bold
+  for the one phrase a skimmer must not miss, and a numbered list claiming that
+  order matters.
+- **`mattpocock/skills`, `skills/in-progress/writing-shape`**: MIT,
+  `mattpocock_skills/LICENSE`, "Copyright (c) 2026 Matt Pocock". The grounding
+  idea, which nothing else in the sources has: every concept a block leans on
+  was either something the reader walked in with or something an earlier block
+  introduced, the unit is the concept rather than the word for it, and the
+  lever is what you make a prerequisite against what you ground inside the
+  piece, since demanding too much shuts readers out and grounding too much
+  drowns the opening. Its format arguments are also taken: prose carries an
+  argument and lists carry parallel items, a table where the same shape repeats
+  three times or more, and quoting where the original wording is the point.
+- **`anthropics/skills`, `skills/internal-comms`**: Apache 2.0, that skill's
+  own `LICENSE.txt`, "Copyright 2026 Anthropic, PBC." The only source here that
+  is explicitly about audience, platform and register for non-engineering
+  writing. Its opening protocol is this skill's first section: ask about the
+  audience, understand the purpose, clarify the tone, confirm the format, then
+  be clear and concise, use active voice and put the most important information
+  first. Its update format contributes the point that the place a piece will be
+  read is a constraint on the writing rather than a detail: something meant to
+  be read in under a minute by people with some but not much context is a
+  different piece from the same facts written to be landed on.
+- **`garrytan/gstack`, `document-generate/SKILL.md`**: MIT,
+  `garrytan_gstack/LICENSE`, "Copyright (c) 2026 Garry Tan". Its voice section:
+  lead with the point, be concrete, name the real thing and the real number.
+  Its rule to gloss a piece of jargon on first use even where the user
+  introduced the term.
+- **`addyosmani/agent-skills`, `skills/doubt-driven-development`** and
+  **`citypaul/.dotfiles`, `claude/.claude/skills/double-check`**: MIT,
+  `addyosmani_agent-skills/LICENSE` ("Copyright (c) 2025 Addy Osmani") and
+  `citypaul_.dotfiles/LICENSE` ("Copyright (c) 2024 Paul Hammond"). The reader
+  test at the end comes from these two rather than from any writing skill: when
+  it is not worth doing; hand over the artifact without your reasoning, because
+  handing over your conclusion gets you agreement with your conclusion; start
+  the reader cold; ask them to find what is wrong; read what comes back rather
+  than deferring, since a fresh reader can be wrong for want of context; and
+  stop when a pass finds only small or known things, bounded at about three
+  passes, with a piece still failing then reported as not ready.
+
+**Left out on a licence.** `anthropics/skills`' `doc-coauthoring` has the best
+statement of reader testing in the corpus, but its directory holds no licence
+file and `anthropics/skills` has none at its root, so nothing is taken from it.
+An earlier version of this skill had nevertheless followed its three reader
+questions and its closing review item for item; the re-validation (#155)
+rebuilt the reader test from the two MIT sources above instead, and dropped
+those parts.
+
+Also left out on purpose: the specific documentation framework the pstack
+skill and the citypaul skill both build on, named and cited in both. Its four
+kinds of document are useful and are carried here in ordinary words, with a
+fifth for a piece written to be decided on, but the kit does not adopt a named
+framework or its file layout, because PRD 7.1 leaves the user free in how they
+keep documents. The reference lists, style-linting tooling and README-specific
+material in the citypaul resources are also out: they are for a documentation
+site rather than for writing in general.
+
+PRD 7.1 decides what this skill is for, and the owner agreed to it in those
+words on 2026-09-20 at 19:45:42: "Write for an audience, a platform and a tone,
+and check the key facts", following the same rules as the other skills,
+"techniques only, no process, deeply written".
+
+One note on this skill's own prose. It carries the rule that a sentence
+carrying a second clause on a dash is usually two sentences, so it is written
+without em dashes throughout. A skill that broke its own punctuation rule in
+its own text would be teaching by counter-example, which happened once already
+in this kit and was caught in review.
+
+## What an acceptance run changed
+
+The skill was run by a bot that had not seen it written, on a real piece of
+internal communication: a change of expenses system for two hundred mostly
+non-technical staff, many part-time, plus a second version for team leads.
+Seven things in it come from what that found.
+
+- One heading was actively steering the writing wrong. "Say what it does, not
+  how it feels" is about empty sentences, but it reads as a rule against
+  addressing how a reader feels, and it pushed the run away from the brief's
+  sharpest constraint. The heading now says what the section is about, and the
+  section says that naming what a reader feels is a fact about them.
+- Nothing covered the facts a writer does not have and must not invent. Marking
+  the hole where it belongs and collecting the questions is now in the skill,
+  along with the point that a piece with its holes marked is a legitimate thing
+  to hand back.
+- Checking assumed the writer could reach the thing being described. Where the
+  only source is the person who asked, that is now said, with what can still be
+  checked: the dates, the arithmetic, and whether the piece contradicts itself.
+- The fresh-reader test had no stopping rule that terminates while facts are
+  still missing, and did not say who counts as a fresh reader.
+- Nothing covered two versions of one thing for two audiences, or the
+  asymmetry between them, which is where that run found its sharpest problem.
+- "Keep the small words" and "keep it short" were in tension with nothing
+  saying which wins.
+- Ordering by importance put three dates on the page out of sequence. A piece
+  that turns on dates or steps needs both orders.
+
+The part of the skill that run rated highest was the fresh-reader test, which
+found that for a large share of the staff the deadline in the first draft fell
+on a day they do not work.