Verify skills are preserved during export/import and document skill-agent associations #82

Problem

User feedback: "i'd be super sad if i exported my team and then re-imported it and lost all my skills along the way."

Current implementation DOES export/import skills (confirmed in index.js lines 350-368 for export, lines 477-483 for import), but:

1. Need to verify this works end-to-end with test coverage
2. Documentation doesn't explicitly call out that skills travel with the team
3. Unclear whether skills should be associated with specific team members or remain team-wide

Questions to Research

1. Current behavior verification:

   • Do skills export/import correctly end-to-end? (Code suggests yes, but needs testing)
   • Are skill SKILL.md files preserved with full YAML frontmatter and content?
   • Do MCP tool dependencies in skills survive the round trip?

2. Design question - skill ownership:

   • Should skills be team-wide (current: .ai-team/skills/{skill-name}/SKILL.md)?
   • Or should skills be per-agent (alternative: .ai-team/agents/{name}/skills/{skill-name}/SKILL.md)?
   • Current decisions.md (2026-02-09) says "Flat skills/ directory replaces per-agent files — skills are team knowledge"
   • But should certain skills be agent-specific? (e.g., a Tester's skill in "writing snapshot tests" vs a Backend dev's skill in "PostgreSQL query optimization")

3. Documentation gaps:

   • docs/features/export-import.md lists "Skills: ✅" but doesn't explain the details
   • Should call out explicitly: "All earned skills export with the team and are immediately available after import"
   • Should explain skill confidence levels survive the journey

Acceptance Criteria

• Test: Export a squad with 3+ skills, import to new repo, verify all SKILL.md files exist and are identical
• Test: Verify skill metadata (confidence levels, MCP dependencies) survives export/import
• Docs: Update docs/features/export-import.md with explicit skills callout and example
• Docs: Update docs/features/skills.md to explain portability via export/import
• Decision: Document whether skills should remain team-wide or support per-agent skills in future
• If skill-agent association is desired, file separate issue for implementation in v0.6.0+

Why This Matters

Skills are one of Squad's most valuable features — they're the compound learning that makes teams smarter over time. Losing skills during team portability would be catastrophic for the "team is more valuable than the project" value prop. We need ironclad guarantees that skills survive export/import, and users need to KNOW they're safe.