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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill feature-store-connectorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It names the skill and category but fails to describe any concrete capabilities, use cases, or meaningful trigger terms. The repeated trigger term suggests auto-generated content without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Connects to feature stores (Feast, Tecton, SageMaker Feature Store) to retrieve, register, and manage ML features for model training and inference.'
Include a 'Use when...' clause with natural trigger scenarios, e.g., 'Use when fetching features for model serving, registering new features, or integrating feature pipelines into ML workflows.'
Add natural keyword variations users might say: 'feature retrieval', 'feature engineering', 'ML features', 'feature pipeline', 'online/offline features', specific platform names.
| 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 the name itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'feature store connector' repeated twice, which is redundant and overly technical. Missing natural variations users might say like 'feature retrieval', 'ML features', 'feature engineering', 'feature pipeline', or specific feature store names. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Feature Store Connector' is somewhat specific to ML infrastructure, which provides some distinctiveness. However, without describing specific capabilities, it could conflict with other ML-related skills or data connector skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about feature store connectors. It contains only generic boilerplate describing what a skill should do without providing any actionable guidance, code examples, or specific information about feature stores, ML deployment, or connector patterns.
Suggestions
Add concrete code examples showing how to connect to common feature stores (Feast, Tecton, SageMaker Feature Store) with executable Python snippets
Define a clear workflow for feature retrieval: connect -> query features -> handle versioning -> validate data types
Include specific configuration examples (connection strings, authentication patterns, batch vs online serving)
Replace generic capability descriptions with actual technical guidance on feature store connector patterns and common pitfalls
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about feature store connectors. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually connect to a feature store or implement anything. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes when the skill activates and what it claims to do, without any actual procedural guidance. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no references to detailed documentation, examples, or related files. There's no structure beyond placeholder sections. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.