feast-architecture

Internals of the Feast codebase — how each component works, where the key abstractions live, and the data flow through the system. Use when asked how feast apply works, how the registry stores data, how materialization moves data, how get_online_features retrieves features, how the feature server works, how the Kubernetes operator manages deployments, or when navigating the codebase to understand where to make a change.

Quality

81%

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

75%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-structured, information-dense architecture reference that gives Claude concrete file locations, method signatures, and data-flow sequences without padding. It is slightly long and could offload some reference detail to bundle files, but earns its length with actionable specifics.

Suggestions

Consider moving the detailed operator CRD YAML and reconcile-loop material into a bundled reference file (e.g. references/operator.md) and summarizing it in SKILL.md to reduce inline length.

Add an explicit verification step to the proto-field workflow (e.g. 'run make compile-protos-python and confirm generated files exist before updating .to_proto()/.from_proto()') to strengthen the dev workflow.

Trim the large ASCII deployment-mode diagram to the essential boxes, or move it to a reference file, to improve token efficiency without losing navigation value.

Dimension	Reasoning	Score
Conciseness	The body is dense with high-value reference material (concrete file paths, method signatures, data-flow diagrams) and assumes Claude's competence without explaining basic concepts; a few sections such as the full ASCII deployment map and operator CRD YAML could be trimmed slightly.	4 / 5
Actionability	Provides concrete, executable guidance throughout — real file paths, method signatures, a copy-ready OfflineStore subclass skeleton, `go run` commands, and proto-field workflow steps — with only minor gaps in edge cases.	4 / 5
Workflow Clarity	Data flows for `feast apply`, `materialize`, `get_online_features`, and `get_historical_features` are clearly sequenced as step diagrams, and the proto-field workflow is numbered; this is a descriptive architecture skill rather than a destructive/batch operation, so explicit validation checkpoints are not required, though a couple of dev workflows lack a verify step.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with a final table of one-level-deep `docs/` references for further reading; no bundle files exist, and while some detailed reference material is inline, the structure and signaling are good with only minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

87%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 what the skill covers and gives explicit, natural-language trigger guidance across the major Feast subsystems. It uses third person and avoids vague fluff.

Dimension	Reasoning	Score
Specificity	Names the domain (Feast codebase internals) and lists several concrete components — 'how feast apply works', 'how the registry stores data', 'how materialization moves data', 'how get_online_features retrieves features', 'how the feature server works', 'how the Kubernetes operator manages deployments' — with only minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' ('Internals of the Feast codebase — how each component works, where the key abstractions live, and the data flow through the system') and 'when' with a concrete 'Use when asked how ...' clause listing multiple concrete triggers.	5 / 5
Trigger Term Quality	Triggers use natural user phrasings ('how feast apply works', 'how the registry stores data', 'navigating the codebase to understand where to make a change') covering the main entry points, though a few synonyms or alternate phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Feast codebase internals/navigation) with distinct, product-specific triggers that are unlikely to fire for unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: feast-dev/feast
Path: skills/feast-architecture/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.