[ENHANCEMENT] use skill when skill is avaible

[scotthuang1989]

Problem (one or two sentences)

It seems roocode will not use skill unless I explicitly ask it to use it. is there a setting for this?
the same skill can be used properly by other agent (openclaw, opencode , etc.)

Context (who is affected and when)

I am working on a specific code base, I summary a skill for this code base. for example, how to add a module for this code base. but every time, I ask roocode to do it. I see that it try to read the makefile and figure it out how to add a module. use a skill should be more efficient .

Desired behavior (conceptual, not technical)

use a skill when the skill is avaiable.

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote-v0]

I have analyzed this issue and here is my proposed implementation plan:

Problem Analysis:
The system prompt already includes a <mandatory_skill_check> section (in src/core/prompts/sections/skills.ts) that instructs the model to evaluate available skills before producing any response. However, models often skip this check and proceed directly to solving the task themselves (e.g., reading Makefiles to figure out how to add a module rather than using a skill that already documents this process).

The root cause is that the skill check instruction appears only once in the system prompt and is buried between other sections (modes, rules, etc.). LLMs are more likely to follow instructions that are reinforced in multiple places and positioned prominently.

Proposed Changes:

1. Reinforce skill awareness in the RULES section (src/core/prompts/sections/rules.ts): Add a rule that explicitly tells the model to check available skills before attempting to solve tasks from scratch. Rules are a high-attention area of the prompt that models tend to follow more reliably.

2. Reinforce skill awareness in the OBJECTIVE section (src/core/prompts/sections/objective.ts): Add a step at the beginning of the goal-setting workflow that says "Before starting work, check if any available skills apply to this task." The objective section defines the model's step-by-step approach, so adding skill checking as Step 0 would make it part of the standard workflow.

3. Strengthen the mandatory_skill_check wording (src/core/prompts/sections/skills.ts): Make the instruction more forceful - for example, adding "WARNING: Ignoring an applicable skill wastes tokens and produces inferior results. Skills contain tested, optimized procedures." and moving the check emphasis to the very beginning of the block.

These are prompt-only changes with no behavioral/code logic changes needed. All existing tests should continue to pass, and new tests will be added for the reinforcement text in the rules and objective sections.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.