Help us improve
Share bugs, ideas, or general feedback.
From velith
Provides academic writing patterns including IMRAD structure, literature review organization, argument chains, citation practices, and thesis/dissertation layout.
npx claudepluginhub epicsagas/plugins --plugin velithHow this skill is triggered — by the user, by Claude, or both
Slash command
/velith:book-academicThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Structure types by discipline**:
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Structure types by discipline:
Literature review: Organize by theme (not chronologically). Structure: establish field → identify gap → position this work. For each source: claim + methodology + limitation + relevance. Synthesis matrix: rows = themes, columns = sources, cells = positions.
Argument chain: Claim → Evidence → Warrant (connects evidence to claim) → Backing (supports warrant) → Qualifier (scope/limits) → Rebuttal (anticipate counter). Every chapter thesis supports the central thesis. Chapter thesis = topic sentence + position + scope.
Citation practices: Inline citation for (author, year). Block quote for >40 words. Paraphrase preferred over direct quote. Primary sources for claims, secondary for context. Citation density: 2-5 per paragraph in lit review, 0-1 in methods/results.
Abstract formula: Context (1-2 sentences) → Gap (1 sentence) → Purpose (1 sentence) → Method (1-2 sentences) → Key finding (1-2 sentences) → Significance (1 sentence). Total: 150-300 words.
Paragraph structure: Topic sentence (claim) → Evidence/analysis (2-4 sentences) → Concluding sentence (significance/bridge). MEAL plan: Main idea → Evidence → Analysis → Link to next.
Academic tone: Third person, present tense for established knowledge, past tense for methodology/findings. Avoid hedging pile-up ("it could perhaps be argued that maybe"). Precise language over verbose. Define terms at first use. Consistent terminology throughout.
Figures and tables: Numbered sequentially per chapter (Fig 3.1, Table 2.4). Caption below figures, above tables. Every figure/table referenced in text. Self-contained: readable without main text.
Cross-reference: Chapter.section.subsection numbering (2.3.1). Forward refs: "as discussed in Section 4.2". Back refs: "as established in Section 2.1". Glossary for discipline-specific terms.
Revision layers: Structure (argument flow, section balance) → Evidence (sufficiency, accuracy) → Writing (clarity, tone, conciseness) → Format (citation style, headings, spacing) → Proofread (typos, consistency).