feature-store-connector
Feature Store Connector - Auto-activating skill for ML Deployment. Triggers on: feature store connector, feature store connector Part of the ML Deployment skill category.
33
Quality
3%
Does it follow best practices?
Impact
84%
0.95xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/08-ml-deployment/feature-store-connector/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that provides almost no useful information for skill selection. It names the skill and its category but fails to describe any concrete capabilities, use cases, or meaningful trigger conditions. The repeated trigger term suggests auto-generated content without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Connects to feature stores to retrieve, register, and serve ML features for model training and inference'
Include a 'Use when...' clause with natural trigger terms like 'feature store', 'ML features', 'feature retrieval', 'feature serving', 'online features', 'offline features'
Specify supported platforms or protocols if applicable (e.g., 'Feast', 'Tecton', 'SageMaker Feature Store') to improve distinctiveness
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Feature Store Connector') without describing any concrete actions. There are no verbs indicating what the skill actually does - no 'connects', 'retrieves', 'syncs', or other specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and provides no explicit 'when to use' guidance. The 'Triggers on' line is just the skill name repeated, not meaningful trigger conditions. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('feature store connector' repeated twice) and overly technical. Missing natural variations users might say like 'feature store', 'ML features', 'feature retrieval', 'feature serving', or specific platform names. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Feature Store Connector' is somewhat specific to ML infrastructure, which provides some distinctiveness. However, without describing what it actually does, it could conflict with other ML-related skills or data connector skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content about feature store connectors. It describes what a skill should do without providing any concrete guidance, code examples, or actionable information. The entire content is self-referential boilerplate that would provide zero value to Claude when actually working with feature stores.
Suggestions
Add concrete code examples showing how to connect to common feature stores (Feast, Tecton, AWS Feature Store, etc.) with executable Python snippets
Define a clear workflow for feature retrieval: connect -> authenticate -> query features -> handle responses, with validation steps
Replace meta-descriptions ('Provides step-by-step guidance') with actual step-by-step guidance for specific feature store operations
Include specific configuration examples, API patterns, and common error handling for production feature store integration
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about feature store connectors. Every section describes what the skill does abstractly rather than providing concrete guidance Claude could use. | 1 / 3 |
Actionability | No concrete code, commands, or specific examples are provided. The content only describes capabilities in vague terms ('provides step-by-step guidance', 'generates production-ready code') without actually delivering any of these. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for connecting to or working with feature stores. | 1 / 3 |
Progressive Disclosure | No references to external files, no structured content organization, and no actual technical content to organize. The sections are just meta-descriptions of what the skill supposedly does. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
f17dd51
- Reviewed
Table of Contents
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.