# Editorial style guide checker

- Human page: https://happytails.ai/en/text-tools/editorial-style-guide-checker/
- Markdown: https://happytails.ai/en/text-tools/editorial-style-guide-checker.md
- Structured JSON: https://happytails.ai/agents/en/text-tools/editorial-style-guide-checker/index.json
- Visibility: public

## Tool capabilities

| Property | Value |
| --- | --- |
| Tool ID | `editorial-style-guide-checker` |
| Category | text-tools |
| Implementation | Registered implementation. Registration alone is not a production-quality guarantee. |
| Browser execution | Use the visible action or interactive controls. |
| Browser processing | Browser; see tool notes for network behavior. |
| HTTP API | Not callable through HTTP. |
| Browser-agent interface | run_current_tool |

### Implementation notes

Supply a JSON array of literal rules with id and find, plus optional replacement and note. Up to 200 rules; find up to 200 characters; id up to 100; replacement and note up to 500. Matching is exact and case-sensitive. No regular expressions or automatic edits are applied. Rules can overlap each other; findings are limited to your supplied style guide. Use up to 500000 text characters and 20000 word tokens. Reports allow up to 10000 matches or repeated phrase groups. JSON and CSV preserve the full report, with bounded exports up to 40 million characters and 500000 CSV records. Analysis runs locally with a 10-second timeout. Preview search and sort cover the first 200 rows; copy returns the summary. Download the full report for every row. Your text is not uploaded.

### Inputs and settings

Text input: Your text.

Example or placeholder shown in the interface (not a validated fixture):

```text
Type or paste your input…
```

Up to 500,000 characters. Review the settings before running.

| Setting | Meaning | Control type | Default | Constraints |
| --- | --- | --- | --- | --- |
| `rules` | Style rules JSON | textarea | "[{\"id\":\"preferred-term\",\"find\":\"utilize\",\"replacement\":\"use\",\"note\":\"Prefer plain language\"}]" |  |

### Browser-agent workflow

1. Open the human page in a browser that supports WebMCP.
2. Discover the interface exposed by that page; use its actual schema.
3. Select files on the page first when the tool requires files.
4. Call `run_current_tool` with valid input and settings.
5. Inspect the returned result or error and the displayed output. Retrieve files from the displayed download links.

Calls do not automatically copy or download results. Browser permissions still apply. Interface availability alone is not proof of successful execution.

### Planning specification

Supply a JSON array of literal rules with id and find, plus optional replacement and note. Up to 200 rules; find up to 200 characters; id up to 100; replacement and note up to 500. Matching is exact and case-sensitive. No regular expressions or automatic edits are applied. Rules can overlap each other; findings are limited to your supplied style guide. Use up to 500000 text characters and 20000 word tokens. Reports allow up to 10000 matches or repeated phrase groups. JSON and CSV preserve the full report, with bounded exports up to 40 million characters and 500000 CSV records. Analysis runs locally with a 10-second timeout. Preview search and sort cover the first 200 rows; copy returns the summary. Download the full report for every row. Your text is not uploaded.

This describes intended requirements. Use the implementation notes, interface schema and observed output to determine current support.

### Complete machine-readable capability record

```json
{
  "id": "editorial-style-guide-checker",
  "category": "text-tools",
  "built": true,
  "requirements": "Supply a JSON array of literal rules with id and find, plus optional replacement and note. Up to 200 rules; find up to 200 characters; id up to 100; replacement and note up to 500. Matching is exact and case-sensitive. No regular expressions or automatic edits are applied. Rules can overlap each other; findings are limited to your supplied style guide. Use up to 500000 text characters and 20000 word tokens. Reports allow up to 10000 matches or repeated phrase groups. JSON and CSV preserve the full report, with bounded exports up to 40 million characters and 500000 CSV records. Analysis runs locally with a 10-second timeout. Preview search and sort cover the first 200 rows; copy returns the summary. Download the full report for every row. Your text is not uploaded.",
  "implementation": {
    "fields": [
      {
        "key": "rules",
        "label": "Style rules JSON",
        "value": "[{\"id\":\"preferred-term\",\"find\":\"utilize\",\"replacement\":\"use\",\"note\":\"Prefer plain language\"}]",
        "type": "textarea",
        "maxLength": 250000
      }
    ],
    "presentation": "metrics",
    "inputMaxLength": 500000,
    "inputErrorCode": "TEXT_DIAGNOSTICS_INPUT",
    "note": "Supply a JSON array of literal rules with id and find, plus optional replacement and note. Up to 200 rules; find up to 200 characters; id up to 100; replacement and note up to 500. Matching is exact and case-sensitive. No regular expressions or automatic edits are applied. Rules can overlap each other; findings are limited to your supplied style guide. Use up to 500000 text characters and 20000 word tokens. Reports allow up to 10000 matches or repeated phrase groups. JSON and CSV preserve the full report, with bounded exports up to 40 million characters and 500000 CSV records. Analysis runs locally with a 10-second timeout. Preview search and sort cover the first 200 rows; copy returns the summary. Download the full report for every row. Your text is not uploaded.",
    "experience": {
      "automatic": false,
      "single": false,
      "inputMaxLength": 500000,
      "inputMode": "text",
      "label": "Your text",
      "placeholder": "Type or paste your input…",
      "help": "Up to 500,000 characters. Review the settings before running.",
      "action": null
    },
    "mode": "explicit",
    "interactive": false
  },
  "execution": "Browser interface",
  "api": null,
  "browser_agent": {
    "supported": true,
    "name": "run_current_tool",
    "discovery": "WebMCP on the human page in a supporting browser",
    "verification": "See audit/API-AUDIT.md; availability is not verification"
  }
}
```

## Page guide

Check prose against your own literal terminology rules, with exact matches and reviewable suggestions.

How can we improve this tool?

Report a problem or share an idea.

Please leave out private information. Your message and the tool name go to our team via PostHog.

### How to use Editorial style guide checker

1. Paste your own passage as plain text.
2. Choose explicit matching or analysis settings.
3. Review the bounded table and download complete JSON or CSV.

## Useful next steps

- [Concordance reader](https://happytails.ai/en/text-tools/concordance-reader/) ([Markdown](https://happytails.ai/en/text-tools/concordance-reader.md))

- [Lexical diversity analyzer](https://happytails.ai/en/text-tools/lexical-diversity-analyzer/) ([Markdown](https://happytails.ai/en/text-tools/lexical-diversity-analyzer.md))

- [Vocabulary coverage estimator](https://happytails.ai/en/text-tools/vocabulary-coverage-estimator/) ([Markdown](https://happytails.ai/en/text-tools/vocabulary-coverage-estimator.md))

## Know exactly what is measured

Supply a JSON array of literal rules with id and find, plus optional replacement and note. Up to 200 rules; find up to 200 characters; id up to 100; replacement and note up to 500. Matching is exact and case-sensitive. No regular expressions or automatic edits are applied. Rules can overlap each other; findings are limited to your supplied style guide.

### Keep the full report

Use up to 500000 text characters and 20000 word tokens. Reports allow up to 10000 matches or repeated phrase groups. JSON and CSV preserve the full report, with bounded exports up to 40 million characters and 500000 CSV records. Analysis runs locally with a 10-second timeout. Preview search and sort cover the first 200 rows; copy returns the summary. Download the full report for every row. Your text is not uploaded. Offsets refer to the original UTF-16 text. Machine report keys and your content are preserved. Formula-protected CSV changes risky cell prefixes; import columns as text when preserving exact identifiers.
