aldengolab/orwell-clear-writing
skills/orwell-clear-writing/SKILL.md
This skill governs all prose output — Claude's own responses, documentation, PR descriptions, commit messages, README content, comments, and any text the user asks to draft or edit. It should also be used when the user asks to "review my writing", "edit this for clarity", "make this clearer", "simplify this text", "rewrite this", "check my prose", "tighten this up", or "make this more concise". Based on George Orwell's "Politics and the English Language" (1946).
development
Updated Apr 10, 2026
$ install --global
skillsauthnpx skillsauth add aldengolab/lorist orwell-clear-writingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 10, 2026, 3:32 AM80.9s2 files scanned
SKILL.md
- name:
- orwell-clear-writing
- description:
- >-
- version:
- 1.0.0
Clear Writing (Orwell)
Apply these rules to all prose — Claude's own output and text drafted for the user.
The Six Rules
- Never use a metaphor, simile, or figure of speech seen regularly in print.
- Never use a long word where a short one will do.
- If it is possible to cut a word out, always cut it out.
- Never use the passive where the active works.
- Never use a foreign phrase, a scientific word, or a jargon word when an everyday English equivalent exists.
- Break any of these rules sooner than say anything barbarous.
Before Writing
Ask six questions before committing words:
- What am I trying to say?
- What words will express it?
- What image or idiom will make it clearer?
- Is this image fresh enough to have an effect?
- Could I put it more shortly?
- Have I said anything that is avoidably ugly?
Start from meaning, then find words — never the reverse. If a phrase comes to mind fully formed, it is probably stale.
When Reviewing User Text
- Read the full text.
- Consult
references/bad-writing-catalog.mdfor the full anti-pattern catalog. - Rewrite offending passages — show original alongside revision.
- Name the rule each change addresses.
- Apply Rule 6: never make text worse to satisfy rules 1-5.
Scope
Applies to prose — text read as connected sentences. Does not apply to code identifiers, log messages, quotations, or domain terms with no plain equivalent (use those, but define on first use).
Reference
references/bad-writing-catalog.md— Dying metaphors, verbal false limbs, pretentious diction, meaningless words, passive voice problems. Each with examples and diagnostic tests.
Related Skills
aldengolab/ubuntu-secureboot-pxe-netboot
development
VerifiedTrustedCommunity
Build a UEFI Secure Boot PXE netboot server for Ubuntu autoinstall. Use when: designing or implementing network boot infrastructure for automated Ubuntu provisioning with Secure Boot enabled. Covers the complete chain: signed shim+GRUB selection, TFTP layout, kernel parameters, autoinstall config requirements, and post-install bootstrapping scripts. Also applicable when debugging an existing PXE setup that uses the wrong GRUB binary or config paths.
SKILL.mdUpdated Apr 10, 2026
aldengolab/pxe-grub-persistent-server-pattern
development
VerifiedTrustedCommunity
Design pattern for running a persistent PXE/TFTP server that safely coexists with already-installed nodes. Use when: building PXE infrastructure that should stay always-on, designing automated bare-metal provisioning in GitOps/Kubernetes environments, or any PXE setup where UEFI boot order has network boot first. Eliminates boot loops without requiring UEFI firmware changes.
SKILL.mdUpdated Apr 10, 2026
aldengolab/k8s-hostnetwork-port-conflict
development
VerifiedTrustedCommunity
Debug Kubernetes pods using hostNetwork: true that crash with "Address already in use" or "failed to create listening socket for port N". Use when: (1) a hostNetwork pod container is in CrashLoopBackOff and logs show a port bind failure, (2) the port works fine in non-hostNetwork pods but fails with hostNetwork, (3) you need to identify which host-level process holds a port from within Kubernetes (no SSH). Covers /proc/net/udp inspection and kubectl debug node with nsenter.
SKILL.mdUpdated Apr 10, 2026
aldengolab/plan-review
development
VerifiedTrustedCommunity
Adversarial 3-stage review of an implementation plan before execution — checks completeness, security/best-practices, and multi-agent implementability. Use this skill whenever the user wants to validate, review, stress-test, or check an existing implementation plan before building or executing it. Trigger on phrases like "review the plan", "stress-test the plan", "is this plan ready", "check the plan", "validate the plan", "go through the plan", "find what's wrong with the plan", "is this ready for agents", "can subagents execute this", or any request to find gaps, security issues, or underspecified tasks in a plan that has already been written. Also trigger when the user has just finished /plan-implementation and is about to run /autonomous-plan-execution — the plan should be reviewed first. This skill is specifically for reviewing EXISTING plans, not for writing new ones (use plan-implementation for that), not for code review or PR review (use code-review for that), and not for debugging or post-deployment issues. If the user mentions a plan file, says "before we build", or asks whether phases can be parallelized, this skill almost certainly applies.
SKILL.mdUpdated Apr 3, 2026