Integration Strategy

Blueprint for integrating new skills into the Family Doctor suite.

When to Use

• Adding a new skill to the family-doctor ecosystem
• Modifying how skills connect to the orchestrator
• Planning routing rules for new capabilities
• Designing data contracts between skills

Skill Types in Family Doctor

Integration Checklist

1. Create Skill File

Create family-doctor/[skill-name]/SKILL.md:

---
name: [skill-name]
description: One-line description. Triggers on keywords.
allowed-tools: [tool1, tool2]
---

# [Skill Name]

... detailed instructions ...

2. Add to Routing Table

Update family-doctor/SKILL.md routing table with:

• Entry trigger pattern (regex or keywords)
• Parent skill (usually "family-doctor")
• Output contract format

3. Define Data Contracts

Input Contract

{
  "query": "string",
  "context": "object",
  "preferences": "object"
}

Output Contract

{
  "query": "string",
  "results": [],
  "confidence": 0.0-1.0,
  "authorization": "session-wide|per-query|none"
}

4. Configure Authorization

All external skills must support:

5. Define Reference Schema

For health data:

{
  "id": "uuid",
  "topic": "string",
  "query": "string",
  "date": "YYYY-MM-DD",
  "sources": ["source names"],
  "summary": "string"
}

Store at: health/References/

Routing Priority

Lower number = checked first:

Conflicts to Avoid

Testing Integration

1. Verify skill file loads correctly
2. Test routing from family-doctor entry point
3. Test authorization flow
4. Verify citation output to health/References/
5. Check data contract compliance