fix: remove em dash

Author: jeremy-london

.github/ACT.md

@@ -4,35 +4,35 @@
 
 **act** is a CLI that runs **GitHub Actions workflows on your computer** instead of on GitHub. It starts **Docker** containers that behave like GitHub’s `ubuntu-latest` runners, checks out your repo (or copies the working tree), and runs the same `run:` steps your YAML defines.
 
-You use it to **catch CI failures before you push**—for example broken `plugin.json`, bad SKILL frontmatter, or failed skill checks.
+You use it to **catch CI failures before you push**-for example broken `plugin.json`, bad SKILL frontmatter, or failed skill checks.
 
 ## How it works (mental model)
 
-1. **Event** — You tell act what happened, e.g. `push` or `pull_request`. Many of our workflows are written for `on: push` / `pull_request`, so `act push` is the usual choice.
-2. **Workflow file** — You pass **which YAML** to run with `-W .github/workflows/<file>.yml`. act does **not** read `on: paths:` the same way GitHub does; if you pass a file, act runs that workflow.
-3. **Jobs** — act lists jobs with `act -l -W …`, then runs them in Docker when you use `act push -W …`.
-4. **Checkout** — `actions/checkout` inside the container gets your project files (warnings like `unable to get git ref` are common until you have at least one git commit; the tree is still copied).
+1. **Event** - You tell act what happened, e.g. `push` or `pull_request`. Many of our workflows are written for `on: push` / `pull_request`, so `act push` is the usual choice.
+2. **Workflow file** - You pass **which YAML** to run with `-W .github/workflows/<file>.yml`. act does **not** read `on: paths:` the same way GitHub does; if you pass a file, act runs that workflow.
+3. **Jobs** - act lists jobs with `act -l -W …`, then runs them in Docker when you use `act push -W …`.
+4. **Checkout** - `actions/checkout` inside the container gets your project files (warnings like `unable to get git ref` are common until you have at least one git commit; the tree is still copied).
 
 Nothing is sent to GitHub when you run act; it is **fully local** (except pulling Docker images the first time).
 
 ## Prerequisites
 
 1. **Docker** running (`docker info` should succeed).
