concept-brieflisted
Install: claude install-skill ymurat/academic-agent-skills
# Concept brief
Produce an evidence-based brief on one concept or topic. Accuracy beats completeness: a section with no verified source says so instead of being filled from memory.
Design credits: evidence grading and audit trail adapted from dgagf111/multi-perspective-research (MIT); explanation layer adapted from guicortei/feynman-technique (MIT).
## Inputs
- The concept or topic (required).
- Reader level: general, student, or specialist (default: specialist/academic).
- Language: the user's language (default Turkish, TDK spelling; keep technical terms in English when no established Turkish term exists, giving the English term in parentheses on first use).
- Length: short (about 1 page) or full (default full).
If the concept is ambiguous (same name in several fields), ask one focused question or state the reading you chose and proceed.
## Research (before writing)
1. Disambiguate: identify field(s) and common synonyms, acronyms, and the English term.
2. Find the authoritative definition: for software/systems topics check SWEBOK v4, ISO/IEC/IEEE standards and glossaries (e.g. ISO/IEC/IEEE 24765), NIST; for AI/governance check NIST AI RMF, OECD, EU AI Act text, ISO/IEC 22989; otherwise a major handbook, encyclopedia of the field, or highly cited review.
3. Find the origin: who introduced or named the concept, in which work, which year. Open the source (publisher page, DOI landing page, archive). If only secondary sources attribute it, say "secondary attribution" and nam