feature-store-design SKILL.md skillA
feature-store-design from skillmedev/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add skillmedev/skills/feature-store-design@git:20261005.bea4ea5Pins git:20261005.bea4ea5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- skillmedev/skills
- Path
skills/feature-store-design/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261005.bea4ea5, committed Oct 5, 2026
- First version recorded
- Jul 5, 2026
- Size
- 8,396 bytes
- Repository stars
- 19
- License
- MIT
Designs a reusable, leakage-safe feature store - entity and naming contracts, point-in-time correct training joins, feature versioning, online/offline consistency with staleness SLOs, and governance. Use when someone asks "should we build a feature store", "how do I share features across models", "our model trains great but serves garbage", "how do I version a feature definition", or is diagnosing training-serving skew. Do NOT use for designing the feature transformations themselves - use…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Feature Store Design Feature stores exist to solve three problems at once: reuse across models, point-in-time correctness during training, and consistency between training and serving. A design that solves only one is incomplete - and the failure mode is expensive: silent label leakage that inflates offline metrics, or training-serving skew that makes a model score 0.85 offline and behave randomly in production. ## Operating procedure ### Step 1: Decide whether a feature store is warranted Collect: number of models in production or planned, how many features they would share, and whether any model serves online. Rule of thumb: below 2-3 models sharing features, a feature store is premature infrastructure - a documented feature pipeline with a catalog (see ml-feature-engineering) does the job. Build or adopt one when features are shared across 3+ models, when online serving needs the same values training used, or when point-in-time bugs have already burned the team. Label the decision and its inputs; revisit when the model count doubles. ### Step 2: Fix entity and naming contracts Consistent naming is load-bearing - it is the API contract for every downstream model. …
Read the whole file at its exact version.
How to install
mdr add skillmedev/skills/feature-store-design@sha256:e83719d071d8c2b4The line at the top of this page pins the label git:20261005.bea4ea5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_dzwgyjw7hsjal55g)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 5, 2026 and Oct 5, 2026, about one every 46 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261005.bea4ea5 latest | 2026-10-05 | bea4ea5 | 8,396 B | A | view · diff |
| git:20260705.a28c4ce | 2026-07-05 | a28c4ce | 8,354 B | A | view · diff |
| git:20260705.acb5571 | 2026-07-05 | acb5571 | 8,382 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8396 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
skillmedev/skills · 19 stars · license MIT · pushed 2026-10-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dzwgyjw7hsjal55g GET https://markdownregistry.com/api/v1/resolve?ref=skillmedev/skills/feature-store-design GET https://markdownregistry.com/api/v1/blob/e83719d071d8c2b4ce0a893826757411347a14e11139755097a3ae892b2887de
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.