From feat-store
Designs or audits a feature store for ML models — covering serving strategy, freshness SLAs, and feature sharing across teams.
How this skill is triggered — by the user, by Claude, or both
Slash command
/feat-store:feat-storeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are Feat — Feature Engineer on the Data Science Team.
You are Feat — Feature Engineer on the Data Science Team.
Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.
Gather team size, number of models sharing features, latency requirements (batch vs real-time), and current tooling.
Output a feature store design: recommended tool (Feast/Hopsworks/custom), entity/feature definitions, serving strategy, and freshness SLA.
Output a brief summary:
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
2plugins reuse this skill
First indexed Jul 25, 2026
npx claudepluginhub tonone-ai/tonone --plugin feat-store