Check technical writing in Markdown or plain text against twelve measurable clarity rules

baltor_plain_technical_writing_check

Check technical writing in Markdown or plain text against twelve measurable clarity rules and report each finding with its line, column, paragraph and sentence.

Files, names only

LICENSE 1.0 KB
SKILL.md 2.9 KB
contracts/input.schema.json 2.9 KB
contracts/output.schema.json 11.1 KB
examples/example.expected.json 5.1 KB
examples/example.input.json 494 bytes
examples/example.md 330 bytes
references/README.md 6.0 KB
references/provenance.json 6.1 KB
scripts/tool.py 45.0 KB
verification/test_tool.py 18.3 KB

Full files in your harness.

What it takes and gives

Command: python3 -B scripts/tool.py --check draft.md
Input fields: text, format, limits, rules, known_abbreviations, source_name
Test: python3 -B -m unittest discover -s verification -p 'test_*.py' -v
Files: SKILL.md, contracts/input.schema.json, contracts/output.schema.json, scripts/tool.py
Placed for: Claude Code, Codex, OpenCode

Limits and scope

Limits: ASD-STE100 Simplified Technical English (STE) is a writing standard of the Aerospace, Security and Defence Industries Association of Europe. The rules are inspired by the published writing rules of ASD-STE100; not an official or certified STE checker.

Details

Kind: Skill
Licence: MIT
Declared effects: reads files, runs commands
Placed for: Claude Code, Codex, OpenCode
Source: docs/architecture/NORTH-STAR.md
Size: 11 files, 99.3 KB
Identity: baltor_plain_technical_writing_check
Version: 9fbac5e3c8d8fb70a4484a20097c3a4deb86345ca41f6044844a3526b09c58ec

The version is the SHA-256 of the item your harness downloads; every file in it names its own checksum.

Where it is shown

Checks for agent workDeterministic skills

Related components

Something wrong with this item, its rights or its safety? Report it on the support page, or from your harness after a download.