Fetch a general article (ACM DL, IEEE, blog posts, etc.) and create a structured summary following the project's document conventions and DoD checklist
Summarize a general article (non-ML-specific) and save it as a Markdown document in the appropriate topic directory.
The user will provide a URL to an article (e.g., https://dl.acm.org/..., https://ieeexplore.ieee.org/document/..., or any web article).
create-topic skill if none fit.machine-learning/), save to <topic>/<year>/.mkdir -p.echo "<article title>" | bash scripts/title-converter.sh to convert the article title to a kebab-case filename.The summary MUST follow this structure:
# Meta Information
- URL: [<Article Title>](<original URL>)
- LICENSE: <license information — check the publisher's copyright notice>
- Reference: <authors> (<year>). <title>. <venue/publisher>.
# <Follow the article's own section structure>
## <Section headings matching the article>
<Content summarized in concrete, specific sentences.>
<Use > [!NOTE] blocks for direct quotes or clarifications.>
<Use > [!TIP] blocks for helpful external references.>
<Use > [!IMPORTANT] blocks for critical information.>
<Use > [!CAUTION] blocks for personal interpretations that may contain errors.>
## Key Contributions
<Summarize the main contributions or takeaways of the article.>
## Comparison with Related Work
<How this work differs from or builds upon related approaches.>
<Applicability: who would use this, when, and where.>
Follow these rules strictly when writing the summary. These come from the Definition of Done (DoD) checklist:
$...$ for inline math and define variables before use. For block equations (even single-line), use a math fenced code block with \begin{align}...\end{align} — do NOT use $$...$$.> [!NOTE] for direct quotes from the article> [!TIP] for links to external references or tutorials> [!IMPORTANT] for critical details not obvious from the article> [!CAUTION] for personal interpretations that may contain errors