📋 Overview
Currently, all profiles share the same .agent/skills directory, which means every skill is available regardless of which profile is active. This wastes context when working on different tasks that need different subagent skill sets.
🎯 Goal
Enable profiles to specify which skills should be included when that profile is active, reducing context waste by only loading relevant skills for the current task.
💡 Proposed Solution
Extend the profile system to support a .agent/skills configuration option that allows:
Profile-level skill selection: Each profile can define a subset of available skills to include
Automatic skill filtering: When a profile is activated, only its configured skills are made available to Claude Code
Backward compatibility: Profiles without explicit skill configuration default to including all available skills
🔧 Implementation Approach
One possible implementation could involve:
Extending the profile configuration to include a skills array or skillsFilter option
Modifying the profile wrapper to copy or symlink only the specified skills to the active profile's .agent/skills directory
Or alternatively, storing a skills manifest in each profile's configuration that Claude Code respects when available
📝 Example Use Case
bash# Create a "backend" profile optimized for backend development
claude-profile create backend
# Configure it to include only: database, api-design, testing skills
# Create a "frontend" profile optimized for UI development
claude-profile create frontend
# Configure it to include only: ui-design, accessibility, performance skills
# When switching profiles, only relevant skills are available
claude-profile use backend
claude # Only backend-specific skills loaded
claude-profile use frontend
claude # Only frontend-specific skills loaded
✅ Benefits
Context efficiency: Reduced token usage by excluding irrelevant skills
Task isolation: Different profiles for different project types or roles
Flexibility: Users can customize skill sets per profile or use defaults
Cleaner workflow: Subagents focus only on needed capabilities
📋 Overview
Currently, all profiles share the same .agent/skills directory, which means every skill is available regardless of which profile is active. This wastes context when working on different tasks that need different subagent skill sets.
🎯 Goal
Enable profiles to specify which skills should be included when that profile is active, reducing context waste by only loading relevant skills for the current task.
💡 Proposed Solution
Extend the profile system to support a .agent/skills configuration option that allows:
Profile-level skill selection: Each profile can define a subset of available skills to include
Automatic skill filtering: When a profile is activated, only its configured skills are made available to Claude Code
Backward compatibility: Profiles without explicit skill configuration default to including all available skills
🔧 Implementation Approach
One possible implementation could involve:
Extending the profile configuration to include a skills array or skillsFilter option
Modifying the profile wrapper to copy or symlink only the specified skills to the active profile's .agent/skills directory
Or alternatively, storing a skills manifest in each profile's configuration that Claude Code respects when available
📝 Example Use Case
✅ Benefits
Context efficiency: Reduced token usage by excluding irrelevant skills
Task isolation: Different profiles for different project types or roles
Flexibility: Users can customize skill sets per profile or use defaults
Cleaner workflow: Subagents focus only on needed capabilities