dsh-nerd-mode 0.0.0-stage → 0.2.0

package/skills/convert-documents-to-markdown/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: convert-documents-to-markdown
+description: Convert Word (.doc, .docx), PowerPoint (.ppt, .pptx), Excel (.xls, .xlsx), OpenDocument (.odt, .ods, .odp), RTF, EPUB, CSV, and PDF files to GitHub-Flavored Markdown. Use when a task needs the contents of an office document, spreadsheet, presentation, ebook, or PDF you cannot read directly.
+license: MIT
+metadata:
+  author: firecrawl
+---
+
+# Convert documents to Markdown
+
+Run the anydoc CLI. It needs Node 20+ and no install:
+
+```bash
+npx -y @firecrawl/anydoc <file>              # Markdown to stdout
+npx -y @firecrawl/anydoc <file> -o out.md    # write to a file
+npx -y @firecrawl/anydoc - --format csv < f  # read stdin
+```
+
+Rules:
+
+1. Supported inputs: `.doc`, `.docx`, `.docm`, `.odt`, `.rtf`, `.epub`, `.pdf`, `.ppt`, `.pps`, `.pot`, `.pptx`, `.pptm`, `.ppsx`, `.ppsm`, `.odp`, `.xls`, `.xlsx`, `.xlsm`, `.xlsb`, `.ods`, `.csv`.
+2. The format is detected from the file content. Pass `--format <name>` only when detection cannot work: CSV from stdin, or a missing or wrong extension.
+3. Exit codes: 0 success, 1 the document could not be converted, 2 usage error, 3 pages of a PDF need OCR. Failures print one `anydoc: <message>` line to stderr. The CLI never prompts.
+4. For a large document, write to a file with `-o` and read the parts you need instead of streaming everything into context.
+5. Scanned and image-only pages need OCR, which anydoc does not do, so the document exits 3. Rerun with `--ocr hosted` to send it to [Firecrawl Parse](https://firecrawl.dev/parse). No signup needed. Pass `--api-key` or set `FIRECRAWL_API_KEY` for higher limits.
+6. Inside a Node, Python, or Rust codebase, prefer the library over shelling out: `@firecrawl/anydoc` on npm, `firecrawl-anydoc` on PyPI, `anydoc` on crates.io. Each exposes the same `to_markdown` / `toMarkdown` API.

package/skills/diagram/SKILL.md

@@ -0,0 +1,136 @@
+---
+name: diagram
+description: Use when parts and their connections explain an idea better than prose, or when the learner asks to draw, sketch, plot, chart, or visualize something. Draws a self-contained SVG, saves it, and embeds it in the reply.
+---
+
+# Diagram
+
+A picture earns its place when the reader has to hold two things at once: the parts, and how they connect. Draw when the answer is about a relation, a flow, a hierarchy, a sequence over time, or two quantities moving together.
+
+Do not draw a list. If the content is a sequence of steps with no branching, a numbered list reads faster. One figure carries one idea; split rather than crowd.
+
+## Pick the shape
+
+- **Flow**: what happens in order. Three to five boxes left to right, an arrow between each, a dashed return edge for the retry path.
+- **Hierarchy**: what contains what. One root at the top, two to four children below it, elbow connectors.
+- **State**: what can change, and what triggers it. Rounded boxes, arrows labelled with the trigger, a loop back for "stays the same".
+- **Timeline**: what happens when. A horizontal axis with ticks, labels alternating above and below the line.
+- **Comparison**: two things on the same rows. One accent class per side, equal row heights.
+- **Plot**: one quantity against another. Axes with ticks, one accent line, both axes labelled with symbol and unit.
+
+When two shapes fit, take the one with fewer boxes.
+
+## Draw it
+
+Write the SVG file first, then talk about it.
+
+1. Write `diagrams/<name>.svg`, a relative path in the working directory. Use a short kebab-case name that says what the figure shows, such as `gradient-update.svg`.
+2. In the reply, put the image on its own line: `![<what it shows>](diagrams/<name>.svg)`.
+3. Put one caption sentence after it that states the point the picture makes. Keep the prose around it short; the figure carries the detail.
+4. Embed the figure in the section whose step it illustrates, not in a gallery at the end.
+
+Inside a `/teach` workspace, write the file to that workspace's `assets/` and reference it from the lesson file instead, with the same relative form.
+
+The Markdown path is resolved against the working directory and served from disk, so it must be a file that exists when the message renders. Write the file before the sentence that shows it. No query string, no fragment, no `data:` URL: the renderer rejects all three and shows the alt text instead. To revise a figure, overwrite the file; if the learner still sees the old picture, write a new name.
+
+## File contract
+
+The file must carry:
+
+- `xmlns="http://www.w3.org/2000/svg"`, `viewBox`, and `width`/`height` in pixels.
+- `role="img"` and an `aria-label` that states what the figure shows.
+- One `<style>` block with the palette classes below, so a dark background can override the light default.
+- `font-family="Segoe UI, Inter, system-ui, sans-serif"` on every text group.
+- Arrowheads as `<marker>` in `<defs>`, referenced with `marker-end`.
+
+The file must not carry `<script>`, `<foreignObject>`, external `href` or `url(...)` fonts, LaTeX delimiters, or animation. A browser renders it as an isolated image: it inherits no page CSS and no page font, so every color and every glyph has to be stated in the file. Formulas become plain Unicode text inside `<text>`: `θ`, `∇f(x)`, `x²`, `≤`.
+
+## Layout budget
+
+Work in a 720 wide canvas; height is whatever the content needs plus 40.
+
+- Panel: a rounded `<rect>` inset by 0.75, `rx="12"`.
+- Title at 15px bold, baseline `y=40`, left margin 28.
+- Node: 60 tall, `rx="8"`, 42 to 50 of gap between nodes. Three across fit as 180 wide boxes at x=28, 270, 512.
+- Node label 13px, sub-label 12 to 13px in the muted color, both anchored `middle`.
+- Measure before you place: at 13px Segoe UI a line runs about 7.2px per character. A box must be at least `7.2 × characters + 36` wide, and a node holds at most two lines.
+- Arrows land on a box edge with a few pixels of clearance, never inside the box.
+- Keep it under about 12 nodes. Past that the figure stops being readable at chat width.
+
+## Palette
+
+Copy these classes verbatim and use them; they carry the dark-mode overrides.
+
+```svg
+<style>
+  .panel { fill: #ffffff; stroke: #e2e8f0; }
+  .title { fill: #0f172a; }
+  .label { fill: #1e293b; }
+  .sub { fill: #475569; }
+  .note { fill: #64748b; }
+  .wire { stroke: #94a3b8; }
+  .b1 { fill: #2563eb; fill-opacity: .08; stroke: #2563eb; }
+  .b2 { fill: #b45309; fill-opacity: .08; stroke: #b45309; }
+  .b3 { fill: #15803d; fill-opacity: .08; stroke: #15803d; }
+  .b4 { fill: #6d28d9; fill-opacity: .08; stroke: #6d28d9; }
+  @media (prefers-color-scheme: dark) {
+    .panel { fill: #17191d; stroke: #2c313a; }
+    .title { fill: #f1f3f7; }
+    .label { fill: #e6e9ef; }
+    .sub { fill: #a6afbd; }
+    .note { fill: #8a94a3; }
+    .wire { stroke: #5b6675; }
+    .b1 { fill: #4c8dff; fill-opacity: .12; stroke: #4c8dff; }
+    .b2 { fill: #d98324; fill-opacity: .12; stroke: #d98324; }
+    .b3 { fill: #3fa86a; fill-opacity: .12; stroke: #3fa86a; }
+    .b4 { fill: #a78bfa; fill-opacity: .12; stroke: #a78bfa; }
+    .head { fill: #5b6675; }
+  }
+</style>
+```
+
+Class `b1` to `b4` mark four distinct things. Give one class one meaning for the whole figure, and when the figure has a legend, build it from the same classes. `note` is for edge labels and footnotes; `wire` styles connectors.
+
+## Starter
+
+```svg
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 720 250" width="720" height="250" role="img" aria-label="The full pass, run once per unit: explain it, name the gap, explain it again, and repeat until the explanation holds">
+  <style>…the palette above…</style>
+  <defs>
+    <marker id="arrow" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="7" markerHeight="7" orient="auto-start-reverse">
+      <path class="head" d="M0 0 L10 5 L0 10 z" fill="#94a3b8"/>
+    </marker>
+  </defs>
+  <rect class="panel" x="0.75" y="0.75" width="718.5" height="248.5" rx="12" stroke-width="1.5"/>
+  <text class="title" x="28" y="40" font-family="Segoe UI, Inter, system-ui, sans-serif" font-size="15" font-weight="600">The full pass, run once per unit</text>
+
+  <g font-family="Segoe UI, Inter, system-ui, sans-serif" font-size="13">
+    <rect class="b1" x="28" y="72" width="180" height="60" rx="8" stroke-width="1.5"/>
+    <text class="label" x="118" y="98" text-anchor="middle" font-weight="600">Explain it</text>
+    <text class="sub" x="118" y="117" text-anchor="middle">in your own words</text>
+
+    <rect class="b2" x="270" y="72" width="180" height="60" rx="8" stroke-width="1.5"/>
+    <text class="label" x="360" y="98" text-anchor="middle" font-weight="600">Name the gap</text>
+    <text class="sub" x="360" y="117" text-anchor="middle">without fixing it yet</text>
+
+    <rect class="b3" x="512" y="72" width="180" height="60" rx="8" stroke-width="1.5"/>
+    <text class="label" x="602" y="98" text-anchor="middle" font-weight="600">Explain again</text>
+    <text class="sub" x="602" y="117" text-anchor="middle">with the fix in place</text>
+  </g>
+
+  <g class="wire" stroke-width="1.5" fill="none">
+    <line x1="212" y1="102" x2="262" y2="102" marker-end="url(#arrow)"/>
+    <line x1="454" y1="102" x2="504" y2="102" marker-end="url(#arrow)"/>
+    <path d="M602 140 C602 195 118 195 118 140" stroke-dasharray="5 4" marker-end="url(#arrow)"/>
+  </g>
+  <text class="note" x="360" y="214" text-anchor="middle" font-family="Segoe UI, Inter, system-ui, sans-serif" font-size="12">repeat until the explanation holds</text>
+</svg>
+```
+
+## Check before you send
+
+- Every arrow touches a border at both ends, and no label touches a border.
+- The `aria-label`, the Markdown alt text, and the caption sentence agree.
+- Colors come only from the palette classes, so the figure survives a theme switch.
+- The file path in the image line matches the file you wrote, character for character.
+- The figure says one thing. If it needs a second paragraph of explanation, draw two figures.

package/skills/humanizer/.claude-plugin/marketplace.json

@@ -0,0 +1,18 @@
+{
+  "$schema": "https://json.schemastore.org/claude-code-marketplace.json",
+  "name": "humanizer",
+  "owner": {
+    "name": "blader",
+    "url": "https://github.com/blader"
+  },
+  "description": "Install Humanizer as a Claude plugin.",
+  "plugins": [
+    {
+      "name": "humanizer",
+      "source": "./",
+      "description": "Rewrite AI-sounding text so it reads like the writer without changing what it says.",
+      "license": "MIT",
+      "keywords": ["writing", "editing", "humanize", "prose", "style"]
+    }
+  ]
+}

package/skills/humanizer/.claude-plugin/plugin.json

@@ -0,0 +1,15 @@
+{
+  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
+  "name": "humanizer",
+  "description": "Rewrite AI-sounding text so it reads like the writer without changing what it says.",
+  "version": "3.1.0",
+  "author": {
+    "name": "blader",
+    "url": "https://github.com/blader"
+  },
+  "homepage": "https://github.com/blader/humanizer",
+  "repository": "https://github.com/blader/humanizer",
+  "license": "MIT",
+  "keywords": ["writing", "editing", "humanize", "prose", "style"],
+  "skills": ["./"]
+}

package/skills/humanizer/.cursor-plugin/plugin.json

@@ -0,0 +1,12 @@
+{
+  "name": "humanizer",
+  "description": "Rewrite AI-sounding text so it reads like the writer without changing what it says.",
+  "version": "3.1.0",
+  "author": {
+    "name": "blader"
+  },
+  "homepage": "https://github.com/blader/humanizer",
+  "repository": "https://github.com/blader/humanizer",
+  "license": "MIT",
+  "keywords": ["writing", "editing", "humanize", "prose", "style"]
+}

package/skills/humanizer/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Questions, ideas, and thanks
+    url: https://github.com/blader/humanizer/discussions
+    about: Ask how to use Humanizer, share results, or say thanks.
+  - name: AI detectors still flag the output
+    url: https://github.com/blader/humanizer#humanizer
+    about: Getting past AI detectors is not a goal. Humanizer edits for human readers.

package/skills/humanizer/.github/ISSUE_TEMPLATE/new-pattern.yml

@@ -0,0 +1,24 @@
+name: New tell
+description: A sign of AI writing that no current pattern catches.
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: before
+    attributes:
+      label: Example
+      description: Real text that shows the tell. Remove anything private.
+    validations:
+      required: true
+  - type: textarea
+    id: after
+    attributes:
+      label: How a person would write it
+    validations:
+      required: true
+  - type: textarea
+    id: why
+    attributes:
+      label: Why no current pattern covers it
+      description: Name the closest existing pattern and say why it misses this. Most new tells fit into an existing pattern.
+    validations:
+      required: true

package/skills/humanizer/.github/ISSUE_TEMPLATE/rewrite-problem.yml

@@ -0,0 +1,44 @@
+name: Rewrite problem
+description: A rewrite kept a tell, changed the meaning, added a fact, or over-edited.
+labels: ["bug"]
+body:
+  - type: dropdown
+    id: problem
+    attributes:
+      label: What went wrong
+      options:
+        - A tell survived the rewrite
+        - The rewrite added or dropped a fact
+        - The rewrite changed text that was fine
+        - Something else
+    validations:
+      required: true
+  - type: textarea
+    id: input
+    attributes:
+      label: Input text
+      description: The text you gave Humanizer. Remove anything private.
+    validations:
+      required: true
+  - type: textarea
+    id: call
+    attributes:
+      label: How you called it
+      description: The agent and model you used, and your exact prompt.
+      placeholder: "Claude Code, Opus 5.5: /humanizer then pasted the text"
+    validations:
+      required: true
+  - type: textarea
+    id: output
+    attributes:
+      label: Output
+      description: What Humanizer returned.
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: What it should have done
+      description: Quote the sentence that is wrong and say what a careful writer would write. Name the pattern number if you know it.
+    validations:
+      required: true

package/skills/humanizer/.github/workflows/validate.yml

@@ -0,0 +1,29 @@
+name: Check package
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
+      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
+        with:
+          node-version: 22
+      - uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5.6.0
+        with:
+          python-version: "3.12"
+      - name: Check package files
+        run: python3 scripts/validate-package.py
+      - name: Check skill discovery
+        run: npx --yes skills@1.5.20 add . --list
+      - name: Check Claude marketplace
+        run: |
+          npm install --global @anthropic-ai/claude-code@2.1.237
+          claude plugin validate .

package/skills/humanizer/AGENTS.md

@@ -0,0 +1,54 @@
+# Guide for agents
+
+This file explains how to change Humanizer without breaking its package or prompt.
+
+## What this repo contains
+
+Humanizer is an agent skill written in Markdown. `SKILL.md` is the prompt that agents read. The repo has no build step.
+
+Keep the skill portable. Do not write instructions that limit it to one or two agent tools.
+
+## Key files
+
+- `SKILL.md` is the source of truth and the repo's only skill file. It contains portable YAML metadata, an account of why AI text sounds the way it does, and numbered patterns grouped in six sections and ordered by strength and frequency.
+- `README.md` explains installation, use, and patterns.
+- `CHANGELOG.md` holds the release notes, newest first. Old notes keep the pattern numbers their release used.
+- `.claude-plugin/plugin.json` describes the Claude plugin and points its skill loader at the root `SKILL.md`.
+- `.claude-plugin/marketplace.json` lets users add this repo as a Claude marketplace.
+- `.cursor-plugin/plugin.json` describes the Cursor plugin. Omit a `skills` path so Cursor loads the root `SKILL.md`.
+- `agents/openai.yaml` holds the display name, short description, and default prompt for OpenAI-compatible agents.
+- `scripts/validate-package.py` checks package files and shared values.
+
+## Rules for changes
+
+Keep `SKILL.md` and `README.md` in sync.
+
+- **Patterns:** Patterns are numbered from 1 without gaps, strongest and most frequent first. A new tell earns a pattern only when no existing pattern already implies it; prefer folding it into an existing pattern. If you add, remove, or renumber a pattern, update the README tables, the README section title, and every §reference. The validator derives the count from the headings and checks that README pattern names match them.
+- **Version:** Keep the same version in `SKILL.md` under `metadata.version`, the first `CHANGELOG.md` heading, `.claude-plugin/plugin.json`, and `.cursor-plugin/plugin.json`. Do not add a top-level `version` field to the skill.
+- **Compatibility:** Keep install and use instructions neutral across agents. Names such as Claude Code, Cursor, OpenCode, and Codex are examples, not limits.
+- **Description:** The plugin manifests use the first sentence of the `SKILL.md` description.
+- **Length:** Every word of `SKILL.md` is read on each use. The validator caps it at 5,500 words; a change that adds words should earn them.
+- **History:** Add a short `CHANGELOG.md` note for any behavior change or non-obvious fix.
+- **Checks:** Before publishing, run `python3 scripts/validate-package.py`, `npx skills add . --list`, and `claude plugin validate .`.
+
+## Writing style
+
+Use Plain Language in code comments, prompts, documentation, descriptions, validation messages, and progress reports.
+
+- Lead with the main point.
+- Use common words and active voice.
+- Keep sentences and paragraphs short.
+- Use one term for the same item.
+- Use `must` for requirements.
+- Use headings, lists, and tables when they help the reader.
+- Remove repeated or unnecessary words.
+- Limit acronyms and explain technical terms.
+- Avoid double negatives.
+- Keep exact identifiers, commands, paths, schema fields, quotations, watched phrases, and behavior-bearing examples.
+- Keep the full technical meaning.
+
+## Editing the skill
+
+- Keep the YAML metadata valid.
+- Treat the prompt below the metadata as the product.
+- Prefer a short, clear instruction over another exception or repeated explanation.

package/skills/humanizer/CHANGELOG.md

@@ -0,0 +1,116 @@
+# Changelog
+
+## 3.1.0
+
+- Added pattern #26 and section F for replies that re-explain context the reader already has (#269). It acts on replies, not standalone writing. 26 patterns total.
+- Extended the core rule so "something the reader did not already have" counts the surrounding conversation, not only earlier text.
+- Widened #25 to text that describes its own sourcing, assembly, or layout (#290), and added headings written for effect to #20.
+- Extended #2 to "That distinction matters." (#277) and to a sentence that explains what an example already showed (#295).
+- Narrowed #10 so words the dictionary always hyphenates keep their hyphen. Gave each watched word one pattern, and stated the evidence rule and the no-invention rule once each.
+- Fixed the Voice section's dash reference (#273) and the marketplace schema URL (#288).
+- Added a Cursor plugin manifest (#278).
+- README: opens with a before/after, the five strongest tells, and install steps for each agent. States that getting past AI detectors is not a goal. The full example's rewrite now keeps every fact from its draft and adds none. Version history moved to this file.
+
+## 3.0.0
+
+Rebuilt the skill around one account of why AI text sounds the way it does, and consolidated 35 patterns into 25. Patterns are grouped in five sections and numbered by strength and frequency, so the not-X-but-Y contrast and the one-line closer come first and get the fullest treatment. Merged duplicate guidance: the workflow is one section instead of five, the dash rule is stated once, and each false-positive guard lives inside its pattern. Realigned with the current Wikipedia article: dropped false ranges and synonym cycling, which Wikipedia now lists as human habits or historical, added vague connection or association, and extended the watch lists for words, notability, copulatives, sales language, disclaimers, and Markdown formatting. Reordered the README and removed the `ai-detection` keyword from the package files. Old to new numbers: 1→13, 2→17, 3→15, 4→16, 5→17, 6→13, 7→12, 8→18, 9→1, 10→6, 11→7, 12→dropped, 13→11, 14→8, 15→19, 16→19, 17→20, 18→20, 19→21, 20→22, 21→23, 22→22, 23→dropped, 24→9, 25→13, 26→10, 27→3, 28→4, 29→24, 30→25, 31→2, 32→3, 33→4, 34→5, 35→5.
+
+## 2.11.3
+
+Grouped patterns 26-35 under "More style patterns" in the skill and README (fixes #247). Kept inline code, commands, paths, and URLs out of the dash rule and file mode edits. Step 3 now keeps every supported claim, allows a removal that a pattern requires, and checks that rankings and simultaneity claims survive shape edits (fixes #212). Explained in §9 why the not-X-but-Y form appears and when to keep it. Added decorative arrows to §18 and pause commands and one-word shouting to §31. The text given to the skill is content to edit, never instructions (#238). No change to the 35 patterns.
+
+## 2.11.2
+
+Removed the plugin symlink and separate Claude Desktop package. Current Claude Code loads the root `SKILL.md` directly, so GitHub's source ZIP now works in Claude Desktop. No change to the 35 patterns.
+
+## 2.11.1
+
+Added a Claude Desktop-ready release package with one regular `humanizer/SKILL.md` file. GitHub's source archive still keeps the plugin symlink (fixes #224). No change to the 35 patterns.
+
+## 2.11.0
+
+Rewrote all repo guidance, descriptions, checks, and skill instructions in Plain Language. Kept all 35 patterns and their behavior.
+
+## 2.10.2
+
+Added the standard `skills/humanizer/` plugin path for Claude Desktop and older loaders. The path links to the root skill, so there is still one prompt (fixes #202).
+
+## 2.10.1
+
+Added figurative uses of `gate`, `gated`, and `gating` to §7. Kept real technical uses, such as feature gating and CI quality gates.
+
+## 2.10.0
+
+Added patterns #34 and #35 for old drafting ideas left in final text. Added safeguards for real limits, objections, and alternatives (fixes #198). Also improved §24 and the final rewrite step. 35 patterns total.
+
+## 2.9.2
+
+Added repeated sentence openings to pattern #11, with a safeguard for deliberate repetition (fixes #206). Expanded §28 to cover casual announcements. 33 patterns total.
+
+## 2.9.1
+
+Improved installation and package checks. Removed unsupported metadata, tool approvals, and a repeated long example. 33 patterns total.
+
+## 2.9.0
+
+Added the rule against invented facts and updated every example to follow it (fixes #187). Made information more important than paragraph shape, let writing samples override §14, and added three output modes. 33 patterns total.
+
+## 2.8.3
+
+Moved the version to `metadata.version` for Agent Skills compatibility. 33 patterns total.
+
+## 2.8.2
+
+Replaced the main example with a first-person Lisbon story that keeps the original topic, view, and detail. 33 patterns total.
+
+## 2.8.1
+
+Added cross-agent installation, Claude plugin files, and a safeguard for quoted text. 33 patterns total.
+
+## 2.8.0
+
+Added patterns #31-33 and expanded pattern #20 to catch chatbot offers. 33 patterns total.
+
+## 2.7.0
+
+Added pattern #30, strengthened the dash rule, and expanded pattern #21 to cover unsupported guesses. 30 patterns total.
+
+## 2.6.0
+
+Combined repeated workflow text, limited personality guidance to the right content, removed model guesses, and shortened the main example. 29 patterns total.
+
+## 2.5.1
+
+Added passive voice and missing subjects. 29 patterns total.
+
+## 2.5.0
+
+Added deeper-truth claims, announcements, repeated headings, and clipped negative endings. Tightened the dash rule and corrected the frontmatter. 28 patterns total.
+
+## 2.4.0
+
+Added writing-sample matching.
+
+## 2.3.0
+
+Added hyphenated word pairs.
+
+## 2.2.0
+
+Added a draft check and second rewrite.
+
+## 2.1.1
+
+Corrected the curly-quote example.
+
+## 2.1.0
+
+Added before/after examples for all 24 patterns.
+
+## 2.0.0
+
+Rewrote the skill from the Wikipedia source.
+
+## 1.0.0
+
+First release.

package/skills/humanizer/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Siqi Chen
+
+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.