Context Quality

Only write context that will be reused later. Before saving an index, summary, or profile, ensure it passes the Minimum-Signal Threshold.

Signal Scoring

Each item in an index or summary gets scored:

Component	Points
Title or name	+1
Link or ID	+1
1-line purpose	+1
Owner or tag	+1

Include items with signal ≥ 2. Items with only a name and nothing else don't provide enough value to persist.

Constraints

• Max 10 items per index or summary
• Sort by signal (highest first), then by recency
• Omit raw timelines, counts, or empty sections
• Be conservative—verify everything you store, make no assumptions

When NOT to Write

If the threshold isn't met (too few items with signal ≥ 2), do NOT write the index. Instead:

1. Add a single enrichment task describing what's missing
2. Return to the user with a suggestion: "I found some contacts but need more context—who are your key collaborators?"

Examples

Good: Meets Threshold

## Key Contacts

| Name | Email | Relationship |
|------|-------|--------------|
| Sarah Chen | sarah@acme.com | Design lead, weekly syncs |
| Alex Kumar | alex@acme.com | Eng manager, project owner |

Both entries have: name (+1), email/ID (+1), relationship/purpose (+1) = signal 3 ✓

Bad: Below Threshold

## Key Contacts

- Sarah
- Alex
- Someone from marketing

No IDs, no purpose, no context. Signal = 1 for each. Don't persist this.

Enrichment Instead

When threshold isn't met:

## Key Contacts

_Insufficient signal. Need to identify:_
- Full names and emails for top collaborators
- Relationship context (team, project, frequency)

**Next step:** Check sent emails for frequent recipients, or ask user directly.

Application

This threshold applies to:

• Profiles built by discovery skills (gmail, slack, calendar)
• Indexes of documents, pages, or resources
• Summaries of conversations or threads
• Entity lists (people, companies, projects)

Skills that build persistent context should reference this guide to avoid low-signal noise in the user's workspace.