Skill Manager (SM)

Repository Structure & Flattened Design (扁平化設計)

• custom/: Your internal/original skills.
• external/: Community skills downloaded for inspection and reference.

Flattened vs. Conditional Nesting (扁平化與條件式嵌套)

To balance discoverability and organization:

• Default (Flattened): Every skill folder SHOULD be a direct child of its domain folder for default detection by npx skills add <directory>.
• Exception (Conditional Nesting): If a domain directory contains more than 10 skills, you MAY create one level of sub-directories (categories) to avoid clutter.
  • Note: When nesting is used, users must use npx skills add <path> --full-depth to find all skills.
• Sync Requirement: Whenever a skill's location changes, you MUST immediately update the corresponding link in SKILLS_LIST.md.

Taxonomy Alignment (目錄架構對齊)

To prevent fragmentation (e.g., mixing search/ and fetch/ for similar tools), you MUST map external skills to our existing local domains/categories:

• Local Domains: basic/, develop/, obsidian/, video-design/, writing/.
• Ignore Provider Names: If an external repo uses research/firecrawl, but we use basic/, move it to external/basic/firecrawl-search/.
• Consistency over Originality: Always prioritize our folder structure over the external repository's original layout.