knowledge-synthesis-attribution-format
Sub-skill of knowledge-synthesis: Attribution Format (+1).
Best use case
knowledge-synthesis-attribution-format is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of knowledge-synthesis: Attribution Format (+1).
Teams using knowledge-synthesis-attribution-format should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/attribution-format/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How knowledge-synthesis-attribution-format Compares
| Feature / Agent | knowledge-synthesis-attribution-format | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of knowledge-synthesis: Attribution Format (+1).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
Related Skills
domain-knowledge-sweep
Systematic multi-source research of an engineering domain. Spawns parent issue → 6 research subissues (Standards, Academic, Industry, LinkedIn-marketing, Code-audit, Synthesis) → gap implementation subissues. Replaces LinkedIn-only extraction with defensible comprehensive sourcing.
public-knowledge-graph-governance
Maintain public-safe knowledge graph artifacts for llm-wiki and similar markdown knowledge bases. Use when changing graph generators, validators, schema docs, weekly freshness checks, or public/private source-scope boundaries.
workspace-knowledge-doc-contracts
Class-level workspace knowledge, LLM-wiki, repo mission contracts, stale doc references, semantic taxonomy, and knowledge-source reconnaissance.
multi-format-transaction-parser
Parse and consolidate financial transaction data across multiple CSV formats and years
multi-format-csv-parser-with-deduplication
Parse brokerage CSV exports that exist in multiple formats with overlapping data across files
multi-format-csv-detection-and-deduplication
Detect and handle multiple CSV format versions from the same data source; deduplicate records across format variants
knowledge-pipeline
Workflow for maintaining workspace-hub knowledge and learning pipelines across scripts/knowledge, scripts/learning, and docs/superpowers, including indexing, archive synthesis, issue updates, and pipeline troubleshooting.
knowledge-base-builder
Build searchable knowledge bases from document collections (PDFs, Word, text files). Use for creating technical libraries, standards repositories, research databases, or any large document collection requiring full-text search.
knowledge-source-recon
Reconnaissance pattern to inventory all knowledge sources across the workspace-hub ecosystem's existing intelligence infrastructure. Maps raw sources for LLM Wiki ingestion planning. Leverages pre-built registries and indexes rather than re-scanning directories.
user-research-synthesis
Synthesize qualitative and quantitative user research into structured insights and opportunity areas
knowledge-synthesis
Combines search results from multiple sources into coherent, deduplicated answers with source attribution and confidence scoring.
knowledge-management
Create, organize, and maintain support knowledge base content to reduce ticket volume