Writing Simplified Technical English
by PostHog469d1773e9cbNo licenseListed Oct 8, 2026Updated Oct 8, 2026
Write English that a reader cannot misread: one meaning per word, active voice, simple tenses, one idea per sentence, short sentences. Based on ASD-STE100 (Simplified Technical English), the controlled-language standard written for aircraft maintenance manuals. Use it for any prose an agent produces that someone else acts on. That covers reports and findings, PR descriptions and commit messages, instructions handed to another agent, tool descriptions, error messages, status summaries, and prompts. Also use it on request, with triggers like "simplify this", "make this readable", "too dense", "rewrite in STE", "simplified technical english", "ASD-STE100".
- 469d1773e9cbCurrentcommit 469d177Published Oct 8, 2026
Source and attribution
Source:PostHog/ai-plugininskills/writing-simplified-technical-englishat commit469d177
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from PostHog/ai-plugin
Working With Task Comments
PostHog
Reads and interprets comments on PostHog tasks, artifacts, and canvases through the PostHog MCP exec dispatcher.
Working With Skills
PostHog
Guides agents in using PostHog's skill-* MCP tools to discover, read, create, update, and refactor skills.
Working With Scouts
PostHog
Operating manual for delegating watching jobs to PostHog Signals scouts, acting on their reports, and steering the fleet over time.
Validating And Publishing Canvases
PostHog
Validate and publish a canvas source project safely: the source-project shape, declared capabilities, reading the current version pointer, iterating on validation diagnostics, guarded publishing with expected_current_version_id, staging a draft build and promoting it, waiting out the queued build, and recovering from a 409 version_conflict or a 429 capacity limit without overwriting concurrent work. Use whenever a canvas edit is ready to save, a draft build is wanted, a canvas publish or build returns diagnostics or a conflict, or a task needs to understand canvas version history.
Understanding Billing Usage
PostHog
Explains PostHog billing usage and spend from the customer's visible Billing MCP tools. Use when the user asks why usage or spend is high, which product or project is driving usage, what a usage type means, how to reduce usage, what changed over time, why they got a usage change alert, or whether a spike/drop alert was real or noisy. Also use before product-specific analytics skills when the user names a billable PostHog product metric such as events, recordings, feature flag requests, exceptions, survey responses, synced rows, logs, AI events, AI credits, or Inbox credits. Starts from Billing usage/spend tools, then routes to customer-visible product MCP surfaces for deeper investigation.
Turning Engineering Analytics Into Insights
PostHog
Turns engineering analytics data into saved PostHog SQL insights, dashboards and subscriptions, with HogQL guidance.
More in Writing & Content
Doc Coauthoring
anthropics
Guides users through a three-stage workflow to co-author documentation, proposals, specs and decision docs.
Writing Guidelines
vercel-labs
Reviews documentation and prose against fetched Writing Guidelines and reports style findings.
Wiki Page Writer
microsoft
Generates technical documentation wiki pages with Mermaid diagrams, code citations and VitePress frontmatter.
Wiki Onboarding
microsoft
Generates four audience-tailored codebase onboarding guides: contributor, staff engineer, executive, and product manager.
Visa Doc Translate
affaan-m
Translates visa application document images into English and produces a bilingual PDF with the original image and translation.
Crosspost
affaan-m
Adapts one piece of content into platform-specific versions for X, LinkedIn, Threads, and Bluesky.