Skip to content

ericrisco/rsc-harness / skills/technical-writing

technical-writing

Verified

Use when writing or fixing user-facing technical docs — a README, a getting-started tutorial, a how-to guide, or API/CLI/config reference — especially when a page tries to teach, explain and enumerate at once, a tutorial branches, a reference is padded with opinions, a README reads like a sales pitch, samples are stale, or weasel words have crept in. NOT an SEO blog article (that is `article-writing`), NOT the content calendar or pipeline (that is `content-engine`).

FileKindSize
SKILL.mdskill md11.7 KB
evals/README.mdmarkdown824 B
evals/cases.yamlconfig3.6 KB
references/diataxis-modes.mdmarkdown4.1 KB
references/vale-starter.mdmarkdown2.2 KB
scripts/verify.shexecutablescript2.6 KB

references/vale-starter.md

View on GitHub
# Vale starter — lint prose in CI

Vale (vale.sh) is the de-facto open-source prose linter. It reads a config at
the repo root, applies styles, and exits non-zero on violations so it can gate
a PR. Used in production by GitLab, Datadog, and ING (accessed 2026-06-02).
Use these files to add a blocking prose check to a docs-as-code repo.

## `.vale.ini` (repo root)

```ini
StylesPath = .github/vale/styles
MinAlertLevel = error

# Lint Markdown and reStructuredText prose.
[*.{md,rst}]
BasedOnStyles = Acme
```

## Custom style: banned terms

Create `.github/vale/styles/Acme/Weasel.yml`:

```yaml
extends: existence
message: "Avoid '%s' — it lies about difficulty and adds no information."
level: error
ignorecase: true
tokens:
  - simply
  - just
  - easy
  - easily
  - effortless(ly)?
  - seamless(ly)?
  - blazing[- ]fast
  - supercharge
```

And `.github/vale/styles/Acme/Substitutions.yml` for preferred terms:

```yaml
extends: substitution
message: "Use '%s' instead of '%s'."
level: error
ignorecase: true
swap:
  in order to: to
  leverage: use
  utilize: use
  log in: sign in
  login: sign in
```

## GitHub Actions: blocking check

Create `.github/workflows/vale.yml`. It fails the PR when prose violates the
style, so docs cannot merge with banned terms.

```yaml
name: vale
on:
  pull_request:
    paths:
      - "**/*.md"
      - "**/*.rst"
jobs:
  prose:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: errata-ai/vale-action@reviewdog
        with:
          fail_on_error: true
          filter_mode: nofilter
```

`fail_on_error: true` makes the job exit non-zero on any error-level alert, so
it blocks the merge. `filter_mode: nofilter` lints the whole changed file, not
only added lines.

## Also check links and samples

Prose lint is half the job. Add to CI (writethedocs.org/guide/tools/testing):

- **Link check** — e.g. `lychee` over the docs tree, fail on dead links.
- **Sample execution** — extract fenced code and run it, or keep samples in a
  tested examples dir and embed them, so a broken command fails the build.

The local equivalent of this gate is `scripts/verify.sh`, which greps the same
banlist without needing Vale installed.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall