Feature Request: Auto-apply skills on session start
What problem does this solve?
Currently, skills must be manually applied at the start of each session using apply_skill. Users who want consistent skill behavior (e.g., always having obsidian-context and programming-assistant active) have no way to persist this across sessions.
Proposed solution
Add a config option to opencode.json (or equivalent) that specifies skills to auto-apply on startup:
{
"skills": {
"apply_on_start": ["obsidian-context", "programming-assistant"]
}
}Or alternatively, a startup_skills array in the skills MCP config:
{
"mcp": {
"skills": {
"startup_skills": ["obsidian-context", "programming-assistant"]
}
}
}Alternatives considered
- Session start prompt — users manually invoke
apply_skill each time (current workaround, not scalable)
- Profile-based activation — tie skill activation to specific work profiles (adds complexity)
- CLI flag —
--apply-skills on startup (less discoverable than config)
Priority
Medium — nice to have for power users, not blocking any core functionality.
Feature Request: Auto-apply skills on session start
What problem does this solve?
Currently, skills must be manually applied at the start of each session using
apply_skill. Users who want consistent skill behavior (e.g., always havingobsidian-contextandprogramming-assistantactive) have no way to persist this across sessions.Proposed solution
Add a config option to
opencode.json(or equivalent) that specifies skills to auto-apply on startup:{ "skills": { "apply_on_start": ["obsidian-context", "programming-assistant"] } }Or alternatively, a
startup_skillsarray in the skills MCP config:{ "mcp": { "skills": { "startup_skills": ["obsidian-context", "programming-assistant"] } } }Alternatives considered
apply_skilleach time (current workaround, not scalable)--apply-skillson startup (less discoverable than config)Priority
Medium — nice to have for power users, not blocking any core functionality.