feast-user-guide

Guide for working with Feast (Feature Store) — defining features, configuring feature_store.yaml, retrieving features online/offline, using the CLI, and building RAG retrieval pipelines. Use when the user asks about creating entities, feature views, on-demand feature views, stream feature views, feature services, data sources, feature_store.yaml configuration, feast apply/materialize commands, online or historical feature retrieval, or vector-based document retrieval with Feast.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, highly actionable Feast reference with strong executable examples. It loses points for missing validation checkpoints around destructive/batch operations and for referencing bundle files that are not present.

Suggestions

Add validation/verification steps for destructive or batch operations — e.g., 'After `feast apply`, run `feast feature-views list` to confirm registration' and a checkpoint before `feast teardown`.

Create the referenced bundle files (references/feature-definitions.md, references/configuration.md, references/retrieval-and-rag.md) or remove the broken links so progressive disclosure resolves.

Trim elementary concept explanations (e.g., the Entity/FeatureView prose) that restate what Claude already knows, leaning even harder on the code examples.

Dimension	Reasoning	Score
Conciseness	Code-forward and mostly lean, but includes a few explanations of concepts Claude already knows (e.g., 'An entity is a collection of semantically related features… Entities have join keys used to look up features'), so it is efficient with minor over-explanation rather than perfectly tight.	4 / 5
Actionability	Provides copy-paste-ready, executable code for entities, data sources, feature views, on-demand views, feature services, online/historical retrieval, materialization (CLI + Python), and vector retrieval — covering the common cases concretely.	5 / 5
Workflow Clarity	Quick Start and Materialization are sequenced, but batch/destructive operations ('feast materialize', 'feast teardown') lack validation or verification checkpoints, so workflow clarity is capped at 3 per the destructive/batch-operations rule.	3 / 5
Progressive Disclosure	Structure and a clearly signaled Detailed References section are good, but the three referenced files (feature-definitions.md, configuration.md, retrieval-and-rag.md) do not exist in the bundle, so the one-level-deep references do not resolve — pulling this below a 4.	3 / 5
	Total	15 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states capabilities and provides explicit, natural trigger phrases covering the Feast feature-store domain. It is concise, third-person, and distinguishes itself from other skills well.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('defining features, configuring feature_store.yaml, retrieving features online/offline, using the CLI, and building RAG retrieval pipelines'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both 'what' (a guide for working with Feast and its listed capabilities) and 'when' via a concrete 'Use when the user asks about…' clause enumerating trigger scenarios.	5 / 5
Trigger Term Quality	Covers natural Feast-domain terms users would say — 'entities, feature views, on-demand feature views, stream feature views, feature services, feast apply/materialize commands, online or historical feature retrieval, vector-based document retrieval' — with synonyms and command names.	5 / 5
Distinctiveness Conflict Risk	Targets a clear Feast-specific niche with distinct triggers (feature_store.yaml, feast apply/materialize, feature views), making conflict with unrelated skills minimal.	5 / 5
	Total	20 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 suspicious	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: feast-dev/feast
Path: skills/feast-user-guide/SKILL.md
Commit: 5ad5592

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.