STE-Pro Max
Clear writing. Evidence-linked explanations.
STE-inspired writing and Karpathy-inspired explanations: briefs, diagrams, and interactive documents.
Copilot CLI + OpenCode. Automatic checks. Other hosts: legacy skills only.
STE · Karpathy · Demos · SkillC · Install · Docs
STE: the foundation
STE means Simplified Technical English, a controlled writing language. Here, clearer language must preserve facts and uncertainty.
Before: “Prior to initiating deployment, verification of the configuration is required.”
STE: “Check the configuration before you deploy.”
STE-inspired, not ASD-STE100 certification. The approach.
Karpathy's guidelines, put to work
Our takeaways from his post:
- Write clearly: relaxed STE.
- Explain mechanisms: diagrams and images.
- Make it explorable: interactive HTML, controls, and animation.
- Narrate only with an available media tool.
- Build to explain: small, purpose-built software.
Choose the smallest useful medium. Keep the evidence inspectable.
Show, don't tell
Line Studio: see the mechanism
“Make 81 → 3 explorable.”
Retry Observatory: 81 versus 3
Adjust budgets, scrub, export SVG. Guide.
New in v0.5.0.
One request. 81 backend attempts.
“Show me why retries multiply. Let me change the rules.”
Four layers with three attempts: 81 backend attempts; one retry owner: 3.
A dense note becomes an evidence-linked brief
“Turn this pilot write-up into a one-screen briefing. Keep the evidence.”
Fictional Northstar pilot: 186/240 answers accepted, limits retained, shadow pilot proposed.
Compare rates without losing context
“Explain 97.4% → 99.7%. Let me change the baseline.”
97.4% to 99.7%: 2.3 percentage points, 2.36% relative change; zero-based scale.
Explore percentage points versus relative change.
Working HTML, not UI mockups. Fictional data and illustrative models. Get examples. No build or server.
Automatic SkillC checks in v0.6.1
SkillC makes STE’s tools check their work before reporting success.
render, narrate, and export check inputs, declared evidence, and actual outputs.
Missing declared evidence blocks a bundle. Changed evidence blocks export. Empty or invalid audio fails preparation.
This is workflow checking, not an English tutor or fact-checker. No manual approval step. Native STE tools need a configured runtime. STE does not restrict your other tools. No off command; host permissions still apply.
Why it matters and how it works · Credits · Tested scope.
Install the plugin
Install v0.6.1. Native tools need a configured runtime.
GitHub Copilot CLI
copilot plugin marketplace add shyamsridhar123/STE-Pro-Max#v0.6.1
copilot plugin install ste-pro-max@ste-pro-max-plugins
Claude Code — legacy v0.5.0 skills
claude plugin marketplace add shyamsridhar123/STE-Pro-Max#v0.5.0
claude plugin install ste-pro-max@ste-pro-max-plugins
Codex CLI — legacy v0.5.0 skills
codex plugin marketplace add shyamsridhar123/STE-Pro-Max --ref v0.5.0
codex plugin add ste-pro-max@ste-pro-max-plugins
Use STE-Pro Max on this material. Make it clear, visual, and interactive where it helps.