Agent Skills: ladder-of-abstraction
Moves prose deliberately between the concrete and the abstract and stops it stranding in the middle rung where bureaucratic prose lives. Tags every paragraph R1 (named particulars) to R4 (meaning), enforces run rules, detects the middle-rung trap, repairs it by climbing down to a real particular rather than simplifying vocabulary, gates the top rung with a counter-sentence test, and closes with an A-frame descent. Use when a draft reads as dense, vague, or jargon-heavy, when a readability score fails, when a conclusion feels grandiose or unearned, when technical material will not land for a general reader, or when user mentions ladder of abstraction, too abstract, too vague, concrete example, middle rung, dead zone, jargon, altitude, zoom in, zoom out, and thus capitalism.
Install this agent skill to your local
Skill Files
The files that make up ladder-of-abstraction.
More agent skills
- adr-architectureDocuments significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
- monitoring-expertConfigures monitoring systems, implements structured logging pipelines, creates Prometheus/Grafana dashboards, defines alerting rules, and instruments distributed tracing. Implements Prometheus/Grafana stacks, conducts load testing, performs application profiling, and plans infrastructure capacity. Use when setting up application monitoring, adding observability to services, debugging production issues with logs/metrics/traces, running load tests with k6 or Artillery, profiling CPU/memory bottlenecks, or forecasting capacity needs.
- peer-reviewPrepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments. Use for authorized review of scientific manuscripts, protocols, preprints, or research proposals; reporting-guideline selection; claim–evidence checks; methods, statistics, reproducibility, ethics, figure/table, and citation critique; or revision-response planning.
- data-engineerBuild scalable data pipelines, modern data warehouses, and
- abridge-rate-limitsAnalyze and control capacity, queueing, and backpressure for a tenant-specific Abridge integration without inventing public limits or headers. Use when handling concurrency or throttling requirements. Trigger with \"plan Abridge capacity\".
- scientific-critical-thinkingEvaluate scientific claims and evidence quality. Use for assessing experimental design validity, identifying biases and confounders, applying evidence grading frameworks (GRADE, Cochrane Risk of Bias), or teaching critical analysis. Best for understanding evidence quality, identifying flaws. For formal peer review writing use peer-review.