Results for “repeatability”
23 skillsMore results
ml-experiment-design
Build reproducible ML experiment plans with hypotheses, metrics, and ablations. Use when: (1) planning experiments, (2) comparing variants, (3) defining acceptance thresholds. NOT for: long-running experiment execution.
0
refactor
Refactors code for better readability, performance, and maintainability
0
data-versioning-reproducibility
A git SHA pins the transformation.
2
tenacity-python
Use for writing, reviewing, debugging, or testing bounded retry policies in Python with Tenacity, including retry predicates, stop and wait strategies, jitter, exception propagation, callbacks, Retrying, and AsyncRetrying. Do not use for generic loops, scheduled jobs, domain polling without a retryable operation, or operations whose side effects are not safe to repeat.
0 · bundle
rebuttal-traceability-matrix
Use when reviewer comments arrive and each one needs a tracked decision, when a revise and resubmit letter must map every comment to a manuscript change, or when contradictory reviewer demands need evidence-based, editor-facing framing.
2
debugging
Reproduces failures, gathers evidence, tests hypotheses, fixes root causes, and adds regression coverage.
0
exp-test-maintainability
Analyzes .NET test suites for duplicated boilerplate, copy-paste tests, and structural maintainability issues, producing a report with concrete before/after refactoring suggestions.
4k
iterative-plan-review
Sharpens and stress-tests an existing plan file through multiple codebase-grounded review passes, editing it in place and recording every finding and iteration in cross-referenced companion files. Use this skill whenever the user wants to iterate on, refine, tighten, or improve a plan. Also use it when the user asks to verify, validate, or confirm feasibility of an approach. Does not implement plan steps, write test plans, review code, or investigate bugs, and does not generate new plans from scratch — use plan-a-feature for a new plan. Runs its review rounds to completion without pausing between them; to review each round as it lands, use pairing.
218 · bundle
systematic-debugging
4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.
3
bmad-ml-omen
Standard reviewer for correctness and reproducibility. Use when the user asks to talk to Omen, requests a code review, or needs reproducibility verification.
0 · bundle
ml-engineering
Enforces rigorous ML modeling, feature engineering, training, and evaluation standards at principal-engineer level.
0
predictions
Use when making a forward-looking claim with a checkable outcome (reply within 24h, error rate will drop, this skill will see more use) — record to state/predictions.jsonl with a review horizon so reflection can grade you later. Closes the in-the-moment double-loop.
6 · bundle
autonomous-skill
Use when work must continue across multiple Codex sessions with `.autonomous/` tracking, resumable execution, or autonomous handoff. Use for long-running, multi-session, or resume-later tasks.
3 · bundle
lambda
Universal transformation λ(ο,K).τ with recursive self-improvement. USE WHEN routing reasoning, validating knowledge graphs, preparing CICM/ANZCA examinations, or when self-improvement of reasoning/architecture/context is required. Routes queries through R0-R3 complexity pipelines, validates topology (η≥target) and governance (KROG), emits per style (Φ), and compounds learnings into knowledge K. Triggers on complexity assessment, multi-step reasoning, examination mode, or /λ invocation.
0 · bundle
fallback
Graceful degradation when primary approach fails. Try alternates in priority order; record which path succeeded for future routing.
1 · bundle
python-resilience
Python resilience patterns including automatic retries, exponential backoff, timeouts, and fault-tolerant decorators. Use when adding retry logic, implementing timeouts, building fault-tolerant services, or handling transient failures.
0
code-quality
Writing maintainable code - readability principles, SOLID patterns applied pragmatically, and the judgment to know when rules should bendUse when "code quality, clean code, readability, naming, SOLID, refactor, code review, best practices, maintainable, how should I structure, clean-code, solid, readability, maintainability, code-review, naming, functions, principles" mentioned.
128 · bundle
code-quality
Reviews cohesion, naming, responsibility, complexity, and maintainability. Do not use as a default companion to every code change.
0
reason
Understand through recursive decomposition and modular reconstruction of simple operations to reproduce emergent complexity. Use this skill whenever reasoning is required. Framework for [[#parse|parsing]], [[#branch|branching]], [[#reduce|reducing]], [[#ground|grounding]] and [[#emit|emitting]]. Employs metacognitive reasoning epistemology, leveraging first principles through recursive decomposition[^1]. Self-referential and scale-invariant.
0
retrospective
Analyzes evaluation patterns across completed plans and evolves the superpowers checklists accordingly.
580 · bundle
apex-batch-chaining
Chains Salesforce Batch Apex jobs via finish() callbacks, Flex Queue guards, or a Queueable coordinator, with guidance on state passing and test limitations.
15 · bundle
alerting-oncall
Alert design and on-call practices — severity, runbooks, SLO burn-rate alerting, escalation. Use when designing alerts, writing runbooks, reducing alert fatigue, setting up escalation policies, implementing SLO-based alerting, or improving on-call processes.
0