Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    STE Precision — Technical Writing Clarity Auditor

    1

    Audits and rewrites technical documentation for ASD-STE100-informed clarity using a deterministic offline screener, without ever claiming false compliance certification.

    $7.15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    STE Precision — Technical Writing Clarity Auditor

    STE Precision — Technical Writing Clarity Auditor

    Example session with this skill installed

    Here's a snippet from our on-call runbook, can you tighten it up? "In the event that the primary database connection is lost, the on-call engineer, after first checking the status dashboard and confirming that the issue is not a known scheduled maintenance window, which can be verified via the maintenance calendar, should then proceed to restart the connection pooler service; note that this operation may cause a brief service interruption of up to 30 seconds, and it is important that the engineer does not restart the primary database itself as this could cause data loss."

    • Read your context and instructions
    • Compiled the ste precision

    Document Type / Mode

    Procedure (runbook step) —

    STE-informed clarity mode. No compliance label attached; this is a clarity rewrite, not a certified standards audit.

    Deterministic Script Output

    $ python scripts/ste_audit.py runbook_excerpt.md --mode procedure --format json
    PARTIAL_STRUCTURAL_REVIEW / UNVERIFIED_LEXICAL — 2 candidates
    L1: sentence_length_candidate — "In the event that the primary database connection is lost, the on-call engineer..." (approx. 52 words; threshold 20)
    L1: semicolon_candidate — "...restart the connection pooler service; note that this operation may cause..."
    

    Protected Elements Frozen Before Editing

    ElementValueMust not change
    Modal (uncertainty)"may cause"Stays "may" — not "will" or "does"
    Negation"does not restart the primary database"Stays negative — not rephrased positive
    Numeric limit"up to 30 seconds"Exact value preserved
    Precondition"checking the status dashboard... confirming... not a scheduled maintenance window"Order preserved — happens before the restart action
    Prohibition rationale"could cause data loss"Preserved — this is the reason the prohibition exists

    Minimal Rewrite (One Instruction Per Sentence)

    If the primary database connection is lost, do this:

    1. Check the status dashboard.
    2. Confirm the maintenance calendar does not show a scheduled maintenance window for this time.
    3. Restart the connection pooler service.

    NOTE: This restart may cause a service interruption of up to 30 seconds.

    WARNING: Do not restart the primary database. This can cause data loss.

    Semantic-Change Ledger

    PropositionBeforeAfterStatus
    Interruption possibility"may cause... up to 30 seconds""may cause... up to 30 seconds"PRESERVED — modal and numeric limit unchanged
    Prohibition on primary DB restartburied mid-sentence, after the main instructionpromoted to a standalone WARNING, placed lastPRESERVED (meaning), flag: placement changed — confirm a trailing WARNING is acceptable in your runbook format, or require it immediately after step 3
    Precondition orderchecks before restartchecks before restart (steps 1–2 before step 3)PRESERVED

    Verified vs. Unverified

    Verified by script: sentence-length and semicolon flags on the original; protected-token diff confirms no numeric, modal, or negation drift in the rewrite.

    Unverified (requires your/SME review): whether a trailing WARNING label meets your organization's runbook formatting standard — the skill does not certify runbook-formatting compliance, only flags the placement change for your decision.

    Next Steps

    1. Confirm the WARNING placement (trailing vs. immediately after the triggering step) matches your runbook's house style.
    2. Run python scripts/ste_audit.py against the final version once placed in the actual runbook file to confirm no new length/semicolon candidates were introduced.
    3. Have the on-call lead sign off on the semantic-change ledger before this replaces the live runbook entry.

    Verification Commands

    python scripts/ste_audit.py runbook_excerpt.md --mode procedure --format json
    python -m unittest discover -s tests
    

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Technical documentation — READMEs, runbooks, API docs, safety procedures — needs unambiguous language, but most "make this clearer" AI rewrites quietly change meaning: turning "may return an error" into "returns an error," or softening a "do not disconnect" warning. This skill applies ASD-STE100 Issue 9 controlled-language principles to technical writing with a built-in semantic-safety net, plus a bundled deterministic Python script for repeatable offline screening — and it is explicit, at every step, about what it cannot certify.

    What it solves

    • Stops meaning-changing "simplification" of safety-critical language (negations, modals, obligations, numeric limits).
    • Replaces subjective "sounds clearer to me" judgments with a repeatable, offline, stdlib-only structural screen.
    • Prevents false compliance claims — the skill explicitly states it is not ASD/STEMG-affiliated or certified, and labels every finding with an honest status (CLARITY_REVIEW_ONLY, PARTIAL_STRUCTURAL_REVIEW, UNVERIFIED_LEXICAL, or EXPERT_REVIEW_REQUIRED).
    • Keeps a frozen inventory of protected elements (commands, numbers, units, WARNINGS/CAUTIONS, negations, modal strength) so nothing safety-relevant changes without explicit escalation.

    How the workflow operates

    1. Inventories the document type, audience, safety criticality, and applicable standard before touching anything.
    2. Freezes protected elements (code, API names, numbers, units, preconditions, safety labels) as invariants pending human approval.
    3. Generates minimal rewrite candidates — one ambiguity at a time — rather than a full rewrite.
    4. Runs the bundled scripts/ste_audit.py for deterministic, offline sentence-length, passive-voice, semicolon, contraction, and note-command candidate detection, with an optional --compare mode that flags protected-token drift between two versions.
    5. Runs a semantic-guard review comparing before/after text for changes to negation, modality, numbers, roles, or order — escalating anything risky to the user/SME instead of silently approving it.
    6. Reports findings with sentence-level evidence, explicit "verified vs. unverified" labeling, and never a fake accuracy percentage or compliance badge.

    What's inside the package

    • SKILL.md — the accuracy contract, mode dispatch, full workflow, and output-format rules.
    • references/evaluation.md — how to build a real evaluation dataset and what the deterministic script does and does not check.
    • references/issue9-migration-notes.md and references/issue9-rule-register.md — a 53-rule independently-paraphrased research register with verification dependencies.
    • references/official-pdf-audit.md, references/source-ledger.md, references/rule-map.md, references/mode-policy.md, references/semantic-guard.md — source provenance, document-class rules, and the meaning-preservation review protocol.
    • scripts/ste_audit.py — a zero-dependency Python 3 stdlib script for offline structural screening (sentence length, passive voice, semicolons, contractions, protected-token drift).
    • tests/test_ste_audit.py — a 49-case unit test suite covering the screener's structural checks, meaning-risk comparisons, and CLI behavior.

    Ideal use cases

    • Auditing READMEs, runbooks, or API docs for ambiguity before publishing.
    • Screening a documentation rewrite for accidental meaning changes before merging.
    • Teams that want a repeatable, offline, no-network clarity check in CI without a compliance claim attached.
    • Technical writers who want ASD-STE100-informed brevity without flattening necessary precision.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.

    Not certified by ASD/STEMG. Cannot verify dictionary compliance without the official PDF. Safety-critical text requires human expert review. Heuristic checks are not exhaustive.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Nothing to install. It runs in your AI agent.

    Optional
    Python 3

    Python runs the bundled scripts/ste_audit.py screener locally (standard library only); the guidance works without it.

    Permissions

    Terminal / Shell
    Read Files

    The bundled script only reads the file(s) you explicitly point it at and never writes or modifies them; terminal access is needed only to invoke the local Python screener, with no network calls anywhere in the package.

    Listed24 days ago

    What's inside

    Frequently Asked Questions

    STE Precision uses a non-negotiable accuracy contract that locks safety labels, numerical values, and obligations as invariants, preventing the "hallucinated simplification" common in generic AI models.

    The skill identifies and flags dense noun clusters, passive voice, and ambiguous phrasing, providing a structured verification report with specific rule citations for every edit.

    You receive the core logic for ASD-STE100 Issue 9 auditing, a suite of Python-based structural screening scripts, and a framework for generating semantic change ledgers.

    While the skill uses bundled Python scripts for offline structural checks, it is designed to integrate with standard LLM environments that support code execution and markdown processing.

    Yes, the 'Inventory phase' allows you to define protected technical elements, such as API names or project-specific units, ensuring the agent treats them as immutable during the rewrite.

    It is highly effective for any procedural or instructional text, including API documentation, on-call runbooks, CLI guides, and industrial engineering manuals.

    No — the skill explicitly states it is not affiliated with or certified by ASD/STEMG, and never claims full compliance; it labels findings as clarity review, partial structural review, or requiring expert review.

    No — the official standard and its ~2,000-word dictionary are copyrighted and not reproduced; the skill contains only original, independently-paraphrased research notes and page locators.

    New in Technical Documentation