skills.rest
machenjie
machenjieCOMMUNITY
Explore all skills by this author →
GitHub

language-runtime-selection

Select programming language and runtime choices using workload classification and runtime behavior tables.

4|Updated May 16, 2026
Search Tags:#observability#runtime selection#workload classification#GC pause SLO#concurrency model#lifecycle horizon#supply-chain posture
One-click install
npx skills add https://github.com/machenjie/rd-skills --skill language-runtime-selection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: language-runtime-selection
Source: https://github.com/machenjie/rd-skills/tree/main/src/foundation/capabilities/language-runtime-selection
Command: npx skills add https://github.com/machenjie/rd-skills --skill language-runtime-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents expensive or failure-prone programming language and runtime decisions by forcing evidence-based evaluation against the workload’s actual performance, reliability, and operational constraints.

Core Features & Use Cases

  • Workload-first runtime classification: Require explicit labeling of the dominant workload axis (e.g., CPU-bound, IO-bound, latency-sensitive, memory-sensitive, batch, interactive, streaming, embedded, edge, contract-heavy) before choosing.
  • Production behavior enumeration: Validate runtime behavior across GC/pause impact, concurrency model, exception model, FFI cost, startup/cold-start budget, binary/image size, observability tooling, and debugging readiness.
  • Operational and lifecycle guardrails: Enforce named operational ownership, a hiring-market feasibility check, and a ≥ 3-year lifecycle horizon with credible roadmap/EOL expectations.
  • Risk escalation routing: Guide when to escalate to deeper decision capabilities for reliability/observability, security supply-chain risk, performance safety, or stack reconsideration.

Quick Start

Use language-runtime-selection to produce a Language/Runtime Decision Record that classifies your workload, enumerates runtime behavior against your SLOs, selects viable runtimes, and rejects alternatives with specific disqualifying constraints.

Frequently Asked Questions about language-runtime-selection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose a programming language and runtime for latency-sensitive workloads?▼

To choose a runtime for latency-sensitive workloads, you must classify the workload shape and validate runtime behavior against GC pause SLOs, concurrency models, and cold-start floors. This ensures the selected language meets strict operational constraints.

What is workload classification in runtime selection?▼

Workload classification in runtime selection is the process of explicitly labeling the dominant workload axis, such as CPU-bound, IO-bound, or memory-sensitive, before evaluating programming languages. It grounds the decision in actual performance and reliability constraints.

How do I evaluate runtime behavior for production readiness?▼

Evaluate runtime behavior for production readiness by enumerating GC pause impact, exception models, FFI cost, startup budgets, binary size, and observability tooling. This validates debugging readiness against your operational SLOs.

Can I use a runtime if it lacks a clear lifecycle horizon and operational ownership?▼

You cannot use a runtime lacking a clear lifecycle horizon and operational ownership. Enforcing a minimum 3-year lifecycle roadmap, hiring-market feasibility, and named ownership prevents committing a team to an unsupported language.

When should I escalate a programming language decision for deeper risk analysis?▼

Escalate a programming language decision for deeper risk analysis when facing supply-chain security risks, complex reliability observability requirements, or performance safety concerns. This routes edge cases to specialized decision capabilities.

What's the best way to document selected and rejected language runtimes?▼

The best way to document selected and rejected language runtimes is to produce a Language/Runtime Decision Record. This record ties viable selections and rejected alternatives to a specific decision rubric based on workload classification.

Related Skills

Explore More Software Engineering Skills→
m2ai-portfoliom2ai-portfolio
4

agent-cost-model

Compute per-task costs, daily and monthly burn, and model-routing savings for agent workflows.

Official
Advanced
badowhpbadowhp

software-architect

Design software architecture with service boundaries, data ownership, and tradeoff analysis.

Community
Advanced
lucas-flatwhitelucas-flatwhite
43

cso

Audit infrastructure, dependencies, and CI/CD pipelines to produce a security posture report.

Community
Advanced
ThrookieThrookie
2

enterprise-agent-ops

Coordinate lifecycle management, observability, and safety controls for agent workloads.

Community
Advanced