GeezerVison is showing github.com — Add Feast Agent Skills · Issue #5976 · feast-dev/feast
Add Feast Agent Skills #5976Activitypatelchaitany commented on Feb 23, 2026 Hey can I pick up this issue? Sagargupta16 commented on Mar 9, 2026 I'd like to take this on. Noticed @patelchaitany expressed interest but no PR has been submitted yet -- happy to collaborate if they're still working on it.
Plan:
- Create skills following the
anthropics/skills SKILL.md format
- Focus on practical Feast workflows: feature store setup, feature definitions, materialization, and retrieval
- Include both a development/contributor skill and a user-facing feature engineering skill
- Will reference Feast's actual CLI commands and Python SDK patterns
Will have a PR up soon. franciscojavierarceo commented on Mar 9, 2026 Sagargupta16 commented on Mar 10, 2026 @franciscojavierarceo good call -- updated the PR to support both platforms.
Changes made:
- Moved skills from
.claude/skills/ to a top-level skills/ directory so they're platform-agnostic
- Added
license, compatibility, and metadata fields to the SKILL.md frontmatter per the Agent Skills spec
- Both OpenAI (tools/skills docs) and Claude Code follow the same open Agent Skills standard, so the SKILL.md format works across both
The skills can be used with OpenAI via their skills API upload, or with Claude Code by symlinking into .claude/skills/. Same files, no modifications needed. ntkathole commented on Mar 10, 2026 Sagargupta16 commented on Mar 10, 2026 @ntkathole thanks for connecting us! I reviewed #6007 from @patelchaitany.
Our PRs have complementary scope with no overlap:
Since the scopes are different, both PRs can merge independently without conflict. I've updated #6081 to remove the user-facing skill (feast-feature-engineering) and keep only the feast-dev contributor skill, so there's zero overlap with @patelchaitany's work.
I also left a review suggestion on #6007 for spec compliance (the Agent Skills standard requires lowercase names and the skills/ directory convention for cross-platform support). Reacted by Nikhil Kathole and Francisco Javier Arceo passionworkeer commented on Mar 10, 2026 Great idea! For implementing Agent Skills: 1) Create a skills/ directory with skill_name/SKILL.md, 2) Define triggers (keywords, URLs, etc.) in the SKILL.md, 3) Load skills at startup via skills field in config. Look at OpenClaw's skill structure for reference - they use �vailable_skills with description, location, and triggers. Happy to help review the PR! Reacted by Nikhil Kathole added a commit that references this issue on Mar 16, 2026This issue will close once commit 1e5b60f is merged into the 'master' branch.1e5b60f added a commit that references this issue on Mar 17, 2026This issue will close once commit 557f859 is merged into the 'master' branch.557f859 added a commit that references this issue on Mar 18, 2026This issue will close once commit 5b0df6c is merged into the 'master' branch.5b0df6c added a commit that references this issue on Mar 23, 2026This issue will close once commit d330e5c is merged into the 'master' branch.d330e5c added a commit that references this issue on Apr 2, 2026This issue will close once commit 24f2b45 is merged into the 'master' branch.24f2b45
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|