Flatten deeply nested skills

[szabosteve]

Description

During hands-on testing, some skills required too many navigation hops before reaching actionable content.

For example:

root → search-quality → search-strategies → hybrid-search → combining-searches

This makes it harder for agents to reach the relevant leaf skill quickly, especially when the user already has a concrete task or troubleshooting symptom.

Proposed change

Review deeply nested skill paths and identify where the hierarchy can be flattened.

Validation

Test the updated structure against the current hierarchy to check whether it reduces navigation hops and helps agents reach actionable content faster.

[szabosteve]

Possible approaches:

• Merge shallow intermediate hub pages into their parent section.
• Link important leaf skills directly from higher-level hub pages.
• Reduce purely navigational pages that add little context.
• Keep feature-based organization where useful, but avoid unnecessary depth.