sensor-calibration-workbench
Use when makers need calibration workflows for sensors such as CO2 sensors, load cells, magnetometers, color sensors, or analog sensors, including warm-up behavior, reference measurements, coefficient storage, and drift checks.
What this skill does
# Sensor Calibration Workbench
Use this skill when the sensor technically works, but the readings are not yet
trustworthy enough for the project.
## Resources
- `references/calibration-flow.md` - end-to-end calibration workflow and evidence checklist
- `references/common-failure-patterns.md` - warm-up, scaling, drift, saturation, and environment mistakes
- `references/persistence-and-revalidation.md` - storing coefficients and deciding when recalibration is needed
## When to Use
Use this skill when the request involves:
- volatile or implausible sensor readings
- "how do I calibrate this sensor?"
- load-cell factor tuning
- CO2, magnetometer, or color-sensor calibration
- storing calibration coefficients in EEPROM or flash
- deciding whether the problem is calibration, hardware, or environment
Do not use this skill when the sensor is not detected at all. That should route
through hardware or bus bring-up first.
## Workflow
1. Confirm the measurement problem:
- unstable -> open `references/common-failure-patterns.md`
- offset or scaling error -> open `references/calibration-flow.md`
- values good once but bad later -> open
`references/persistence-and-revalidation.md`
2. Identify the calibration class:
- one-point or zero-offset
- two-point scale calibration
- multi-orientation or environmental calibration
3. Collect reference evidence before changing coefficients:
- known reference values
- warm-up state
- ambient conditions
- sample stability
4. Decide how calibration values will persist and how revalidation will be
triggered after reboot, firmware update, or field drift.
## Core Rules
- Calibration without a known reference is guesswork.
- Warm-up and stabilization time are part of calibration, not a side note.
- Do not mix hardware-fault symptoms with coefficient-tuning symptoms.
- Store both the calibration values and enough metadata to know when they became
stale.
## Verification
- Confirm readings converge toward a known reference after calibration.
- Confirm the calibrated values stay stable across repeated samples.
- Confirm stored coefficients reload correctly after restart.
- If the project has operating thresholds, verify those thresholds against the
calibrated output rather than the raw sensor value.
## Integration
- Pair with `i2c-bringup-diagnostician` or `circuit-debugger` when the sensor is
not yet electrically trustworthy.
- Pair with `arduino-code-generator` when the user needs persistence or
filtering code added to the sketch.
- Pair with `field-power-and-connectivity-triager` when sensor behavior changes
only off USB or under field power conditions.
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.