Summary
This project already has a great foundation with:
- LangGraph orchestration
- MCP dynamic tools
- tool approval flow
- persistent memory
A very valuable next step would be first-class Skills support.
Why
MCP tools answer:
Skills would answer:
- how the agent should approach a task
That would make it easier to create reusable, task-specific capabilities such as:
- research assistant
- code review
- PR summarization
- customer support workflows
- domain-specific operating instructions
Suggested MVP
A simple first version could support:
- loading skills from a local
skills/ directory
- enabling/disabling skills per agent or thread
- injecting active skill instructions into the system prompt/context
- optionally exposing active skills in the UI
Why this fits this template
This template already supports dynamic tools and LangGraph-based orchestration, so adding a skills layer feels like a natural next step.
Benefit
This would make the project more reusable, composable, and practical for real-world agent workflows.
Happy to help refine the idea or contribute if this is interesting.
Summary
This project already has a great foundation with:
A very valuable next step would be first-class Skills support.
Why
MCP tools answer:
Skills would answer:
That would make it easier to create reusable, task-specific capabilities such as:
Suggested MVP
A simple first version could support:
skills/directoryWhy this fits this template
This template already supports dynamic tools and LangGraph-based orchestration, so adding a skills layer feels like a natural next step.
Benefit
This would make the project more reusable, composable, and practical for real-world agent workflows.
Happy to help refine the idea or contribute if this is interesting.