ml-feature-engineering

ML feature engineering workflow for feature definition, lineage, and online-offline parity. Use when model performance depends on explicit feature design and parity controls; do not use for generic API-layer or infrastructure-only changes.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "ml-feature-engineering" with this command: npx skills add kentoshimizu/sw-agent-skills/kentoshimizu-sw-agent-skills-ml-feature-engineering

Ml Feature Engineering

Overview

Use this skill to design features that are useful, explainable, and consistent across training and serving.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Online/offline parity rules:
    • references/online-offline-parity-rules.md

Templates And Assets

  • Feature specification template:
    • assets/feature-spec-template.csv

Inputs To Gather

  • Candidate feature hypotheses and business rationale.
  • Data sources and freshness constraints.
  • Serving path capabilities and latency budget.
  • Leakage/fairness/compliance constraints.

Deliverables

  • Feature catalog with lineage and ownership.
  • Parity validation plan for train vs serve paths.
  • Feature risk and maintenance notes.

Workflow

  1. Define feature specs in assets/feature-spec-template.csv.
  2. Validate parity assumptions with references/online-offline-parity-rules.md.
  3. Prioritize features by incremental value vs complexity.
  4. Verify leakage and freshness assumptions.
  5. Publish feature rollout and deprecation plan.

Quality Standard

  • Feature definitions are versioned and reproducible.
  • Online/offline behavior is consistent for decision-critical features.
  • Feature ownership and monitoring are explicit.

Failure Conditions

  • Stop when feature logic diverges between training and serving.
  • Stop when feature value cannot justify operational complexity.
  • Escalate when parity gaps remain unresolved.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Web3

requirements-definition

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

architecture-clean-architecture

No summary provided by upstream source.

Repository SourceNeeds Review
Security

security-authentication

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

sqlalchemy-orm-patterns

No summary provided by upstream source.

Repository SourceNeeds Review