explore-run
Rigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subset validation, short-cycle guess-and-check, batch sweeps, idle-GPU search, or quick transfer-learning trials, with fair-comparison caveats and no-overclaim summaries in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline execution, conservative training verification, default routing, verified SOTA claims, or implicit experimentation.
What this skill does
# explore-run Use this as the Rigor Improve / Rigor Explore run leaf skill. The installed slug remains `explore-run` for compatibility. Use the shared operating principles in `../../references/agent-operating-principles.md`; this skill should guide candidate run planning while preserving model judgment about the active repo. ## When to apply - When the researcher explicitly authorizes exploratory runs. - When the task is a small-subset validation, short-cycle training probe, batch sweep, idle-GPU search, or quick transfer-learning trial. - When the output should rank candidate runs rather than certify trusted success. ## When not to apply - When the user wants trusted training execution or conservative verification. - When there is no explicit exploratory authorization. - When the task is repository setup, intake, or debugging. ## Clear boundaries - This skill owns exploratory execution planning and summary only. - Use `ai-research-explore` instead when the task spans both current_research coordination and exploratory code changes. - It may hand off actual command execution to `minimal-run-and-audit` or `run-train`. - It should keep experiment state isolated from the trusted baseline. - It should prefer small-subset and short-cycle checks before heavier exploratory runs. - It should label run results as bounded evidence and explain when a comparison is not directly fair. ## Ranking Semantics - Pre-execution candidate selection uses three factors: `cost`, `success_rate`, and `expected_gain`. - Default weights should stay conservative unless the researcher explicitly provides `selection_weights`. - Budget pruning still applies after scoring through `max_variants` and `max_short_cycle_runs`. - If runs are executed later, downstream ranking should switch to real execution evidence, not stay purely heuristic. ## Variant Spec Hints - Use `variant_axes` to define the candidate dimension grid. - Use `subset_sizes` and `short_run_steps` to express exploratory run scale. - Use `selection_weights` to rebalance `cost`, `success_rate`, and `expected_gain`. - Use `primary_metric` and `metric_goal` so downstream ranking can order executed candidates consistently. ## Output expectations - `explore_outputs/CHANGESET.md` - `explore_outputs/SCIENTIFIC_CHANGELOG.md` - `explore_outputs/COMPARABILITY_REPORT.md` - `explore_outputs/TOP_RUNS.md` - `explore_outputs/status.json` ## Notes Use `references/execution-policy.md`, `../../references/explore-variant-spec.md`, `../../references/deep-learning-experiment-principles.md`, `scripts/plan_variants.py`, and `scripts/write_outputs.py`.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.