| name | knowledge-synthesis-attribution-format |
| description | Sub-skill of knowledge-synthesis: Attribution Format (+1). |
| version | 1.0.0 |
| category | business |
| type | reference |
| scripts_exempt | true |
Attribution Format (+1)
Attribution Format
Inline for direct references:
Sarah confirmed the REST approach in her email on Wednesday.
The design doc was updated to reflect this (~~cloud storage: "API Design Doc v3").
Source list at the end for completeness:
Sources:
- ~~chat: #engineering discussion (Jan 14) — initial decision thread
- ~~email: "API Decision" from Sarah Chen (Jan 15) — formal confirmation
- ~~cloud storage: "API Design Doc v3" last modified Jan 15 — updated specification
Attribution Rules
- Always name the source type (~~chat, ~~email, ~~cloud storage, etc.)
- Include the specific location (channel, folder, thread)
- Include the date or relative time
- Include the author when relevant
- Include document/thread titles when available
- For ~~chat, note the channel name
- For ~~email, note the subject line and sender
- For ~~cloud storage, note the document title