-2. **act** installed — [releases](https://github.com/nektos/act/releases) or e.g. `brew install act`. Use **act ≥ 0.2.86** when possible (security fixes).
+2. **act** installed - [releases](https://github.com/nektos/act/releases) or e.g. `brew install act`. Use **act ≥ 0.2.86** when possible (security fixes).
 
 ## Run this repo’s CI locally (copy-paste)
 
 From the **repository root**:
 
-**Recommended — all workflows (same as `task act`):**
+**Recommended - all workflows (same as `task act`):**
 
 ```bash
 ./scripts/act-all.sh
 ```
 
-That script lists and runs **validate-plugin** and **test-skills** with `act push` (these **must** succeed — the script exits non-zero if either fails). It then runs **semantic-pull-request** (`act pull_request` + [`.github/act/event-pull_request.json`](act/event-pull_request.json)) and **release-please** (`act push`) as **extra smoke tests**. Those two workflows call the **GitHub REST API** (`pulls.get`, release-please), so they **usually fail inside act** without a real `GITHUB_TOKEN`; that is expected and the script still exits **0** after the first two workflows pass.
+That script lists and runs **validate-plugin** and **test-skills** with `act push` (these **must** succeed - the script exits non-zero if either fails). It then runs **semantic-pull-request** (`act pull_request` + [`.github/act/event-pull_request.json`](act/event-pull_request.json)) and **release-please** (`act push`) as **extra smoke tests**. Those two workflows call the **GitHub REST API** (`pulls.get`, release-please), so they **usually fail inside act** without a real `GITHUB_TOKEN`; that is expected and the script still exits **0** after the first two workflows pass.
 
-**Manual — plugin + skills only:**
+**Manual - plugin + skills only:**
 
 **1. See what would run (job names):**
 
@@ -50,14 +50,14 @@ act push -W .github/workflows/test-skills.yml
 
 Order does not matter between the two files; run both to match what CI exercises for plugin + skills.
 
-**Manual — semantic PR workflow (`pull_request`):**
+**Manual - semantic PR workflow (`pull_request`):**
 
 ```bash
 act -l -W .github/workflows/semantic-pull-request.yml
 act pull_request -W .github/workflows/semantic-pull-request.yml -e .github/act/event-pull_request.json
 ```
 
-**Manual — release-please (`push` to `main`):**
+**Manual - release-please (`push` to `main`):**
 
 ```bash
 act -l -W .github/workflows/release-please.yml
@@ -83,9 +83,9 @@ If you use [Task](https://taskfile.dev/), [`Taskfile.yaml`](../Taskfile.yaml) de
 
 | Topic | On GitHub | With act |
 | --- | --- | --- |
-| `paths:` filters | Workflow may be skipped if paths don’t match | Ignored for “should this run?” — you chose the file with `-W` |
+| `paths:` filters | Workflow may be skipped if paths don’t match | Ignored for “should this run?” - you chose the file with `-W` |
 | Runners | GitHub-hosted Ubuntu | Docker image (e.g. `ghcr.io/catthehacker/ubuntu:act-latest`) |
-| **`GITHUB_TOKEN`** | Injected automatically for each job as `secrets.GITHUB_TOKEN` (scoped to the repo, permissions from the workflow `permissions:` block). You do **not** add it under **Settings → Secrets**. | **Not** the same as GitHub’s token. act may set a placeholder or empty value; it does **not** mint a real token that can call `api.github.com` like the hosted runner. To exercise API-using actions locally you must pass a token yourself (e.g. `act … -s GITHUB_TOKEN=…` with a fine-scoped PAT)—optional and easy to get wrong, so we treat API workflows as **CI-only** for “full success.” |
+| **`GITHUB_TOKEN`** | Injected automatically for each job as `secrets.GITHUB_TOKEN` (scoped to the repo, permissions from the workflow `permissions:` block). You do **not** add it under **Settings → Secrets**. | **Not** the same as GitHub’s token. act may set a placeholder or empty value; it does **not** mint a real token that can call `api.github.com` like the hosted runner. To exercise API-using actions locally you must pass a token yourself (e.g. `act … -s GITHUB_TOKEN=…` with a fine-scoped PAT)-optional and easy to get wrong, so we treat API workflows as **CI-only** for “full success.” |
 | `import yaml` in Python | Works after we install **`python3-yaml`** via `apt` in the workflow | Same; that step exists so act matches GitHub |
 | **release-please** / **semantic PR** actions | Full GitHub API + real `GITHUB_TOKEN` | May fail or partially run without a PAT; use for YAML/container smoke tests |
 
@@ -100,5 +100,5 @@ If you use [Task](https://taskfile.dev/), [`Taskfile.yaml`](../Taskfile.yaml) de
 
 ## See also
 
-- [CONTRIBUTING.md — Development setup](../CONTRIBUTING.md#optional-run-ci-workflows-locally-with-act)
+- [CONTRIBUTING.md - Development setup](../CONTRIBUTING.md#optional-run-ci-workflows-locally-with-act)
 - [GitHub: Workflow syntax](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)

.github/ISSUE_TEMPLATE/bug_report.md

@@ -33,4 +33,4 @@ assignees: []
 
 ## Additional context
 
-<!-- Logs, screenshots, links — do not paste secrets, tokens, or real record UIDs -->
+<!-- Logs, screenshots, links - do not paste secrets, tokens, or real record UIDs -->

.github/ISSUE_TEMPLATE/config.yml

@@ -2,4 +2,4 @@ blank_issues_enabled: true
 contact_links:
   - name: Keeper Security product support
     url: https://keepersecurity.com/support
-    about: Account, vault, KSM, or Commander product issues — use official support, not this repo.
+    about: Account, vault, KSM, or Commander product issues - use official support, not this repo.

CHANGELOG.md

@@ -8,14 +8,14 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 ### Added
 
-- **Skills** — Three agent skills with reference documentation under `skills/*/references/`:
-  - `keeper-secrets` — KSM CLI (`ksm`): secrets retrieval, `ksm exec`, `ksm interpolate`, Keeper notation, Docker/Kubernetes/CI patterns.
-  - `keeper-admin` — Keeper Commander (`keeper`): vault, enterprise admin, PAM, rotation, and related command references.
-  - `keeper-setup` — Installing and configuring the KSM and Commander CLIs, regions, and troubleshooting.
-- **Distribution** — Claude Code plugin metadata (`.claude-plugin/`), marketplace listing, and install paths via [Vercel Skills CLI](https://github.com/vercel-labs/skills) (`npx skills add`) or manual copy into an agent’s skills directory.
-- **Documentation** — README, CONTRIBUTING, SECURITY, `TEST_PROMPTS.md`, and links to official Keeper docs (Secrets Manager overview, Commander overview, Keeper notation).
-- **CI** — GitHub Actions workflows to validate plugin JSON, marketplace JSON, SKILL frontmatter, reference files, and skill trigger/content checks; `python3-yaml` installed in workflows for reliable frontmatter parsing locally and on runners.
-- **Developer tooling** — `Taskfile` tasks for Markdown (`task fmt`), dependencies (`task install`), and running CI locally with [act](https://github.com/nektos/act) (`task act`); [`.github/ACT.md`](.github/ACT.md) documents local workflow runs.
-- **Community** — Issue templates, pull request template, `CODEOWNERS`, Apache 2.0 [`LICENSE.md`](LICENSE.md).
+- **Skills** - Three agent skills with reference documentation under `skills/*/references/`:
+  - `keeper-secrets` - KSM CLI (`ksm`): secrets retrieval, `ksm exec`, `ksm interpolate`, Keeper notation, Docker/Kubernetes/CI patterns.
+  - `keeper-admin` - Keeper Commander (`keeper`): vault, enterprise admin, PAM, rotation, and related command references.
+  - `keeper-setup` - Installing and configuring the KSM and Commander CLIs, regions, and troubleshooting.
+- **Distribution** - Claude Code plugin metadata (`.claude-plugin/`), marketplace listing, and install paths via [Vercel Skills CLI](https://github.com/vercel-labs/skills) (`npx skills add`) or manual copy into an agent’s skills directory.
+- **Documentation** - README, CONTRIBUTING, SECURITY, `TEST_PROMPTS.md`, and links to official Keeper docs (Secrets Manager overview, Commander overview, Keeper notation).
+- **CI** - GitHub Actions workflows to validate plugin JSON, marketplace JSON, SKILL frontmatter, reference files, and skill trigger/content checks; `python3-yaml` installed in workflows for reliable frontmatter parsing locally and on runners.
+- **Developer tooling** - `Taskfile` tasks for Markdown (`task fmt`), dependencies (`task install`), and running CI locally with [act](https://github.com/nektos/act) (`task act`); [`.github/ACT.md`](.github/ACT.md) documents local workflow runs.
+- **Community** - Issue templates, pull request template, `CODEOWNERS`, Apache 2.0 [`LICENSE.md`](LICENSE.md).
 
 [1.0.0]: https://github.com/Keeper-Security/agent-kit/releases/tag/v1.0.0

CONTRIBUTING.md

@@ -73,8 +73,8 @@ This repo is Markdown-only (no build step for the skills themselves). To run the
 
 ### Required: Task and Cargo
 
-1. **[Task](https://taskfile.dev/installation/)** — install the `task` CLI so you can run tasks from [`Taskfile.yaml`](Taskfile.yaml) (`task fmt`, `task install`, etc.).
-2. **[Rust and Cargo](https://doc.rust-lang.org/cargo/getting-started/installation.html)** — required because `task install` uses [cargo-binstall](https://github.com/cargo-bins/cargo-binstall) to pull prebuilt binaries (e.g. [rumdl](https://github.com/rvben/rumdl)).
+1. **[Task](https://taskfile.dev/installation/)** - install the `task` CLI so you can run tasks from [`Taskfile.yaml`](Taskfile.yaml) (`task fmt`, `task install`, etc.).
+2. **[Rust and Cargo](https://doc.rust-lang.org/cargo/getting-started/installation.html)** - required because `task install` uses [cargo-binstall](https://github.com/cargo-bins/cargo-binstall) to pull prebuilt binaries (e.g. [rumdl](https://github.com/rvben/rumdl)).
 
 Then clone and install dev tools:
 
@@ -113,9 +113,9 @@ Pull requests are checked by **Semantic PR** (`.github/workflows/semantic-pull-r
 
 #### `version.txt` (how the version is updated)
 
-- **Role** — One line, semver only (e.g. `1.2.3`). With **`release-type: simple`** in `release-please-config.json`, this file is the **canonical project version** release-please reads and writes.
-- **Normal workflow** — **Do not** edit `version.txt` by hand to ship a release. Land conventional commits on `main`, let release-please open its **release PR**, review it, and **merge that PR**. The PR updates `version.txt` together with `.release-please-manifest.json`, `CHANGELOG.md`, and the `version` fields in `.claude-plugin/plugin.json` and `marketplace.json` (see `extra-files` in `release-please-config.json`).
-- **Avoid drift** — If you ever change a version **outside** that flow (unusual), update **every** file release-please keeps in sync so they all match; mismatches break automation and CI expectations.
+- **Role** - One line, semver only (e.g. `1.2.3`). With **`release-type: simple`** in `release-please-config.json`, this file is the **canonical project version** release-please reads and writes.
+- **Normal workflow** - **Do not** edit `version.txt` by hand to ship a release. Land conventional commits on `main`, let release-please open its **release PR**, review it, and **merge that PR**. The PR updates `version.txt` together with `.release-please-manifest.json`, `CHANGELOG.md`, and the `version` fields in `.claude-plugin/plugin.json` and `marketplace.json` (see `extra-files` in `release-please-config.json`).
+- **Avoid drift** - If you ever change a version **outside** that flow (unusual), update **every** file release-please keeps in sync so they all match; mismatches break automation and CI expectations.
 
 ### Optional: run CI workflows locally with [act](https://github.com/nektos/act)
 
@@ -276,30 +276,30 @@ ksm secret list
 
 Focus on:
 
-- **When to use** — Clarify skill purpose and when agent should use it
-- **Prerequisites** — What users need before using
-- **Core concepts** — Key ideas explained simply
-- **Common patterns** — Most used workflows
-- **Guardrails** — Security and safety guidelines
+- **When to use** - Clarify skill purpose and when agent should use it
+- **Prerequisites** - What users need before using
+- **Core concepts** - Key ideas explained simply
+- **Common patterns** - Most used workflows
+- **Guardrails** - Security and safety guidelines
 
 ### Reference Files
 
 Focus on:
 
-- **Complete reference** — All commands and options
-- **Examples** — Real-world usage patterns
-- **Troubleshooting** — Common issues and solutions
-- **Best practices** — Recommended approaches
+- **Complete reference** - All commands and options
+- **Examples** - Real-world usage patterns
+- **Troubleshooting** - Common issues and solutions
+- **Best practices** - Recommended approaches
 
 ## Versioning
 
-**Plugin / repo version** — [release-please](https://github.com/googleapis/release-please) manages **one** semver for the whole distribution: `version.txt`, `.release-please-manifest.json`, `CHANGELOG.md`, and the `version` fields in **`.claude-plugin/plugin.json`** and **`.claude-plugin/marketplace.json`** (see `release-please-config.json` → `extra-files`). It does **not** bump per-skill versions; skills under `skills/` ship as part of that plugin release.
+**Plugin / repo version** - [release-please](https://github.com/googleapis/release-please) manages **one** semver for the whole distribution: `version.txt`, `.release-please-manifest.json`, `CHANGELOG.md`, and the `version` fields in **`.claude-plugin/plugin.json`** and **`.claude-plugin/marketplace.json`** (see `release-please-config.json` → `extra-files`). It does **not** bump per-skill versions; skills under `skills/` ship as part of that plugin release.
 
 **Change significance** (for commit messages and changelog tone; not separate skill semver in this repo):
 
-- **MAJOR** — Breaking changes to command syntax or CLI
-- **MINOR** — New features, new commands, additions
-- **PATCH** — Documentation fixes, clarifications, typos
+- **MAJOR** - Breaking changes to command syntax or CLI
+- **MINOR** - New features, new commands, additions
+- **PATCH** - Documentation fixes, clarifications, typos
 
 ## License